| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 19 Aug 2009 21:41:14 -0700
From: Bryan Kadzban <bryan@...zban.is-a-geek.net>
To: Jordan_Hargrave@...l.com
CC: netdev@...r.kernel.org, linux-hotplug@...r.kernel.org
Subject: Re: PATCH: Network Device Naming mechanism and policy
Jordan_Hargrave@...l.com wrote:
> example udev config:
> SUBSYSTEM=="net", SYMLINK+="net/by-mac/$sysfs{ifindex}.$sysfs{address}"
So say I have two NICs, currently named eth0/eth1, and I keep them using
those names via the current udev MAC address rules. Furthermore, say
that this patch is applied, and so I start using 0.<addr0> and 1.<addr1>
in my network configuration, instead of eth0/eth1.
Now, say that on some given boot, these two NICs show up to the kernel
in a different order. I might move them around in the machine (this is,
after all, the point behind using the MAC as the identifier ;-) ), or
one of them might be USB, or something else random changes the order.
With this rule, they're now at 0.<addr1> and 1.<addr0>.
In other words, these names are not actually persistent.
If you get rid of the $sysfs{ifindex}, then this should work. If that
doesn't work for what you're trying to do for some reason, then you can
make another directory of symlinks by-ifindex, and use that; that should
work as well. But coupling the ifindex to the MAC address like this
doesn't work. (In general, coupling any two unrelated attributes when
trying to do persistent names doesn't work.)
Download attachment "signature.asc" of type "application/pgp-signature" (261 bytes)
Powered by blists - more mailing lists