Network-manager should prefer 802.11a
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
It seems that network-manager (or maybe network-
We have a large, crowded wireless network with APs supporting both 802.11a/n and 802.11b/g/n.
Sitting directly beneath the AP (output of nm-tool):
*h_da: Infra, 00:26:3E:14:72:02, Freq 2437 MHz, Rate 54 Mb/s, Strength 100 WPA WPA2 Enterprise
h_da: Infra, 00:26:3E:14:72:03, Freq 5180 MHz, Rate 54 Mb/s, Strength 85 WPA WPA2 Enterprise
As you can see the 802.11b/g/n band gets selected. But 802.11a/n would be much better (less clients, less noise, more available frequencies thus less overlapping).
It is not an option to enter the APs by BSSID to prefer 802.11a/n - our university has many APs installed..
| affects: | ubuntu → network-manager (Ubuntu) |
| Mathieu Trudel-Lapierre (cyphermox) wrote | #1 |
| Mathieu Trudel-Lapierre (cyphermox) wrote | #2 |
| Changed in network-manager (Ubuntu): | |
| status: | New → Incomplete |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in network-manager (Ubuntu): | |
| status: | Incomplete → Expired |
With lower signal strength the advantage of using different frequencies is reduced -- note that both are detected running at 54mb/s. Furthermore, whether different frequencies yield less clients, noise, etc. is specific to the environment you're in, so in this case basing the choosing on signal strength makes sense. In many cases different types of connections like this are set up on different ESSIDs.