[gutsy] network device name change after Gutsy upgrade, suddenly no/intermittent network

Bug #155603 reported by James
2
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: network-manager

Hi

I upgraded from Feisty to Gutsy via the release candidate then to Gutsy stable on 18/10.
I noticed the network devices changed names from eth0 to eth1 and wlan0 to wlan1 after the upgrade, which I think is something to do with udev and devices being imported from the deprecated iftab file

Yesterday (22/10) both wireless and cable devices suddenly stopped working. I have been able to get wireless working again by manually tinkering with various networking files but cable refuses to come up.

The things that happened yesterday:
* upgrade to latest Gutsy updates (including an updated linux-image according to Adept)
* an acpi suspend failed, although it had been working with Feisty and Gutsy pre 22/10

Networking seemed to fail after that.

Various things that have happened since then:

* Manually bringing up and down the interfaces caused errors such as:
Ignoring unknown interface eth1=eth1.
Ignoring unknown interface wlan1=wlan1.

* Neither device gets an IP from the router via DHCP. I have no idea what generates these messages.
* Network Manager sometimes detects the device and other times not. When it does detect the cable device it deactivates it immediately. Sometimes this happens for the wireless device as well.
* MAC addresses remain the same (no hardware changes)
* Manually updating udev rule and interfaces file to get a network device
* KNetworkManager shows a "wired device" eth0 with correct MAC address but is greyed out.

I manually edited the udev file to use the device names eth0 and wlan0 then restarted networking and NetworkManager, the wireless device is the only one that works (and only sometimes). I I try to manually bring up the cable device I now get the "Ignoring unknown interface eth0=eth0"

I will attach some of the networking files for this bug, with MAC addresses removed. They are correct for the devices, the only difference is that the MAC addresses created by udev are lowercase whilst those reported by ifconfig are uppercase (I don't think that is an issue).

At the moment I have no cable network device and wireless is intermittent.. I'm wondering i this affects others as well .. it is a bit of a showstopper for me and I'm pretty sure if it happens to someone with less technical knowledge than my simple tech skills it'll be a complete WTF.

System: Kubuntu 7.10 fully up to date. Dell Inspiron 8600, 1.24 Gig RAM. Wireless uses ndiswrapper because BCM4309 doesn't work with restricted drivers.

Any help appreciated
James

Revision history for this message
James (james-ellis-gmail) wrote :

networking tools output attached

Revision history for this message
James (james-ellis-gmail) wrote :

udev rules attached

Revision history for this message
James (james-ellis-gmail) wrote :

udev manual changes

Revision history for this message
James (james-ellis-gmail) wrote :

interfaces file attached

- on the network renaming - it seems half the system thinks the devices are name <device>0 while the other half is using <device>1 ? I'm unsure why.

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi there
do you still experience this issue with the current version of the application?, could you please try to reproduce this using the live environment of the Desktop CD of the development release - Hardy Heron.

Thanks in advance

Changed in network-manager:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

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

Other bug subscribers

Remote bug watches

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