Bug#1105204: udev: networking broken by interface name change upgrading from bookworm to trixie enp1s0 -> ens1
Emanuele Rocca
ema at debian.org
Tue May 13 11:31:41 BST 2025
Package: udev
Version: 257.5-2
Severity: important
Hi!
We tested a bookworm to trixie update on one of our systems. The host
did not come back online after reboot, and the issue seems to be caused
by the 252 -> 257 systemd update.
The main network interface on the system was named "enp1s0" by systemd
252.36 shipped with bookworm. After upgrading the machine to trixie and
rebooting, the host was unreachable via the network. Logging in via
out-of-bound console it became evident that systemd v257 on trixie chose
a different name for the network interface: "ens1".
After rebooting the machine passing net.naming_scheme=v252 to the kernel
command line, we verified that the interface name went back to "enp1s0".
The important change seems to be that v257 sets ID_NET_NAME_SLOT=ens1,
and *that* is chosen as the interface name to use instead of
ID_NET_NAME_PATH=enp1s0.
Here's the diff of `udevadm test-builtin net_id /sys/class/net/$IFACE`
--- v252.txt 2025-05-12 20:44:42.252702652 +0200
+++ v257.txt 2025-05-12 20:43:50.668953530 +0200
@@ -11,7 +11,7 @@
Loading kernel module index.
Loaded 'libkmod.so.2' via dlopen()
Found container virtualization none.
-Using interface naming scheme 'v252'.
+Using default interface naming scheme 'v257'.
Parsed configuration file "/usr/lib/systemd/network/99-default.link"
Parsed configuration file "/usr/lib/systemd/network/80-vm-vt.link"
Parsed configuration file "/usr/lib/systemd/network/80-container-vz.link"
@@ -20,10 +20,12 @@
Parsed configuration file "/usr/lib/systemd/network/80-6rd-tunnel.link"
Parsed configuration file "/usr/lib/systemd/network/73-usb-net-by-mac.link"
Created link configuration context.
-ID_NET_NAMING_SCHEME=v252
+ID_NET_NAMING_SCHEME=v257
ID_NET_NAME_MAC=enx001b21e7ca26
enp1s0: MAC address identifier: hw_addr=00:1b:21:e7:ca:26 → x001b21e7ca26
ID_OUI_FROM_DATABASE=Intel Corporate
+sd-device: Failed to chase symlinks in "/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/net/enp1s0/of_node".
+enp1s0: Failed to get device of_node, ignoring: No such device
sd-device: Failed to chase symlinks in "/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/of_node".
0000:01:00.0: Failed to get device of_node: No such device
sd-device: Failed to chase symlinks in "/sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/physfn".
@@ -31,10 +33,8 @@
0000:01:00.0: Could not obtain onboard index: No such file or directory
ID_NET_NAME_PATH=enp1s0
enp1s0: PCI path identifier: domain=n/a bus_and_slot=p1s0 func=n/a port=n/a → enp1s0
-sd-device: Failed to chase symlinks in "/sys/class/pci".
-sd-device: Failed to chase symlinks in "/sys/bus/subsystem/devices/pci".
-sd-device: Failed to chase symlinks in "/sys/class/subsystem/pci".
-sd-device: Failed to chase symlinks in "/sys/firmware/subsystem/pci".
+ID_NET_NAME_SLOT=ens1
+enp1s0: PCI slot identifier: domain=n/a slot=1 func=n/a port=n/a → ens1
enp1s0: Could not find USB parent device: No such file or directory
enp1s0: Could not get BCMA parent device: No such file or directory
Unload kernel module index.
More information about the Pkg-systemd-maintainers
mailing list