On Sat, 2019-02-02 at 14:43 -0800, Mike Wright wrote: > On 2/2/19 4:22 AM, Patrick O'Callaghan wrote: > > Last ditch left-field idea: I have a (commercial) VPN service which is > > not normally turned on but does have a systemd daemon running. I turned > > it off and everything started working. > > > > I'll bet the vpn is messing with your routes. The routing table is the same with and without the daemon running, but actually starting the VPN does change it of course: VPN off: $ ip route default via 192.168.1.1 dev enp3s0 proto static metric 100 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.73 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 VPN on: $ ip route 0.0.0.0/1 via 10.191.0.141 dev tun0 default via 192.168.1.1 dev enp3s0 proto static metric 100 10.191.0.1 via 10.191.0.141 dev tun0 10.191.0.141 dev tun0 proto kernel scope link src 10.191.0.142 128.0.0.0/1 via 10.191.0.141 dev tun0 185.230.125.203 via 192.168.1.1 dev enp3s0 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.73 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 These are both with one guest running as well, hence the virbr0 stuff. The 185.230.125.203 address is one of the provider's endpoints. poc _______________________________________________ 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
