Plasma NM should allow to configure wireless networks priority, so that when multiple wireless networks are available the one with the highest priority is selected. This is an old bug, which affected NetworkManager. Finally seems to be solved (on 2014-10-13) as stated in this bug report: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/366780 So now should be possible to add the configuration interface to Plasma-NM to support this feature. Reproducible: Always Steps to Reproduce: 1.Turn on wifi where multiple saved wireless networks are present 2. 3. Actual Results: Plasma-NM connects to the one with the strongest signal (I guess) Expected Results: Plasma-NM connects to the user preferred network References: https://bugzilla.gnome.org/show_bug.cgi?id=580018 https://bugs.kde.org/show_bug.cgi?id=194101
I see, it would be easy to implement this, but given that this feature is introduced in NM 1.0.0 then I'm afraid you will have to wait until Ubuntu update to the required NM version, which could be in Ubuntu 15.10.
Can't you add this feature in a separate branch so that it's possible to provide this feature to non ubuntu systems as soon as they start using NM 1.0.0? As an example, Arch has NM 1.0.0 already in the testing repository so it'll be released in the stable repo soon I guess. It would be possible to create an AUR package for plasma-nm with this patch so that the users will be able to use it. It would be great. I'm really eager to see this feature implemented because it affects me every day (also because there are other bugs in the wifi management which concur in degrading the user experience). As an example: when I got home and resume the notebook, plasma-nm connects to a shared network I've created to use at work and it doesn't show all the other wifi networks. So I have to do this: 1) Disconnect the current network 2) Turn off wifi 3) Turn on wifi 4) Manually connect to the desired network If I just disconnect the network and click the circular green arrow (which I guess should rescan the available networks [a tooltip here would be great]) nothing happens. So the other problems are two: 1) The other newroks are not shown upon resuming 2) The scan for network doesn't work
Git commit 6f6c11474b1e179215054a34b743ff1006f36c42 by Jan Grulich. Committed on 19/01/2015 at 09:40. Pushed by grulich into branch 'master'. Add option for autoconnect-priority M +18 -1 libs/editor/settings/connectionwidget.cpp M +140 -81 libs/editor/settings/ui/connectionwidget.ui http://commits.kde.org/plasma-nm/6f6c11474b1e179215054a34b743ff1006f36c42
Thank you very much for the quick update!