On Monday, 30.01.2006 at 14:13 +0100, Torquil Macdonald Sørensen wrote:
> >I also had the same problem. It seems to me that udev cannot assign a
> >name to a network device if that name is already taken by another
> >device. Therefore these udev rules only "work" if the assignment
> >happened to be correct anyway and fail if the devices switch names
> >during boot. On my laptop I had a failure rate of about 5-10%.
> >
> >I managed to circumvent this problem by assigning new names to both
> >devices in the udev rules, e.g.
> >
> >KERNEL="eth*", SYSFS{address}="00:00:00:00:00:00", NAME="lan0"
> >KERNEL="eth*", SYSFS{address}="11:11:11:11:11:11", NAME="wlan0"
> >
> >Then I changed /etc/network/interfaces so that it referred to the
> >devices by these new names instead of ethx. Since then the assignment
> >and the subsequent configuration have worked 100% reliable. Of course
> >you have to remember to change to the new names everywhere, for example
> >if you use ifplugd.
>
> Thanks Florian, that's a nice solution. I updated
> /etc/network/interfaces and /etc/shorewall/interfaces, and now
> everything is fine, and it will most likely be so every time I boot.
You might find 'ifrename' a good solution here, too, for what it's
worth.
Dave.
--
Please don't CC me on list messages!
...
Dave Ewart - davee@sungate.co.uk - jabber: davee@jabber.org
All email from me is now digitally signed, key from http://www.sungate.co.uk/
Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92
Attachment:
signature.asc
Description: Digital signature