Ubuntu
network-manager package

network device changes from eth1 to eth0

Bug #151522 reported by Benjamin Herbert
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Low
Unassigned

Bug Description

After reboot or suspend to disk the eth1 wireless card changes to eth0.
This renders the configuration for the wifi card useless.

There was no change to the system. Only a reboot.

I think it is the order the system assigns to the two network cards present.. Sometimes it is this way, sometimes the other. This should be made consistent to guarantee a working network... It took me long to figure that out.
A new user would be frustrated.

Revision history for this message
Alexander Sack (asac) wrote :

please reproduce this bug and attach your /var/log/syslog.

Changed in network-manager:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Benjamin Herbert (benherbert) wrote :

Oct 18 20:11:05 xubuntu-desktop kernel: [ 23.358339] zd1211rw 3-3:1.0: firmware version 4605
Oct 18 20:11:05 xubuntu-desktop kernel: [ 23.400325] zd1211rw 3-3:1.0: zd1211 chip 0ace:1211 v4330 high 00-11-f6 RF2959_RF pa0 -----
Oct 18 20:11:05 xubuntu-desktop kernel: [ 23.403050] zd1211rw 3-3:1.0: eth0

I guess this is the place, but see also the attachment.

A few words about my configuration:

I have an internal network interface which is normally connected to an internal LAN, this is eth0.
I also have a USB network wifi card on eth1 (via udev I renamed it to wlan1), I am connected to a WPA access point with wpa_supplicant. The configuration is for wlan1.

What happens now is, that my eth1(usb wifi) is somehow detected as eth0 as stated above...
This renders the configuration file wrong.

I don't know where to start fixing this. Is it a kernel problem in detecting the device in a wrong/nonconsistent order?

After a reboot, the order is correct again.

Revision history for this message
Benjamin Herbert (benherbert) wrote :
Leann Ogasawara (leannogasawara)
Changed in network-manager:
status: Incomplete → Confirmed
Revision history for this message
Benjamin Herbert (benherbert) wrote :

I deinstalled network-manager and still have this problem... I guess perhaps udev causes this?

Revision history for this message
jgcb (jens-g) wrote :

I have the same problem on an ubuntu 8.04 LTS 64 Bit Linux, kernel version: 2.6.24-21-generic.
The PC has two NIC interfaces, one onboard and another one as PCI-E Card.
Sometimes the onboard NIC becomes eth0 and the PCI-E NIC eth1 and sometimes round versa.
Resetting and configuring the network by hand after booting is not possible because the machine is a diskless Client which mounts its root filesystem over NFS. On a network reset the root filesystem will get lost.
So how can I set fixed device names for the NIC interfaces in a very early stage of booting?

Revision history for this message
Alexander Sack (asac) wrote :

you have to force the name in udev i think. one more reason why using not-fixed interface names is a bad idea. anyway, not a network-manager bug.

Changed in network-manager:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.