Re: Debian 10 --> 11 on Dell R740: network interfaces renamed
On 2022-06-14 01:48:16, David Wright wrote: Perhaps calling the new interface naming scheme "predictable" is somewhat overselling it, but "persistent" (a better choice IMHO) was already in use, both in the way quoted above, and as one of the choices for MAC address generation. The changed names are neither predictable nor persistent, so this naming scheme failed, regardless how you call it. I would be glad if I could get some *expected* interface names, at least. The question remains: How comes? Looking at the kernel logging output the interface names were generated as good ol' "eth0", "eth1" and so on. They were renamed into a "persistent" string later by some code on the initrd, as it seems. AFAICT this code is part of systemd/udev. Is this a bug or did this happen on purpose? Regards Harri
Re: Debian 10 --> 11 on Dell R740: network interfaces renamed
On Thu 09 Jun 2022 at 10:42:07 (+0200), Harald Dunkel wrote:
>
> If I have to hardwire the interface names to their Mac address as you
> suggested, then I don't see a significant difference to the old-style
> /etc/udev/rules.d/70-persistent-net.rules we had till Debian 10, except
> that the former was auto-generated and easier to modify.
The autogeneration wasn't always popular. If your network card packed
up and you replaced it with another, suddenly your eth0 configuration
would fall over because the new card's interface became eth1. Or eth2
if there was already an eth1 lurking in the file.
Perhaps calling the new interface naming scheme "predictable" is
somewhat overselling it, but "persistent" (a better choice IMHO)
was already in use, both in the way quoted above, and as one of
the choices for MAC address generation.
Easier to modify? I'd say the INI file syntax is easier to write and
maintain than incantations like:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:13:49:f0:0b:aa", ATTR{dev_id}=="0x0", ATTR{type}=="1",
KERNEL=="wlan*", NAME="wlan0"
Cheers,
David.
Re: Debian 10 --> 11 on Dell R740: network interfaces renamed
On Thu, Jun 09, 2022 at 10:42:07AM +0200, Harald Dunkel wrote: > > If I have to hardwire the interface names to their Mac address as you > suggested, then I don't see a significant difference to the old-style > /etc/udev/rules.d/70-persistent-net.rules we had till Debian 10, except > that the former was auto-generated and easier to modify. Yes, that's correct. It's conceptually the same exact thing we used to do with udev. Only now it has to be done with systemd instead. Because someone decided to change it.
Re: Debian 10 --> 11 on Dell R740: network interfaces renamed
If I have to hardwire the interface names to their Mac address as you suggested, then I don't see a significant difference to the old-style /etc/udev/rules.d/70-persistent-net.rules we had till Debian 10, except that the former was auto-generated and easier to modify. Regards Harri
Re: Debian 10 --> 11 on Dell R740: network interfaces renamed
On Wed, Jun 08, 2022 at 02:17:18PM -0600, Charles Curley wrote: > On Wed, 8 Jun 2022 15:17:04 -0400 > Greg Wooledge wrote: > > > I strongly recommend that you create systemd.link(5) files, one for > > each interface. > > Or just get back the original interface naming scheme. > https://wiki.debian.org/NetworkInterfaceNames#THE_ORIGINAL_SIMPLE_SCHEME On a machine with 6 ethernet interfaces, I doubt this will give stable names either. The original "eth0" scheme is absolutely perfect for a machine with exactly 1 ethernet interface, but becomes unreliable with more interfaces.
Re: Debian 10 --> 11 on Dell R740: network interfaces renamed
On Wed, 8 Jun 2022 15:17:04 -0400 Greg Wooledge wrote: > I strongly recommend that you create systemd.link(5) files, one for > each interface. Or just get back the original interface naming scheme. https://wiki.debian.org/NetworkInterfaceNames#THE_ORIGINAL_SIMPLE_SCHEME -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Debian 10 --> 11 on Dell R740: network interfaces renamed
On 09.06.2022 00:04, Harald Dunkel wrote: Hi folks, after the upgrade to Debian 11 some network interfaces in my Dell R740 got renamed. Before: # lshw -class network -short H/W path Device Class Description /0/2/0 eno1 network Ethernet Controller 10G X550T /0/2/0.1 eno2 network Ethernet Controller 10G X550T /0/3/0 eno3 network I350 Gigabit Network Connection /0/3/0.1 eno4 network I350 Gigabit Network Connection /0/103/0 ens3f0 network I350 Gigabit Network Connection /0/103/0.1 ens3f1 network I350 Gigabit Network Connection After: # lshw -class network -short H/W path Device Class Description === /0/2/0 eno1 network Ethernet Controller 10G X550T /0/2/0.1 eno2 network Ethernet Controller 10G X550T /0/3/0 eno3 network I350 Gigabit Network Connection /0/3/0.1 eno4 network I350 Gigabit Network Connection /0/103/0 enp94s0f0 network I350 Gigabit Network Connection /0/103/0.1 enp94s0f1 network I350 Gigabit Network Connection How comes? AFAIR these predictable interface names had been introduced to get *stable* names, if the hardware is changed. Since it is more likely to get a kernel upgrade than new network hardware I wonder of the predictable names could be made even more predictable? For me the best solution is to manually create .link¹ files for every interface, to name them to something nice, like "ether0" or "wan0". [1] https://www.freedesktop.org/software/systemd/man/systemd.link.html -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄
Re: Debian 10 --> 11 on Dell R740: network interfaces renamed
On Wed, Jun 08, 2022 at 09:04:46PM +0200, Harald Dunkel wrote: > after the upgrade to Debian 11 some network interfaces in my > Dell R740 got renamed. I strongly recommend that you create systemd.link(5) files, one for each interface. Make up some names of *your* choice for each interface (I'm using lan0 etc.), so there's no possibility of a conflict with a name that the system might choose. Assign your names to the interfaces by MAC address. unicorn:~$ ls /etc/systemd/network 10-lan0.link unicorn:~$ cat /etc/systemd/network/10-lan0.link [Match] MACAddress=18:60:24:77:5c:ec Type=ether [Link] Name=lan0 It's the best (possibly the only) way to ensure you get consistent names. The so-called "predictable" interface names are not actually predictable, as you have learned.
Debian 10 --> 11 on Dell R740: network interfaces renamed
Hi folks, after the upgrade to Debian 11 some network interfaces in my Dell R740 got renamed. Before: # lshw -class network -short H/W path Device Class Description /0/2/0eno1networkEthernet Controller 10G X550T /0/2/0.1 eno2networkEthernet Controller 10G X550T /0/3/0eno3networkI350 Gigabit Network Connection /0/3/0.1 eno4networkI350 Gigabit Network Connection /0/103/0 ens3f0 networkI350 Gigabit Network Connection /0/103/0.1ens3f1 networkI350 Gigabit Network Connection After: # lshw -class network -short H/W path Device Class Description === /0/2/0eno1 networkEthernet Controller 10G X550T /0/2/0.1 eno2 networkEthernet Controller 10G X550T /0/3/0eno3 networkI350 Gigabit Network Connection /0/3/0.1 eno4 networkI350 Gigabit Network Connection /0/103/0 enp94s0f0 networkI350 Gigabit Network Connection /0/103/0.1enp94s0f1 networkI350 Gigabit Network Connection How comes? AFAIR these predictable interface names had been introduced to get *stable* names, if the hardware is changed. Since it is more likely to get a kernel upgrade than new network hardware I wonder of the predictable names could be made even more predictable? Old kernel was 4.19.0-18-amd64, new kernel is 5.10.0-14-amd64. /lib/systemd/network/99-default.link is [Match] OriginalName=* [Link] NamePolicy=keep kernel database onboard slot path AlternativeNamesPolicy=database onboard slot path MACAddressPolicy=persistent Every helpful comment is highly appreciated. Harri
