networks with multiple access points roaming fails

[Mike O'Connell]

Binary package hint: network-manager

When connecting to wireless networks with multiple access points with the same SSID, the nm daemon repeatedly tries to associate. Generally the connection will only last a minute or two. Both the nm-applet and knetworkmanager (the new kde4 version) front ends have the same issue.

The syslog reads as follows:
09/04/09 04:26:43 pm michael-laptop wpa_supplicant[3114] CTRL-EVENT-CONNECTED - Connection to 00:06:5a:80:52:ac completed (reauth) [id=2 id_str=]
09/04/09 04:26:43 pm michael-laptop NetworkManager <info> (wlan0): supplicant connection state: scanning -> associated
09/04/09 04:26:43 pm michael-laptop NetworkManager <info> (wlan0): supplicant connection state: associated -> completed
09/04/09 04:26:43 pm michael-laptop kernel [44895.225326] wlan0: RX ReassocResp from 00:06:5a:80:52:ac (capab=0x31 status=0 aid=28)
09/04/09 04:26:43 pm michael-laptop kernel [44895.225329] wlan0: associated
09/04/09 04:26:45 pm michael-laptop NetworkManager <debug> [1252099605.002484] periodic_update(): Roamed from BSSID (none) ((none)) to 00:06:5A:80:52:AC (Private)
09/04/09 04:27:12 pm michael-laptop wpa_supplicant[3114] CTRL-EVENT-SCAN-RESULTS
09/04/09 04:27:12 pm michael-laptop wpa_supplicant[3114] Trying to associate with 00:06:5a:80:52:ac (SSID='Private' freq=2432 MHz)
09/04/09 04:27:12 pm michael-laptop wpa_supplicant[3114] Association request to the driver failed
09/04/09 04:27:12 pm michael-laptop wpa_supplicant[3114] CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
09/04/09 04:27:12 pm michael-laptop NetworkManager <info> (wlan0): supplicant connection state: completed -> associating
09/04/09 04:27:12 pm michael-laptop NetworkManager <info> (wlan0): supplicant connection state: associating -> disconnected
09/04/09 04:27:15 pm michael-laptop NetworkManager <debug> [1252099635.003009] periodic_update(): Roamed from BSSID 00:06:5A:80:52:AC (Private) to (none) ((none))
09/04/09 04:27:17 pm michael-laptop wpa_supplicant[3114] Authentication with 00:00:00:00:00:00 timed out.
09/04/09 04:27:17 pm michael-laptop wpa_supplicant[3114] Failed to initiate AP scan.
09/04/09 04:27:17 pm michael-laptop NetworkManager <info> (wlan0): supplicant connection state: disconnected -> scanning
09/04/09 04:27:18 pm michael-laptop kernel [44930.289750] wlan0: authenticate with AP 00:06:5a:80:52:ac
09/04/09 04:27:18 pm michael-laptop kernel [44930.291215] wlan0: authenticated
09/04/09 04:27:18 pm michael-laptop kernel [44930.291217] wlan0: associate with AP 00:06:5a:80:52:ac
09/04/09 04:27:18 pm michael-laptop wpa_supplicant[3114] Associated with 00:06:5a:80:52:ac

But subsequent DNS lookups fail. Tried removing and re-inserting the ath5k module, restarting the NetworkManager daemon, etc... Clicking connect on the network will reconnect, only to roam to (none) (none) later.

Running the latest karmic packages.

[Alexander Sack (asac)]

dupe of bug 291760 ... due to background scanning. since the fix on driver side appears at least in reach, i am not sure if we should still invest what it takes to make user experience good without background scanning.

[Alexander Sack (asac)]

maybe you can configure a fixed bssid for your connection to make the symptoms less severe (not suggesting as a workaround/solution, just curious).

[Jason Cipriani (jason-cipriani)]

2012, Ubuntu 11.10, still can't establish a reliable connection on networks with multiple APs. Immediately after connection dmesg states deauthenticated for reason 2 (authentication no longer valid). Network manager constantly prompts for password. No trouble establishing connections to single AP networks.

[Arnab Roy (arnabroy)]

Same issue here ...if you strong signal from 2 or 3 AP's in different channels...you are in trouble straight away! ...Can this be give some importance I have tried older ubuntu release and have the same issues