After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 734545 - Network Manager not connecting to the best signal wifi AP in range
Network Manager not connecting to the best signal wifi AP in range
Status: RESOLVED DUPLICATE of bug 580018
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other Linux
: Normal major
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-08-09 12:31 UTC by asbesto
Modified: 2014-08-11 11:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description asbesto 2014-08-09 12:31:12 UTC 
The method by which network-manager choose to connect to an AP is a little weird: 

instead of choosing the AP with the more powerful signal, he chooses to connect to (i think) the "last" AP, often choosing between two, the one with the poorest signal.

I strongly believe this is really a stupid choiche. What about checking signal level and, after this, connecting automagically to the BEST signal available?
Comment 1 Thomas Haller 2014-08-11 11:49:13 UTC 
Since there is not much control of how to do that, using the least recently used one seems like a good idea. That simple policy is not going to change.

However, there is a bug 580018 that asks for more control over choosing the next autoconnect connection. This bug should be solved in the context of bug 580018.

*** This bug has been marked as a duplicate of bug 580018 ***