eth* devices (again)
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"
I see now that I never bothered to try to force the firewire to be eth2,
so maybe that's something. But why wouldn't the second rule take care
of my wireless card on it's own?
Anyway, the above rules are NOT in effect on my system at the moment.
Recently (maybe since 8 or so days ago) I see that there is no eth1
device anymore. There is now an eth1_temp device. E.g.
# ip link
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
qlen 1000 link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
3: eth1_temp: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ieee1394 xx:xx:xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff:ff:ff
<snip other devices>
Ugh! What's the deal here? Is there someway I can (or should?) delete
the eth1_temp device and recreate an eth1 device? My wireless device is
now flipping back and forth between eth2 and eth1_temp (on reboots, of
course -- it doesn't change while the system is up).
So I'm wondering if the udev rules aren't quite working (I'm running a
decently recent version of etch), or if I didn't get them quite right.
If I enable the rules again, is there anything I can be looking for in
syslog or the messages file to debug udev?
Thanks,
Rick Reynolds
--
Hey, this is the government. You just can't expect five 9s -- Chief
Justice, on the Gore/Bush election's narrow margin
Reply to: