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 635294 - Network Manager lacks wifi network ordered preference
Network Manager lacks wifi network ordered preference
Status: RESOLVED DUPLICATE of bug 580018
Product: NetworkManager
Classification: Platform
Component: Wi-Fi
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Dan Williams
: 405638 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-11-19 19:21 UTC by Silivrenion
Modified: 2012-07-26 23:41 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Silivrenion 2010-11-19 19:21:12 UTC
Network Manager currently connects to whichever network was last used. This is problematic -- Network Manager needs a prioritized connection list.

The expected behavior is prioritized connection. Given two access points, one being a small home network, and the other being a large wide area wifi, Network Manager should be able to be set to connect to the small home network when within range, and the wide area wifi when not in range of the home wifi. Using the current configuration, users must manually connect to their home wifi when within range if they use other access points in the day.

Windows operating systems accomplish this by using an ordered list, where the more preferred access points are at the top of the list, and will always be connected before the ones at the end of the list.
Comment 1 Chris Wilson 2011-11-15 13:11:24 UTC
This issue is currently being tracked downstream in Ubuntu https://bugs.launchpad.net/network-manager/+bug/390243

Has there been any discussion on implementing this?
Comment 2 Pavel Simerda 2012-07-25 11:20:47 UTC
It seems to be still the case with 0.9.4.
Comment 3 Pavel Simerda 2012-07-26 15:41:37 UTC
*** Bug 580018 has been marked as a duplicate of this bug. ***
Comment 4 Pavel Simerda 2012-07-26 15:42:54 UTC
*** Bug 405638 has been marked as a duplicate of this bug. ***
Comment 5 Pavel Simerda 2012-07-26 23:41:23 UTC

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