Written by gmendoza the 26 Apr 09 at 23:47.

As described in my bug report / enchancement request on NM's bugzilla tracking system:

http://bugzilla.gnome.org/show_bug.cgi?id=580018

1.) I'd love for NetworkManger to use priorities that can be managed for both
system wide and user specific connection profiles.

For example...

If a user has two or more available wireless networks defined, one could always
be given preference for an automatic connection. This priority could be a
numeric value, and NM should compare the priorities across all network types.
e.g. A wireless connection could be given priority over a wired connection.

2.) Along with priorities, there should also be a concept of preemption or
automatically re-connecting to a more preferred network based on certain
classifications of events.

For example...

As described in my bug report / enchancement request on NM's bugzilla tracking system: http://bugzilla.gnome.org/show_bug.cgi?id=580018 1.) I'd love for NetworkManger to use priorities that can be managed for both system wide and user specific connection profiles. For example... If a user has two or more available wireless networks defined, one could always be given preference for an automatic connection. This priority could be a numeric value, and NM should compare the priorities across all network types. e.g. A wireless connection could be given priority over a wired connection. 2.) Along with priorities, there should also be a concept of preemption or automatically re-connecting to a more preferred network based on certain classifications of events. For example... A wired or wireless connection is defined as a system profile, and which authenticates the machine using 802.1x before any user logs on. This provides basic connectivity for centralized authentication, etc. But upon user desktop login, a user specific profile can be made to force NetworkManager to preemptively re-authenticate as the user's profile. NetworkManager would then automatically switch back to the system wide profile after the user logs off. Preemptive event classifications could be a number of things: 1. Simply the higher of two or more priorities. 2. Better encryption options WPA2 vs WPA vs WEP vs Open 3. Interactive Desktop Logon / Logoff 4. Successful connection of another network profile. For example, a VPN connection could automatically connect based on the event of a successful connection being made to any (specific or non-specific) wired, wireless, or PPPoE connection.

Written by Darwin Survivor the 27 Apr 09 at 11:46.

Windows has a system like what #1 is proposing (though EXTREMELY limited), and I hated being switched to a preferred network when the new connection was only 50%. There should be an option to reduce a connection's priority by 3 (or something) points when the connection starts to drop.

Windows has a system like what #1 is proposing (though EXTREMELY limited), and I hated being switched to a preferred network when the new connection was only 50%. There should be an option to reduce a connection's priority by 3 (or something) points when the connection starts to drop.

Written by Psycho_zs the 28 Apr 09 at 05:11.

When click on specific network, it just turns this one network on/off, and does not act on its own.

When click on specific network, it just turns this one network on/off, and does not act on its own.

Written by cybert the 10 May 09 at 11:18.

There should be a button in the wireless-login-window
that gives you the possibility to say:

"Don't try this network again!"

So you don't have to disable your network every time,
or to click 25 times "break off" every time,
if there is no network you want to get in.

There should be a button in the wireless-login-window that gives you the possibility to say: "Don't try this network again!" So you don't have to disable your network every time, or to click 25 times "break off" every time, if there is no network you want to get in.

Written by kpeiruza the 10 May 09 at 23:34.

IMHO it's a nice feature for users and a headache for sysadmins.

When doing network testing, Network Manager interfers into normal operation of tools such as airmon, tcpdump.... with wireless and ethernet, also while trying to manually setup new ip's and so on. As these are standard Ubuntu packages, it's really frustrating to see how they don't work at all...

Why can't I use my Ubuntu Desktop to make networking tests or clustering experiments?

It's pretty common to listen sysadmins blaming NM for the weird behaviour. It's really scary to realize iwconfig or tcpdump don't work anymore :S

It gets too tricky to get it ready to sniff into a wire, change an IP or do whatever we learned to do and isn't possible any more!!!!

This solution should keep current settings, so, it also implements solution #3.

Add a button, link, menu, whatever wherever, but make it visible and easy to completly shut down Network Manager.

Bring us the choice of the command line back!

IMHO it's a nice feature for users and a headache for sysadmins. When doing network testing, Network Manager interfers into normal operation of tools such as airmon, tcpdump.... with wireless and ethernet, also while trying to manually setup new ip's and so on. As these are standard Ubuntu packages, it's really frustrating to see how they don't work at all... Why can't I use my Ubuntu Desktop to make networking tests or clustering experiments? It's pretty common to listen sysadmins blaming NM for the weird behaviour. It's really scary to realize iwconfig or tcpdump don't work anymore :S It gets too tricky to get it ready to sniff into a wire, change an IP or do whatever we learned to do and isn't possible any more!!!! This solution should keep current settings, so, it also implements solution #3. Add a button, link, menu, whatever wherever, but make it visible and easy to completly shut down Network Manager. Bring us the choice of the command line back!

Written by cyberix the 18 May 09 at 15:41.

From time to time I need multiple network connections. The most typical use case would be that I need wireless for connecting to the Internet, but I'd simultaneously need to reach some computer over ethernet. Or the other way around.

This does not solve the whole problem, but Mac OS X seems to be able to handle this. At least in a case where you use Internet over wireless and connect two computers to each other directly with an ethernet cable.

From time to time I need multiple network connections. The most typical use case would be that I need wireless for connecting to the Internet, but I'd simultaneously need to reach some computer over ethernet. Or the other way around. This does not solve the whole problem, but Mac OS X seems to be able to handle this. At least in a case where you use Internet over wireless and connect two computers to each other directly with an ethernet cable.