Pre-F26 upgrade I used a route file to apply work related routes while docked, for some reason since the upgrade when I look via route or ip route I am no longer getting the ones from the file applied.
Thanks
I did verify the name of my interface is correct.. the name changed once after an update so that's always the first thing I check.
I also have the same routes in the Route tab in Network Manager, and looking in journalctl I see:
Jul 17 08:16:53 Vostok audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd"
Jul 17 08:16:53 Vostok dhclient[3662]: bound to 10.0.20.186 -- renewal in 1122048 seconds.
Jul 17 08:16:53 Vostok nm-dispatcher[3754]: req:1 'pre-up' [enp62s0u1u2]: new request (1 scripts)
Jul 17 08:16:53 Vostok NetworkManager[1158]: <info> [1500301013.5560] device (enp62s0u1u2): state change: ip-check -> secondaries (reason 'n
Jul 17 08:16:53 Vostok NetworkManager[1158]: <info> [1500301013.5563] device (enp62s0u1u2): state change: secondaries -> activated (reason '
Jul 17 08:16:53 Vostok dnsmasq[1477]: reading /etc/resolv.conf
Jul 17 08:16:53 Vostok dnsmasq[1477]: using nameserver 10.0.20.19#53
Jul 17 08:16:53 Vostok NetworkManager[1158]: <info> [1500301013.5650] device (enp62s0u1u2): Activation: successful, device activated.
Jul 17 08:16:53 Vostok dnsmasq[1477]: using nameserver 10.0.20.1#53
Jul 17 08:16:53 Vostok dnsmasq[1477]: using nameserver 10.0.22.1#53
Jul 17 08:16:53 Vostok dnsmasq[1477]: using nameserver 10.0.20.20#53
Jul 17 08:16:53 Vostok nm-dispatcher[3754]: req:2 'up' [enp62s0u1u2]: new request (7 scripts)
Jul 17 08:16:53 Vostok nm-dispatcher[3754]: req:2 'up' [enp62s0u1u2]: start running ordered scripts...
Jul 17 08:16:53 Vostok systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive.
Jul 17 08:16:53 Vostok NetworkManager[1158]: <info> [1500301013.7452] policy: set 'USB-c Ethernet' (enp62s0u1u2) as default for IPv4 routing
Jul 17 08:16:53 Vostok dnsmasq[1477]: reading /etc/resolv.conf
Jul 17 08:16:53 Vostok dnsmasq[1477]: using nameserver 10.0.20.19#53
Jul 17 08:16:53 Vostok dnsmasq[1477]: using nameserver 10.0.20.20#53
Jul 17 08:16:53 Vostok dnsmasq[1477]: using nameserver 10.0.20.1#53
Jul 17 08:16:53 Vostok dnsmasq[1477]: using nameserver 10.0.22.1#53
Jul 17 08:16:53 Vostok dhclient[3662]: bound to 10.0.20.186 -- renewal in 1122048 seconds.
Jul 17 08:16:53 Vostok nm-dispatcher[3754]: req:1 'pre-up' [enp62s0u1u2]: new request (1 scripts)
Jul 17 08:16:53 Vostok NetworkManager[1158]: <info> [1500301013.5560] device (enp62s0u1u2): state change: ip-check -> secondaries (reason 'n
Jul 17 08:16:53 Vostok NetworkManager[1158]: <info> [1500301013.5563] device (enp62s0u1u2): state change: secondaries -> activated (reason '
Jul 17 08:16:53 Vostok dnsmasq[1477]: reading /etc/resolv.conf
Jul 17 08:16:53 Vostok dnsmasq[1477]: using nameserver 10.0.20.19#53
Jul 17 08:16:53 Vostok NetworkManager[1158]: <info> [1500301013.5650] device (enp62s0u1u2): Activation: successful, device activated.
Jul 17 08:16:53 Vostok dnsmasq[1477]: using nameserver 10.0.20.1#53
Jul 17 08:16:53 Vostok dnsmasq[1477]: using nameserver 10.0.22.1#53
Jul 17 08:16:53 Vostok dnsmasq[1477]: using nameserver 10.0.20.20#53
Jul 17 08:16:53 Vostok nm-dispatcher[3754]: req:2 'up' [enp62s0u1u2]: new request (7 scripts)
Jul 17 08:16:53 Vostok nm-dispatcher[3754]: req:2 'up' [enp62s0u1u2]: start running ordered scripts...
Jul 17 08:16:53 Vostok systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive.
Jul 17 08:16:53 Vostok NetworkManager[1158]: <info> [1500301013.7452] policy: set 'USB-c Ethernet' (enp62s0u1u2) as default for IPv4 routing
Jul 17 08:16:53 Vostok dnsmasq[1477]: reading /etc/resolv.conf
Jul 17 08:16:53 Vostok dnsmasq[1477]: using nameserver 10.0.20.19#53
Jul 17 08:16:53 Vostok dnsmasq[1477]: using nameserver 10.0.20.20#53
Jul 17 08:16:53 Vostok dnsmasq[1477]: using nameserver 10.0.20.1#53
Jul 17 08:16:53 Vostok dnsmasq[1477]: using nameserver 10.0.22.1#53
Any thoughts?
Thanks
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx