Re: Another Network Manager Stupidity: Swapping eth0 and eth1

[Jon Escombe <lists dresco co uk>]

Yeah, it's actually udev that's swapping the device names (happens to me 
too), depending on the order they get initialised. Guess the 'usual' 
network scripts may already have had some magic to deal with this...

I've not tried it myself, but you can create new udev rules to lock the 
mac address to a specific interface name. There's a good example here -  
http://www.debianhelp.co.uk/udev.htm

HTH,
Jon.


Darren Albers wrote:
> I don't think this is Network Manager, it does not touch that as far 
> as I am aware of.  I have seen this problem in Ubuntu and I think it 
> was a bug in hotplug that caused it to swap.  The bug was filed in 
> Launchpad.net <http://Launchpad.net> so maybe if you can find it there 
> you will find more information and a possible fix for Fedora?
>
> On 5/9/06, *Charles Curley* < charlescurley charlescurley com 
> <mailto:charlescurley charlescurley com>> wrote:
>
>     I have just found what may be another Network Manager (NM)
>     stupidity. I have two NICs on my laptop
>     (http://www.charlescurley.com/Lenovo.R51.html) running Fedora Core
>     5. One is a wired Ethernet interface, the other a wireless Ethernet
>     interface. In system-config-network, I have anchored eth0 and eth1 to
>     specific MAC addresses.
>
>     I recently switched from using the usual configuration tools to NM. I
>     just found out is that NM seems to be ignoring that MAC address
>     anchoring. It has swapped eth0 and eth1. As a result of this the
>     firewall defined by firestarter does not work, and as a result of that
>     my system is wide open and has been for several days.
>
>
>