Network Manager was unable to connect to a WLAN with a hidden SSID
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
I know there are a couple of bugs filed regarding this issue, but none for Ubuntu 9.04.
My home WLAN does not propagate its SSID.
With Jaunty 64bit, I was not able to connect to it using the Networkmanager Applet in Gnome.
I had to modify my WLAN router, so that it now sends the SSID. This way, Network Manager was able
to connect to the WLAN.
About my network device:
lspci -v reports:
02:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
Subsystem: Intel Corporation Device 1101
The version of Network manager is 0.7.1~rc4.
If this bug is a duplicate, please close it.
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
IfupdownConfig:
auto lo
iface lo inet loopback
MediaBuild: Ubuntu 9.04 "Jaunty Jackalope" - Beta amd64 (20090324)
NonfreeKernelMo
Package: network-manager 0.7.1~rc4.
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
Uname: Linux 2.6.28-11-generic x86_64
Same here. My wireless was working in 8.10 with router set up to hidden SSID, WPA2 Personal, TKIP & AES. Now I can only connect to WLAN if the router is set up to broadcast SSID.
When SSID is broadcasted, I get the following in my wpa_supplicant.log
CTRL-EVENT- SCAN-RESULTS SCAN-RESULTS CONNECTED - Connection to 00:21:91:d4:14:bd completed (auth) [id=0 id_str=]
Trying to associate with 00:21:91:d4:14:bd (SSID='martian' freq=2412 MHz)
CTRL-EVENT-
Associated with 00:21:91:d4:14:bd
WPA: Key negotiation completed with 00:21:91:d4:14:bd [PTK=CCMP GTK=TKIP]
CTRL-EVENT-
If I tell the router to stop broadcasting SSID then I get the following line DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-
and the connection is dropped. After that there is no way to connect to wireless, and after first unsuccessful attempt the Network Manager simply stops trying and does nothing in response to try to connect to hidden network.
wpa_supplicant.log file is being filled will the "CTRL-EVENT- SCAN-RESULTS" lines.
Same events reflected in syslog:
1. While SSID is being broadcasted
May 11 13:20:08 mars kernel: [ 271.356066] wlan0: authenticate with AP 00:16:ca:f5:31:41
May 11 13:20:08 mars kernel: [ 271.507094] wlan0: authenticated
May 11 13:20:08 mars kernel: [ 271.507108] wlan0: associate with AP 00:16:ca:f5:31:41
May 11 13:20:08 mars kernel: [ 271.525979] wlan0: RX AssocResp from 00:16:ca:f5:31:41 (capab=0x421 status=0 aid=2)
May 11 13:20:08 mars kernel: [ 271.525989] wlan0: associated
2. The router is told to stop broadcasting SSID
May 11 13:20:08 mars kernel: [ 271.526756] wlan0: disassociating by local choice (reason=3)
May 11 13:25:56 mars kernel: [ 619.714296] wlan0: deauthenticated
The connection is then dropped. Attepts to connect to now hidden network with Network Manager produce the following syslog entries:
May 11 18:36:50 mars NetworkManager: <info> Activation (wlan0/wireless): connection 'martian' has security, and secrets exist. No new secrets needed.
May 11 18:36:50 mars NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
May 11 18:36:50 mars NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
May 11 18:37:50 mars NetworkManager: <info> Activation (wlan0/wireless): association took too long.
May 11 18:37:50 mars NetworkManager: <info> (wlan0): device state change: 5 -> 9
May 11 18:37:50 mars NetworkManager: <info> Activation (wlan0) failed for access point (martian)
May 11 18:37:50 mars NetworkManager: <info> Activation (wlan0) failed.
May 11 18:37:50 mars NetworkManager: <info> (wlan0): device state change: 9 -> 3
May 11 18:37:50 mars NetworkManager: <info> (wlan0): deactivating device (reason: 0).
To date, I cannot establish connection to hidden wireless network. Please let me know if I can be of any further assistance to fix this nasty bug. Cannot beleive it that Ubuntu is being released with a MAJOR bug like this!