Re: 70-persistent-net-rules no longer supported? (Was Re: Document removal of ecryptfs-utils from Buster)
On 2019-07-02, The Wanderer <wanderer@fastmail.fm> wrote:
>> Not even that, it seems (no longer affects systemd).
>
> Have you confirmed that? It seems possible that on a systemd machine,
> things in other packages (such as whatever would provide that
> 99-default.link file, which unfortunately - because it's under /etc/ -
> can't be easily found through 'apt-file search') might still be
> overriding 70-persistent-net.rules, even with this change reverted.
https://github.com/systemd/systemd/issues/11436
https://github.com/systemd/systemd/commit/ed30802324365dde6c05d0b7c3ce1a0eff3bf571
Let's revert, and start with a clean slate. This fixes #11436.
(#11436 being 'network interface is renamed although NAME has been set by
udev rule'.)
Maybe I'm not understanding this (quite possible).
Somebody on an up-to-date Buster could perform Michael Biebl's bug
reproduction test:
To reproduce the issue, create a file /etc/udev/rules.d/70-persistent-net.rules containing
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="<MAC>", KERNEL=="eth*", NAME="lan0"
with the mac address of your ethernet network interface.
Unload the network module (in my case 8139cp), then load it again.
Notice how the interface is properly renamed:
[ 3750.870434] 8139cp 0000:00:03.0 lan0: renamed from eth0
Now run udevadm trigger --action=add
[ 3752.509458] 8139cp 0000:00:03.0 ens3: renamed from lan0
The interface is renamed although a custom NAME has been set.
Sorry if this is noise.
Reply to: