Rick Reynolds wrote:
> I've posted about this before and there have been several suggestions --
> none of which have seemed to work. A new wrinkle has recently showed up
> that I thought I would post.
>
> I have eth0 (lan), eth1 (wireless), and eth2 (firewire) defined on my
> system. I've had problems for a few months of eth1 and eth2 swapping
> places (and occasionally even eth0 becoming the wireless). I attempted
> the udev rule strings that have been suggested before, but they didn't
> seem to work -- while my rule was in place wireless became eth2 again,
> for instance. Here are the rules I've used before (anonymized a bit):
>
> KERNEL=="eth*", SYSFS{address}=="xx:xx:xx:xx:xx:xx", NAME="eth0"
> KERNEL=="eth*", SYSFS{address}=="xx:xx:xx:xx:xx:xx", NAME="eth1"
This CANNOT work!
If eth0 is taken by something, you cannot assign it again by such rules, so
all of them will fail.
Give your devices descriptive names:
eth_lan0
eth_wlan0
eth_fw0
Those won't conflict with the names that the kernel chooses, so you do not
conflict.
This applies to whatever method you choose to change the interface name.
HS
--
Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de
oder über pgp.net
PingoS - Linux-User helfen Schulen: http://www.pingos.org
