On Fri, Jun 10, 2016 at 1:40 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > On Fri, Jun 10, 2016 at 1:25 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: >> 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. > > Aha! The "Use this connection only for resources on its network" > causes ipv4.never-default to change from no to yes. i.e. unchecked > it's no, and checked it's yes. > > So why doesn't this do what I'm thinking it ought to do? Answer! It's a bug! https://bugzilla.redhat.com/show_bug.cgi?id=1344788 Clicking the Apply button does not reload the connections, so the settings change does not take effect. I either have to do 'nmcli c reload' or in the GUI click on Wired, then change On to Off to back On. And now it works as expected. GENERAL.DEFAULT is now no for this wired connection, and ip route show no longer shows it as default via. Sooo... if someone wants to test this on Fedora 23 in GNOME to see if this Apply bug happens there, it would be great to know if it's a regression or not, and note this in the bug. Thanks! -- 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
