[SOLVED] udev network device name

gtwrek · Last edited by gtwrek on Thu Dec 02, 2021 5:42 pm; edited 1 time in total

The instructions here:
https://wiki.gentoo.org/wiki/Eudev/Network_device_names

That allows us to keep the traditional "eth0", "eth1",etc. network names has suddenly stopped working for me with a recent world update.

I think the machine in question was doing the eudev-> systemd-udevd migration at the time.
But after this world update, and a reboot, my network was gone..

This is especially frustrating as many of my gentoo machines are headless servers with just a sshd connection enabled - so network gone, means a difficult to debug problem.

I checked for the existance of the /etc/udev/rules.d/80-net-name-slot.rules file - it's still there.
But, no "eth0" device - I get the new fangled /dev/enp0s3 instead.

How does one re-enable this "stop messing with my network names" part of udev?

NeddySeagoon · Posted: Wed Dec 01, 2021 9:13 pm Post subject:

dtwrek,

Add

sam_ · Developer Joined: 14 Aug 2020 Posts: 1678

I've also updated the page you linked to refer to the newer instructions here (see bug 827937 too).

gtwrek · Posted: Thu Dec 02, 2021 12:40 am Post subject:

Well, I think I've figured out *some* of what's going on.
To keep the normal network names, there's three methods:

Method 1 works with eudev and certain older versions of udev. (As I understand things eudev was forked from an early version of udev, so this make sense)
Method 2 works with current udev.
Method 3 (currently recommended?) should work past some xxx.xxx kernel version.

I'm still puzzled as to why udev is now being pulled in for me. I've been using eudev forever, and I thought we had until Jan 1, 2022 until it was formally deprecated.

But in any event I think some more text to the enews might be called for, for those of use migrating from eudev to udev. Dropping off the network after a reboot from a world update is a very frustrating experience.

sam_ · Developer Joined: 14 Aug 2020 Posts: 1678

Hu · Moderator Joined: 06 Mar 2007 Posts: 21607

2022-01-01 is the date on which the news said eudev would be retired and removed. I interpret that as meaning that on or about that date, emerge --pretend --verbose sys-fs/eudev will begin reporting "No such package". This gives users a window during which they could copy the last version of eudev into an overlay, if they are determined to continue using it instead of switching to udev.

gtwrek · Posted: Thu Dec 02, 2021 5:42 pm Post subject:

Thanks Sam, and Hu. Sam - your edits to the enews message and the udev message are great. I think that should cover things.

Hu, yes rereading the original enews, it mentioned 2022-01-01 as the removal but 2021-10-01 as the mask. I'd really not consider the difference between the two. And it appears the 2021-10-01 mask was delayed to sometime in the last few weeks. This is what triggered my conversion from eudev->udev and the resulting network naming problems note in this thread.

I think I'm ok with moving forward with updating the rest of my machines, now that I understand what's happening.

Thanks all for the help.

sam_ · Developer Joined: 14 Aug 2020 Posts: 1678

figueroa · Posted: Fri Dec 03, 2021 4:29 am Post subject:

Just to cover all of the bases:
1. I created a symlink "80-net-name-slot.rules -> /dev/null" on April 2, 2013
2. I created a symlink "80-net-setup-link.rules -> /dev/null" on May 10, 2014.
3. I also have the line GRUB_CMDLINE_LINUX="net.ifnames=0" in /etc/default/grub

ADDED: On my newer main desktop machine, I use my own unique network names with a udev rule that was originally done because of a failing built-in NIC.

gtwrek · Posted: Fri Dec 03, 2021 5:08 am Post subject:

Jaglover · Posted: Fri Dec 03, 2021 5:30 am Post subject:

I do it just one way, I have "net.ifnames=0" in kernel builtin command line.