7 Aug
2023
7 Aug
'23
8:11 a.m.
tl;dr - fixed. Removed the "/etc/systemd/network/99-default.link" file then
typed "sudo update-initramfs -u" and rebooted as described in the VIRTUAL
MACHINES section of
https://wiki.debian.org/NetworkInterfaceNames#Complications_and_corner_cases
On Sun, 6 Aug 2023, at 23:36, Andy Smith via BitFolk Users wrote:
As far as I'm aware eth0 will be renamed to enX0
unless you have
taken steps in the past to prevent this. So have you done any of the
things described here?
https://wiki.debian.org/NetworkInterfaceNames#How_to_get_it_back
Hi Andy,
Not recently, no. I can't rule out having unwittingly made changes in previous years,
though.
On a bullseye VM this is what udev thinks about my
eth0:
$ sudo udevadm test-builtin net_id /sys/class/net/eth0
<snip
lots-of-details>
and on a bookworm VM this is what it thinks:
$ sudo udevadm test-builtin net_id /sys/class/net/enX0
<snip
lots-more-details>
What does yours say?
"device is missing." :-(
Fixed now, as described in the tl;dr section at the top. There's nothing but comments
in the /etc/systemd/network/99-default.link file, but these comments seem to describe my
situation (and maybe some others over the next few months?) pretty well:
# This machine is most likely a virtualized guest, where the old persistent
# network interface mechanism (75-persistent-net-generator.rules) did not work.
# This file disables /lib/systemd/network/99-default.link to avoid
# changing network interface names on upgrade. Please read
# /usr/share/doc/udev/README.Debian.gz about how to migrate to the currently
# supported mechanism.
Finally, the sysv-rc-conf package was removed - nothing being held back any more:
Yes, you can remove it, it's not being used. It
doesn't have
anything depending upon it either:
Cool. Removed and rebooted without issue - thanks!
Cheers,
jmi