Package: systemd
Version: 252.22-1~deb12u1
Severity: important
X-Debbugs-Cc: sunkan+debian.bugs@zappa.cx

Dear Maintainer,

After upgrading systemd from 252.19-1~deb12u1 to 252.22-1~deb12u1
(Bookworm 12.4 to 12.5) the IFB network devices are no longer
automatically created when loading the `ifb` module. This is a
regression since previous releases as there is nothing mentioned about
this in the changelog.

It seems the root cause is that the following has been added to /lib/modprobe.d/systemd.conf

[part of .../systemd.conf]
# Do the same for ifb0.

options ifb numifbs=0
[end]

How this will affect your system depends a lot on what you use the IFB device(s) for. In my case it is used in combination with a QoS scheduling/shaping setup.

For now I have worked around this change by adding the IFB device I
needed manually with the command `ip link add ifb0 numtxqueues 8 type
ifb`. And from what I can tell the kernel default setting is
`numifbs=2`.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Control: tags -1 wontfix
Control: close -1

On Mon, 12 Feb 2024 08:33:21 +0100 Andreas Sundstrom <sunkan+debian.bugs@zappa.cx> wrote:

Package: systemd
Version: 252.22-1~deb12u1
Severity: important
X-Debbugs-Cc: sunkan+debian.bugs@zappa.cx

Dear Maintainer,

After upgrading systemd from 252.19-1~deb12u1 to 252.22-1~deb12u1
(Bookworm 12.4 to 12.5) the IFB network devices are no longer
automatically created when loading the `ifb` module. This is a
regression since previous releases as there is nothing mentioned

about

this in the changelog.

It seems the root cause is that the following has been added to /lib/modprobe.d/systemd.conf

[part of .../systemd.conf]
# Do the same for ifb0.

options ifb numifbs=0
[end]

How this will affect your system depends a lot on what you use the

IFB

device(s) for. In my case it is used in combination with a QoS scheduling/shaping setup.

For now I have worked around this change by adding the IFB device I
needed manually with the command `ip link add ifb0 numtxqueues 8 type
ifb`. And from what I can tell the kernel default setting is
`numifbs=2`.

This is the intended default as suggested by the kernel maintainers.
Just add a drop-in in /etc/modprobe.d/ if the default doesn't work for
you.

--
Kind regards,
Luca Boccassi

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEErCSqx93EIPGOymuRKGv37813JB4FAmXJ6agACgkQKGv37813 JB57BQ//TZm1r/FImguKTgqGMUIUnj0C7hEuhpWKkdYwwQrJ/aC7raExLJPDKDUV sbWX77XNNwhoNDkVfcPV2HP8LSIfyYstSkouAuN5kHwHGOE6BKiNGP9oPIOjxlFq aroGvCaNkEObYmYDD1XL3T0vVPTau+63SRi5ZVnqOpNlsdWhoqaAmwd7nt4kjMqb CZHh88bK8v2FsMrHZr0A3zLTJ0MlbvQezdCCThJ4y2blhkl50QLpgLRtrzGxiJjw YeLJLxZBii9DTV4m672dk/0yn5zA4a8RqLsGNDmPphoRVsBA9ncEFjLNbVO+VcsY tT8NxhqlBlADunclx/Jby414Lq7f3HNl5Sea8aDKdzvHj0rBYBeU7Xct++85jcPb JEkJcnKPKxxBosmWhenqaNAw3Id27IOSvvxyTTFN2MrMh0V2kpUYAOO4Dexz+1Iy f/VCO3Gc3kDVAFe2RNro09nHUS5+MOFCyfu/zymDdLLfXc2PealtWEgt91lfe8et Ovo7OnjqXzlV656589UspJd+gObbO2B9d+ihAdm9WjBYrw2nIXqsdnTRXR7nOnQS jthYhxZdMiMhuEOtzGWDVLj9iVdfUa5gU0Fz2jJ/bjB4cQMOLfVjXog14ye4fqPE uWfimN05/qdzso2VXU7vqBpIR0Qtyfpm6rK+H8xjDPRYnhl73Gs=
=ARPj
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Ok, then I will stick with my workaround.

Although I don't think defaults like this really should change within a
stable release, and certainly not without a notice about in in the
changelog or NEWS file.

/Andreas

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)