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 706496 - Network Manager should connect to strongest network after resume
Network Manager should connect to strongest network after resume
Status: RESOLVED DUPLICATE of bug 593654
Product: NetworkManager
Classification: Platform
Component: Wi-Fi
unspecified
Other All
: Normal enhancement
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-08-21 13:22 UTC by Zygmunt Krynicki
Modified: 2018-12-28 16:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Zygmunt Krynicki 2013-08-21 13:22:26 UTC 
I'm using my laptop with several different wireless networks. They are overlapping a little so I can often see two networks, one with very strong signal and another one with a medium to weak signal.

When I move my laptop I close the lid to suspend it. When I resume my laptop I'm almost always re-connected to the same network I was using before, one that has very weak signal by now.

I'd like network manager, upon resume, to connect to the strongest known network available.
Comment 1 Pavel Simerda 2013-08-21 18:00:54 UTC 
I'm in a different situation. I'm using a specific network only when I'm downstairs in the pub or when my network has problems and otherwise I don't want the network to be autoconnected. So I always choose it manually if I want it, but otherwise I always prefer my home network.

Therefore while switching the behavior may help a specific group of people, it would badly affect another (possibly much larger one).
Comment 2 Matthew Paul Thomas (mpt) 2015-01-06 15:25:24 UTC 
This looks like a duplicate of bug 593654.
Comment 3 Thomas Haller 2015-01-06 15:34:57 UTC 
(In reply to comment #2)
> This looks like a duplicate of bug 593654.

I agree. The special case of "after resume" is not something that NM understands.

NM is just thinking "I want to autoconnect. Which connection to choose"

Handling "after resume" specially would be possible. But up to now there isn't even a consensus what is the best behavior in the general case.


Closing as duplicate

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