[gutsy] network-manager tries to use wrong essid
Bug #125965 reported by
Martin Uecker
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: network-manager
Somehow network-manager ( 0.6.5-0ubuntu7) started to hang while connecting to my home network.
After checking with iwconfig I found out that the essid was set to some different network while the
wireless key was correctly set. The gconf-key are correct, Manually changing the essid with
iwconfig allows the network-manager to proceed.
Revision history for this message
| Jamie Lokier (jamie-shareable) wrote | #1 |
Revision history for this message
| Alexander Sack (asac) wrote Re: [Bug 125965] Re: [gutsy] network-manager tries to use wrong essid | #2 |
Revision history for this message
| Alexander Sack (asac) wrote | #3 |
| Changed in network-manager: | |
| status: | New → Fix Released |
To post a comment you must log in.
I would like to confirm I see exactly the same. I was about to report it as a separate bug.
My wireless device is an IPW3945.
This morning, I booted the laptop afresh (not from suspend). Shortly after booting, the system popped up a dialog asking for my Keyring passphrase, which I entered correctly. Then network-
It didn't connect quickly, so I looked with "iwconfig eth1" and it showed the ESSID as "belkin54g", which is a neighbour's WLAN.
It wasn't a brief glitch: the applet continued to show "christopher", but iwconfig continued to show "belkin54g".
By the way, "christopher" is encrypted with a 26-digit hex key; "belkin54g" has no key, but it usually doesn't respond to DHCP.
For a minute or so it failed to get a connection, then gnome-network-
The applet continued to show it's connecting to "christopher", and iwconfig continued to show it's ESSID as "belkin54g"....
Clicking on "christopher" in the applet didn't change the output of iwconfig. Clicking on a different WLAN, then back to "christopher", didn't change it either. Disabling wireless using right-click on the applet, then reenabling it, didn't change it either.
Eventually I did "iwconfig eth1 essid christopher" from the command line. Then the dialog for WPA/WEP key appeared again, I entered the key, and it connected within a few seconds.
This often happens, but not every time. Sometimes it just connects without a problem.
Some more information which might be useful: iwlist eth1 scanning typically shows "belkin54G" and one or two other access points, but not "christopher", for a minute or two. Despite the short list from iwlist, sometimes the network-manager applet shows a longer list. The list in the applet is almost always _different_ from the list from iwlist, and the latter changes every few seconds. After doing "iwconfig eth1 essid christopher", "christopher" always appears in the output of iwlist.