NM cannot change wireless networks

[Melq Rivera]

I have several wireless network available around me and I usually use one --- let us name it WNET A --- to update Ubuntu as it is the fastest and then there is another wireless network --- let us call it WNET B --- that I use to download other stuff as it is slow but has unlimited data. My problem is that I cannot now move from WNET A to WNET B; Ubuntu just won't connect to the other wireless network; it just keeps on sticking to WNET A. I have tried other non-Ubuntu laptops to connect to WNET A and also to WNET B and they can do it without any hiccups...

help urgently requested please...

Cheers!
Melq
:-)

[Tyler Hicks (tyhicks)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Thomas Hood (jdthood)]

Please make an attempt to connect to WNET B and send us the relevant output from /var/log/syslog. Also run "apport-collect 943277". What wireless hardware do you have and what driver are you using?

Any improvement with Ubuntu 12.04?

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

[indigocat (indigocat)]

This still happens on 12.04:
NM sticks to one wireless network, does not switch to another configured network.
Only a reboot fixes this, and for an hour or two; after that time, it becomes impossibe again to switch wireless networks.
I've run apport-collect 943277, results should be attached soon

[Margarita Manterola (marga-9)]

Indeed this still happens with NM in Precise. Usually, just restarting NM is enough, though, no need to reboot the whole machine.

I'm not sure if it's NM's fault or wpa_supplicant's fault. Every time I've experienced this it has been related to networks protected with wpa.

[Margarita Manterola (marga-9)]

Using a new wpa supplicant version seems to fix the issue.

[indigocat (indigocat)]

Not affected by the problem anymore.