NetworkManager attempts to connect to unavailable previously connected network when resuming from suspend

[Michael Marley]

Binary package hint: network-manager

On Kubuntu Karmic, if I suspend my computer while connected to a wireless network and then resume it in a different location without that wireless network, the computer will attempt (but fail, obviously) to connect to the same network it used to be connected to. Even after it fails, this network will remain in the list until KDE or the computer is restarted. If another wireless network is available, NetworkManager will still try to connect to the unavailable one, only connecting to the available one after the first attempt fails. My wireless card is a Intel 4965 using the latest driver from compat-wireless, but the problem occurs with all drivers. I have also tried using later upstream versions of the Network Manager plasmoid, but these do not affect the problem.

[Gary Trakhman (gary-trakhman)]

This happened to me on intrepid/jaunty/karmic when I switched to the ath5k driver. I have this problem right now. I don't think it's networkmanager's fault. It seems the previous connected network shows up in the scanning list before real networks do, and then it doesn't go away. I'm on a thinkpad sl300 with atheros ar5007EG, 242x, running 2.6.30-8.

02:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)

[Gary Trakhman (gary-trakhman)]

I was using madwifi before, and i didn't have this problem. One cumbersome workaround is to edit the pm-utils scripts to unload and reload the ath5k module on resume. I did something similar for madwifi for a different issue.

[Michael Marley (mamarley)]

Yes, I thought about doing that, too. I probably will now. The problem might be related to the Full-MAC drivers (like madwifi) vs the Soft-MAC drivers (like ath5k and iwlagn).

[Gary Trakhman (gary-trakhman)]

For once today, this behavior did not occur for me. Using 2.6.30-9 with karmic.

On Fri, Jun 12, 2009 at 3:34 PM, Michael
Marley<email address hidden> wrote:
> Yes, I thought about doing that, too.  I probably will now.  The problem
> might be related to the Full-MAC drivers (like madwifi) vs the Soft-MAC
> drivers (like ath5k and iwlagn).
>
> --
> NetworkManager attempts to connect to unavailable previously connected network when resuming from suspend
> https://bugs.launchpad.net/bugs/379201
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Gary Trakhman (gary-trakhman)]

Seems like it's fixed on the new linux 2.6.31 in karmic. I will keep testing going from school to home.

[Gary Trakhman (gary-trakhman)]

Definitely not a problem for me anymore.

[Pedro Villavicencio (pedro)]

awesome, marking this as fixed.

[Caleb K (ckemere)]

In Karmic, kernel 2.6.31-17 and the wl wireless kernel module (BCM4328), I still have this problem. I find that removing and re-inserting the module (sudo rmmod wl; sudo modprobe wl) enables NetworkManager to work properly, but then the system inevitably freezes within a few minutes.

[Gary Trakhman (gary-trakhman)]

It's not a networkmanager bug

Networkmanager gets its list of connections from the driver, and the driver may report the old one to exist when in fact it doesn't. This is a bug with specific drivers i think.

[Caleb K (ckemere)]

If I use the command "sudo iwlist scanning", which I think uses the driver to report networks, the network in question is _not_ reported.

[PJD (pdoucet)]

sorry to revive an old bug but i have this similar functionality as well. when suspending and moving to a new location, the network manager tries to connect to the old AP until it asks for the password for it. when canceled it will connect to new AP and old APs are gone from the list. I am using the broadcom sta driver. i am running a fully updated lucid with nm version 0.8, though apparently it isnt a nm issue.