Bug 194101

Summary: Network connections should be sorted by priorities
Product: [Unmaintained] knetworkmanager Reporter: m.wege
Component: generalAssignee: Will Stephenson <wstephenson>
Status: RESOLVED UPSTREAM    
Severity: wishlist CC: hbarmeter76
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Unspecified   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description m.wege 2009-05-26 01:06:14 UTC 
Version:            (using KDE 4.2.3)
Installed from:    Ubuntu Packages

The networkmanager applet should offer to sort the configured networks by priorities and connect to the one with the highest priority.
Comment 1 Will Stephenson 2009-08-04 09:04:46 UTC 
The new logic is:

In the main popup, only show connections that are currently connectable - eg there is a configuration for this network and the access point(s) providing this is currently found via scan.  Networks that are configured but where the access point is not present are not shown.

The other, unconfigured scanned networks are in a submenu.  Is this an acceptable prioritisation?
Comment 2 m.wege 2009-08-04 09:17:25 UTC 
Actually I a meant something different. I want the list of already configured networks sorted by priority, no matter if they are available or not. For example I want to put cable network as first. If cable is available then disconnect wireless. If I have the choice between Wireless A and B, B is my choice and so on
Comment 3 Will Stephenson 2009-08-04 09:59:54 UTC 
It's not possible with NetworkManager - the policies the daemon uses are quite inflexible.  The only way you can influence this is to set some connections as 'never default' (which sucks when the cable connection is not present) or change the timestamp on wireless connection B so it is newer than A and NM will prefer it.

It also tries to keep as many 'connect automatically' connections up as possible so the 'disable wireless when connected to cable' idea is not possible.  Sorry.  Please try and convince NM to add client policy control and then I'lll implement it in the KDE UI.
Comment 4 m.wege 2009-08-19 11:03:52 UTC 
Bug has been reported upstream. http://bugzilla.gnome.org/show_bug.cgi?id=580018
Comment 5 Erik Martens 2009-11-28 19:42:18 UTC 
I'd like to add that I experience a related (annoying) behavior (I am not sure if I should submit this as bug or here):

If two wireless networks have been configured with autoconnect, knetworkmanager seems to choose the weaker connection instead of the stronger - this should be fixed. 

Is this also an issue of nm policies? Please advice if I should file a bug report elsewhere. Thank you!