Hi Justin, thanks for the elaborate followup.
Just a few quick answers: > Did the installer give you a 70-persistent-net.rules file? It seems a > bit of a pointless mechanism for hardware like yours... I did not check on the test system (on which I installed bullseye and upgraded to bookworm) if there was one, I assume though that there was none, otherwise I would not expect the network device renaming after the upgrade. On my production machine (initial installation is much older than bullseye), I found one, which still seems to work (since the system still has an wlan0 interface). Judging after etckeeper, I commented the eth line during the upgrade from stretch to buster (I do not recall why though): rd@home:~$ cat /etc/udev/rules.d/70-persistent-net.rules # This file was automatically generated by the /lib/udev/write_net_rules # program, run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single # line, and change only the value of the NAME= key. # Unknown net device (/devices/soc0/soc/2100000.aips-bus/2188000.ethernet/net/ eth0) (fec) # SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address} =="d0:63:b4:00:2b:ac", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" # Unknown net device (/devices/soc0/soc/2100000.aips-bus/2190000.usdhc/ mmc_host/mmc0/mmc0:0001/mmc0:0001:1/net/wlan0) (brcmfmac) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address} =="b8:5a:f7:82:aa:c2", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0" rd@home:~$ What I don't understand: Before the upgrade from bullseye to bookworm, this machine still had the eth network interface names, even though the line in /etc/udev/rules.d/70- persistent-net.rules was already commented out. > >> Sure, *if* the change was in bookworm. But if people didn't read > >> the stretch and buster release notes, why would we expect a warning in > >> the bookworm release notes to do any good? > > > > I am also somewhat concerned that users don't read the release notes > > carefully, break their systems. This information should probably be in a > > more prominent place and clearly visible during the upgrade. I liked the > > previous solution better that systems by default continue to use the old > > naming scheme. > Well, systems still do continue to use the old naming scheme, unless > you change your apt sources to point at a new release! And it's > really much easier to change your configuration once to use the new > names than to change your grub configuration and carry that around > forever - or until linux-8.0.0 stops supporting that commandline > parameter, long after you've forgotten you were using it... I fully agree. But it would be much better if I would learn before the upgrade about this change and not get as a surprise a headless system which does not connect to the network anymore after the upgrade. > Personally I have a .link file in /etc/systemd/network to make sure > my machines use consistent names for their interfaces regardless of > their hardware differences, and if you're administrating machines with > different architectures that might well be what you'd want, too. Many thanks for sharing this. For reference, I found an example here: https://wiki.archlinux.org/title/Systemd-networkd#Renaming_an_interface Thanks again Rainer -- Rainer Dorsch http://bokomoko.de/