On Sun, 05 Jan 2025 11:50:31 -0600 aipark <aip...@outlook.com> wrote:
Package: release-notes Severity: minor X-Debbugs-Cc: aip...@outlook.comI updated a staging bookworm VM with VirtIO NIC to trixie and temporarily lost network access because enp6s18 became ens18, and subsequently /etc/network/interfaces 'allow-hotplug enp6s18' no longer functioned. (Weirdly, 'auto' still works.) systemd v257 release notes and man subpage net-naming-scheme show new "PCI slot number is now read from firmware_node/sun sysfs file" and documented 'net.naming_scheme=v255' kernel cmdline reverted the changes back to what it was in bookworm with systemd v252.
So, for a remote system where you don't want the naming scheme to change, would it make sense to add a recommendation to pin it to the systemd version the system was originally installed with?
Say for a bookworm system, you add "net.naming_scheme=v252" to the kernel command line. Then you can dist-upgrade and boot into your new trixie system (including the new kernel).
And at a later point, you can decide to bump net.naming_scheme to v257 at a more opportune time.
Michael[1] https://www.freedesktop.org/software/systemd/man/latest/systemd.net-naming-scheme.html
OpenPGP_signature.asc
Description: OpenPGP digital signature
