Comment 24 for bug 92299

Several different machines setup. 4 desktops with feisty currently updated. Using belkin usb 802.11b net adapters. Recognized as wlan0. These adapters were recognized and worked great using knetworkmanager up untill I reported this problem. On that day theupdate broke it.

Main machine is a dell D820 laptop, using Intel 3945. Recognized as eth1. Again it worked great untill that update. I don't know if it was a n-m update or knetworkmanager that broke it?
Here is teh /etc/network/interfaces
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

auto eth0
iface eth0 inet static
address 192.168.14.107
netmask 255.255.255.0
gateway 192.168.14.1

auto eth1
iface eth1 inet static
wireless-essid linksys
address 192.168.14.113
netmask 255.255.255.0
gateway 192.168.14.100

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

I have made no changes to this file, and have not used any static setups. Now in order to get any net to work I use ifconfig, iwconfig, and dhclinet in console. None of the net adapters are recognized by knetworkmanager. The system is up to date as of today.

Interestingly I have another laptop I use for screen projection at the church. When the updates broke all these other machines I stopped updating it so it still works great!

Hope this helps us figure it out!

Mike