Messages in this thread | | | Date | Thu, 14 Dec 2023 15:47:59 +0100 | Subject | Re: Failed to start Raise network interfaces error | From | Ivan Vecera <> |
| |
On 14. 12. 23 15:33, Julia Lawall wrote: > > > On Tue, 12 Dec 2023, Ivan Vecera wrote: > >> >> >> On 12. 12. 23 17:33, Julia Lawall wrote: >>>> Look at 'systemd.net-naming-scheme' man page for details how the interface >>>> names are composed. >>> After booting into 6.7.0-rc4, I have the following in >>> /etc/network/interfaces: >>> >>> # This file describes the network interfaces available on your system >>> # and how to activate them. For more information, see interfaces(5). >>> >>> source/etc/network/interfaces.d/* >>> >>> # The loopback network interface >>> auto lo >>> iface lo inet loopback >>> >>> auto enp24s0f0 >>> iface enp24s0f0 inet dhcp >> >> Just change 'enp24s0f0' in /etc/network/interfaces to 'enp24s0f0np0' > > Hello, > > I don't know if anything can be done about it, but this change introduces > complexities. The people who manage the cluster that I use say that the > name of the network interface should be predictable, which is no longer > the case because it now depends on the kernel version.
In this case, you can configure custom udev rule that will fix the name of the interface... Like:
host ~ # cat /etc/udev/rules.d/70-network.rules ACTION=="add", SUBSYSTEM=="net", DRIVERS=="i40e",\ ATTR{address}=="xx:xx:xx:xx:xx:xx", NAME="enp24s0f0" ACTION=="add", SUBSYSTEM=="net", DRIVERS=="i40e",\ ATTR{address}=="yy:yy:yy:yy:yy:yy", NAME="enp24s0f1"
Regards, Ivan
| |