Re: NetworkManager, Avahi, WiFi v Wired priority

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/28/18 03:31, Chris Murphy wrote:
> nmclic c show <connection uuid>
>
> connection.autoconnect-priority should be higher on the preferred connection.
>
> https://developer.gnome.org/NetworkManager/stable/nm-settings.html
>
> So I've picked a value of 1 for wired and 0 for wifi. That should mean
> if I make an outgoing connection, it should always prefer wired. And
> yet 'netstat -natp' shows this is not true, sometimes it's using the
> wired path sometimes the wireless path, and I can't tell what the
> pattern is. If any.


I don't believe the parameters do what you are thinking they do.  "Connection" refers
to "Connection Profiles" and not how data flows on the network.

You can have multiple connection profiles for the same physical device.  I think the
best way to illustrate this is by using a WiFi Device. 

For example, lets say you have a device wlp4s0.  For that device you can create
multiple "Connection Profiles".   The major difference between the profiles would
most likely be the SSID.  Both connections could have the  autoconnect parameter set
to "yes".  However, you could then set autoconnect-priority to give priority of one
SSID over the other (or others).  This way if both SSID's are available you can be
sure your preferred SSID will get connected.

You could have a similar configuration for an ethernet connection.  One connection
profile may have a requirement that IPv6 be available and have priority over another
profile were IPv6  isn't required.  Potentially, in both profiles you have static
IPv4 addresses which differ.  This way a profile would be selected automatically
depending on where you connected your laptop, for example.

-- 
Conjecture is just a conclusion based on incomplete information. It isn't a fact.

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux