fai1...@macrotex.net writes: > I am already using that patch. The problem seems to be that the altname > returned by "ip link show eth0" in 30-interface is "enp11s0" and hence > that is the filename what 30-network puts into /etc/network/interfaces.d, but > when the new system boots the name in /sys/class/net is "ens192".
> Why is there this mismatch? Is it an issue with bullseye itself? Maybe "ip link show" can't really be trusted here... There is a documented priority list[1] and the slot based name (e.g. ens192) is preferred over the path based name (e.g. enp0s0). It seems the path based name is used when booting the NFSROOT while the slot based name is used when the machine is rebooted after installation. To me that looks like a problem with the NFSROOT like missing kernel modules or libraries. Maybe Bullseye really has changed more than previous releases in this area? [1] https://wiki.debian.org/NetworkInterfaceNames -- Stefan
