network manager should have weighting

Bug #112789 reported by Alan Pope 🍺🐧🐱 🦄
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Wishlist
Unassigned

Bug Description

Binary package hint: network-manager

When in an environment where multiple networks are visible it would be useful to be able to set an order of precedence. This could enable the user to coerce/bias network manager towards one network. This could be achieved with a gconf key with a weight from 1 to 5. In the user interface for network-manager this can be implemented with stars in a similar way to iTunes/Rhythmbox.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Hi Alan, thanks for your suggestion. You might want to suggest it upstream as well for faster up-take: http://www.gnome.org/projects/NetworkManager/

Changed in network-manager:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Motin (motin) wrote :

This bug is very similar to Bug #102555: network-manager-gnome needs a "default network" checkbox

However, it is not a duplicate, as the other report only suggest to have a default network.

I'd prefer weighting.

Revision history for this message
Motin (motin) wrote :

However, I would instead suggest a prioritization based on the order the networks are listed in nm-editor. That would make it easy to rank our most preferred networks.

This would be very easy to implement in the nm-editor interface at least.

A variant based on stars sounds even more user-friendly though. If it is not too hard to implement then why not?

Revision history for this message
Motin (motin) wrote :

I found an even earlier bug #46123 which addresses the same issue. Marked as duplicate.

You should however suggest your idea about the stars as a strategy of implemenation of this feature.

Cheers

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.