No Networking after Suspend

[Nikolaus Rath]

If the computer resumes from suspend, nm-applet claims that no network devices have been found.

However, I can bring up both eth0 and eth1 up fine manually, so there are definitely interfaces.

[Nikolaus Rath (nikratio)]

Just waiting a little bit longer fixes the bug :-)

[Nikolaus Rath (nikratio)]

Ok, this apparently was a one-time effect. At least I can't reproduce it even after waiting for 1h.

[Nikolaus Rath (nikratio)]

Ok, what I meant was: The bug is valid an the network is gone after suspend. Just to make it clear.

[Richard Hussong (rhussong)]

I also experience this bug periodically. My hardware is an IBM Thinkpad T42, using the built-in wireless device with driver ipw2200. The problem happens often enough to be annoying (especially because the only guaranteed way I have found to fix it is to reboot), but infrequently enough not to be reliably reproducible.

On my machine, networking is usually working perfectly when nm_applet reports "no network devices" after a resume. That is, eth1 (the wireless interface) still has the IP address it acquired from my DHCP server, and all network functions work, except for nm_applet itself. Sometimes, however, the network is dead, possibly because the DHCP lease times out and the DHCP client removes the IP address from the interface.

On one occasion, nm_applet started working again when I removed and reinserted the ipw2200 module, but that fix only worked that one time out of at least 10 attempts. I might somehow have been fooling myself, though I can't think how. I have tried stopping and restarting networking, but that has never done anything useful.

[Simon Hepburn (sth)]

I also had this problem. The solution was to comment out all lines in /etc/network/interfaces except the loopback interface. n-m cannot control already configured interfaces. If that does not cure the problem then you should take a look at #40125 and probably mark this bug a duplicate.

[Nikolaus Rath (nikratio)]

Marking as duplicate.