The problem is not so simple: Once I've ordered the list of networks (A, B, C), suppose I'm connected to network A, and nm detects there is no connectivity (i.e. no ping to gateway, or DNS), then it should fallback to network B.
The problem here is how to decide when to go back to network A without interrupting connectivity. 1) The easy way is interrupting it, say, 30 minutes later and check. All connections will be lost. 2) Other possibility is stay on B until it loses connectivity. 3) The hard way, and I guess is not possible yet, is that the NIC and the driver support virtual STAtions, this way it can associate to multiple APs simultaneously. In that case we could even round robin connections and have bandwidth incremented. Regards, Mariano -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/366780 Title: Please provide a mechanism whereby Wi-Fi networks can be prioritized Status in “network-manager” package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager I've got few wifi network profiles. NM connects to 1st available network in alphabetical order. But at my home NM connects to slow and unstable free network and I want to connect to my own wifi router. I suggest to add some priorities to different networks to set the order which network to connect to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/366780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
