NetworkManager prefers slower 11b connection to 11a connection

Bug #586273 reported by Erno Kuusela on 2010-05-27
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Fix Released
network-manager (Ubuntu)

Bug Description

Binary package hint: network-manager

When there are APs advertising the same SSID on both 11a and 11b, NetworkManager picks a 11b AP to associate to when I select the SSID of the network in the toolbar dropdown menu. It should prefer the faster 11a AP.

We have a city/university network with the same ssid, and typically there are many base stations visible.
In our office there are both 11a (54 Mbps/5 GHz) and 11b (11 Mbps/2.4 GHz) connections available
(as shown by iwlist scan, if i run it many enough times - most times it only shows the current association...).

I can make it associate to a 5 GHz AP if I manually create a connection with the BSSID of a nearby 11a AP,
and select that connection via the "Connect to hidden wireless network..." menu item.

This is on Lucid installed and updated today (2010-05-27), amd64 architecture. Hardware is
ThinkPad X200s. The iwlagn identifies the wlan card thusly: "Detected Intel Wireless WiFi Link 5300AGN REV=0x24".
Basestation hardware is Cisco Aironet 1200 with dual (11b & 11a) radios.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: network-manager 0.8-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic
Uname: Linux 2.6.32-22-generic x86_64
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Thu May 27 12:51:12 2010
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
IpRoute: dev wlan0 proto kernel scope link src metric 2 dev wlan0 scope link metric 1000
 default via dev wlan0 proto static
Keyfiles: Error: [Errno 2] No such file or directory
SourcePackage: network-manager

Erno Kuusela (erno-iki) wrote :
Thomas Hood (jdthood) wrote :

Please file this request upstream:

Changed in network-manager (Ubuntu):
status: New → Invalid
Erno Kuusela (erno-iki) wrote :

It's a good idea but I don't think you're supposed to mark upstreamable bugs as invalid. If you want to triage
this bug you can do this:

Changed in network-manager (Ubuntu):
status: Invalid → New
Changed in network-manager:
importance: Unknown → Wishlist
status: Unknown → Confirmed
Thomas Hood (jdthood) on 2012-08-07
Changed in network-manager (Ubuntu):
status: New → Confirmed
Changed in network-manager:
status: Confirmed → Fix Released
Changed in network-manager:
status: Fix Released → Confirmed
Changed in network-manager:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.