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 593654 - Auto-connect to networks based on signal strength
Auto-connect to networks based on signal strength
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: Wi-Fi
0.7.x
Other Linux
: Normal enhancement
: ---
Assigned To: Dan Williams
NetworkManager maintainer(s)
: 609535 706496 (view as bug list)
Depends on: 737356
Blocks:
 
 
Reported: 2009-08-31 11:15 UTC by Ian
Modified: 2020-11-12 14:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
nm-applet connecting to downeaster 1 instead of downeaster 2 (2.22 KB, text/plain)
2009-09-14 21:07 UTC, Ian
Details
nm-applet connecting to downeaster 1 instead of downeaster 2 (screenshot) (31.00 KB, image/png)
2009-09-14 21:09 UTC, Ian
Details

Description Ian 2009-08-31 11:15:37 UTC
nm-applet is wonderful in that it Just Works, but there is one aspect that could be improved.

I commute to work via train, and free wifi is provided on-board.  There is a separate wireless AP in each train car, with SSIDs indicating the train name and car number.  On any given day, you will see 3 access points: the one in your train car and the ones in the cars immediately before and after -- with far weaker signals.

Right now, nm-applet connects to the network I connected to most recently (out of the ones in the auto-connect list), which often ends up being a network with a poor signal.  I'd rather it just pick the one with the best signal, since I end up having to do that manually 66% of the time.  

It seems like the cases where your prefered network is NOT the one with the best signal would be the exception and not the rule.  Is there a compelling reason to ignore signal strength when automatically connecting?
Comment 1 Dan Williams 2009-09-03 22:56:17 UTC
Do all the APs have different SSIDs, like "car #1" "car #2" "car #3"?  That would be really odd, and pretty stupid...  Or are they all the same SSID?

If you could run 'nm-tool' next time you encounter this issue and paste the results in here that would be helpful too.  Thanks!
Comment 2 Ian 2009-09-14 21:07:56 UTC
Created attachment 143194 [details]
nm-applet connecting to downeaster 1 instead of downeaster 2

goes with attached screenshot
Comment 3 Ian 2009-09-14 21:09:22 UTC
Created attachment 143195 [details]
nm-applet connecting to downeaster 1 instead of downeaster 2 (screenshot)

goes with other attachment of nm-tool output
Comment 4 Dan Williams 2010-05-10 07:05:22 UTC
*** Bug 609535 has been marked as a duplicate of this bug. ***
Comment 5 Marius Kotsbak 2012-10-18 09:08:08 UTC
It should be configurable. In some other cases the last used network is a better choice than the strongest (e.g. if the last one is usually the strongest, but you happen to have stronger signal at another just when you connected).
Comment 6 Thomas Haller 2015-01-06 15:34:57 UTC
*** Bug 706496 has been marked as a duplicate of this bug. ***
Comment 7 Thomas Haller 2015-01-06 15:46:20 UTC
Bug 737356 proposes a possible solution. Adding bug dependency.
Comment 8 André Klapper 2020-11-12 14:28:00 UTC
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).