On Tue, Jul 18, 2017 at 12:46 PM, Rick Stevens <ri...@alldigital.com> wrote:
> On 07/18/2017 11:05 AM, InvalidPath wrote: > > Thanks Rick, Yeah I'm certain. The network interface enp62s0u1u2 is the > > usb-c adapter built into the dock. So once docked that int comes up > > and, before the F26 upgrade the routes would get applied. Not they don't > :( > > Hmmm. Are you using NM to control this? If so, have you checked NM's > config for that device (the IPV4 tab, the "Routes..." button). > > > On Tue, Jul 18, 2017 at 10:38 AM, Rick Stevens <ri...@alldigital.com > > <mailto:ri...@alldigital.com>> wrote: > > > > On 07/18/2017 08:19 AM, InvalidPath wrote: > > > Anyone? Seems like an issue of this caliber would be important. > I know > > > it is for me when I am forced to resort to manually inputting > custom > > > routes each morning. > > > > You specifically said "while docked". Are you certain your system is > > recognizing when it is docked and when it isn't? That's the first > thing > > to check as that's probably more complex than picking up routes (like > > sorting out suspend issues). > > > > > On Mon, Jul 17, 2017 at 9:14 AM, InvalidPath < > invalid.p...@gmail.com <mailto:invalid.p...@gmail.com> > > > <mailto:invalid.p...@gmail.com <mailto:invalid.p...@gmail.com>>> > > wrote: > > > > > > 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. > > > 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 > > > > > > Any thoughts? > > > > > > Thanks > > > > > > > > > > > > > > > _______________________________________________ > > > users mailing list -- users@lists.fedoraproject.org > > <mailto:users@lists.fedoraproject.org> > > > To unsubscribe send an email to > > users-le...@lists.fedoraproject.org > > <mailto:users-le...@lists.fedoraproject.org> > > > > > > > > > -- > > ------------------------------------------------------------ > ---------- > > - Rick Stevens, Systems Engineer, AllDigital ri...@alldigital.com > > <mailto:ri...@alldigital.com> - > > - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 > - > > - > - > > - "I'd explain it to you, but your brain might explode." > - > > ------------------------------------------------------------ > ---------- > > _______________________________________________ > > users mailing list -- users@lists.fedoraproject.org > > <mailto:users@lists.fedoraproject.org> > > To unsubscribe send an email to users-le...@lists.fedoraproject.org > > <mailto:users-le...@lists.fedoraproject.org> > > > > > > > > > > _______________________________________________ > > users mailing list -- users@lists.fedoraproject.org > > To unsubscribe send an email to users-le...@lists.fedoraproject.org > > > > > -- > ---------------------------------------------------------------------- > - Rick Stevens, Systems Engineer, AllDigital ri...@alldigital.com - > - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - > - - > - "And on the seventh day, He exited from append mode." - > ---------------------------------------------------------------------- > _______________________________________________ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Currently? Both are in play and are identical. route file and NM's route tab.
_______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
