Re: NetworkManager, using two networks simultaneously

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

 



On Fri, Jun 10, 2016 at 12:50 PM, Gordon Messmer
<gordon.messmer@xxxxxxxxx> wrote:
> On Fri, Jun 10, 2016 at 9:42 AM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote:
>>
>> I would have though for wired, setting "Use this connection only for
>> resources on its network" would do that, but it doesn't.
>
> What does "ip route show" output when you set that option?  Also, are
> you setting that option for both ipv4 and ipv6?

Wireless On, Wired Off = Internet works

[root@f24m ~]# ip route show
default via 172.19.11.1 dev wlp3s0b1  proto static  metric 600
172.19.11.0/24 dev wlp3s0b1  proto kernel  scope link  src
172.19.11.35  metric 600
192.168.124.0/24 dev virbr0  proto kernel  scope link  src
192.168.124.1 linkdown

Wirless On, Wired On with "Use this connection only for resources on
its network" unchecked = No internet

[root@f24m ~]# ip route show
default via 192.168.1.1 dev enp2s0f0  proto static  metric 100
default via 172.19.11.1 dev wlp3s0b1  proto static  metric 600
172.19.11.0/24 dev wlp3s0b1  proto kernel  scope link  src
172.19.11.35  metric 600
192.168.1.0/24 dev enp2s0f0  proto kernel  scope link  src
192.168.1.185  metric 100
192.168.124.0/24 dev virbr0  proto kernel  scope link  src
192.168.124.1 linkdown

Wirless On, Wired On with "Use this connection only for resources on
its network" checked = No internet

[root@f24m ~]# ip route show
default via 192.168.1.1 dev enp2s0f0  proto static  metric 100
default via 172.19.11.1 dev wlp3s0b1  proto static  metric 600
172.19.11.0/24 dev wlp3s0b1  proto kernel  scope link  src
172.19.11.35  metric 600
192.168.1.0/24 dev enp2s0f0  proto kernel  scope link  src
192.168.1.185  metric 100
192.168.124.0/24 dev virbr0  proto kernel  scope link  src
192.168.124.1 linkdown

Two default via's? Seems like a bad idea. Is this a bug? I can't
imagine that I'm the only person with two ethernets, it doesn't really
matter one of them is wireless, and I have a prefered default routing.

https://developer.gnome.org/NetworkManager/stable/ref-settings.html
says that ipv4.never-default yes should mean "this connection will
never be the default connection for this IP type, meaning it will
never be assigned the default route by NetworkManager." But this is
definitely not true. There's a bug somewhere, either my reading
comprehension is flawed, the documentation is flawed, or
NetworkManager should work the way the doc and I think it should work.



-- 
Chris Murphy
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org



[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