[plasma-nm] [Bug 394364] Connection with higher priority is not activated

[Petr Nehez]

https://bugs.kde.org/show_bug.cgi?id=394364

--- Comment #3 from Petr Nehez  ---
@Jan Grulich 

Out of curiosity - do you know why a magic number of 2 is being added into
connection's metric?

https://unix.stackexchange.com/questions/444538/metric-on-connections-and-magic-2-value-added

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 394364] Connection with higher priority is not activated

[Petr Nehez]

https://bugs.kde.org/show_bug.cgi?id=394364

--- Comment #2 from Petr Nehez  ---
OK, I will try to use metric of each connection whether it helps.
It's just annoying that when I plug in a cable my LAN connection is not chosen
as the default one and the system still uses modem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasma-nm] [Bug 394364] Connection with higher priority is not activated

[Jan Grulich]

https://bugs.kde.org/show_bug.cgi?id=394364

Jan Grulich  changed:

   What|Removed |Added

 CC||jgrul...@redhat.com
 Resolution|--- |WONTFIX
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Jan Grulich  ---
The "priority" property you talking about is "autoconnect-priority", which
means that it is taken into account when there are e.g. more available wireless
networks at the moment and this helps to decide which should be activated. It
has no effect on device priority. It's NetworkManager who decided which device
should be the default one.

-- 
You are receiving this mail because:
You are watching all bug changes.