Re: Discussion? New names of betwork devices
On 3/22/19 9:06 AM, Hans wrote:
> since some time the names for network devices have changed. So its is no more
> "ethX" , but "enp1s10" or similar or "wlan0" and now "wlp5s0". You know, what
> I mean.
Interesting that this came up this morning. I'm on Buster.alpha5. I
tried to relabel my Ethernet interfaces the eth<n> names a few days ago.
It didn't seem to work, so I tried to undo everything I'd done. This
morning, after another reboot, it came up with the eth<n> names.
The powers that be are calling my Ethernet devices enp6s0 and enp7s0. I
guess enp (EtherNet Port) is OK. But 6 and 7 aren't. There are only two
of them, and numbers on my computers don't start at 6.
Another suggestion:
The front panel of my Juniper firewall has a row of Ethernet ports
across it. It calls all of those ethernet0/<n>. Ethernet ports in the
plugins in the back start at ethernet1/<n>.
Eth sounds good to me, as long as nothing non-Ethernet is labeled eth.
But Juniper's naming algorithm makes a lot of sense. The connectors on
the motherboard could be called eth0<n>. And added boards could be eth1,
2, 3, etc.
> This is made by the kernel.
Not in Buster.alphs5, it ain't. The naming is quite complex, and there
are several files that've been chattr'ed so they cant be changed.
> However, I discovered many packages, where are still the old names
> preconfigured with the old names.
Change them to check the Ethernet port labels? I suspect that'd be
fairly easy for the Debian maintainers.
But udev can do all this well and nicely, if people'd just leave it
alone and let it do its job. And make sure things use the correct device
labels.
--
Glenn English
Reply to: