On Tue, 2018-08-21 at 15:15 -0700, Samuel Sieb wrote:
On 08/21/2018 09:08 AM, Patrick O'Callaghan wrote:
> It works as far as it goes, but still no split tunnel. I suspect the
> (provider-supplied *binary*) connection script is forcing all traffic
> through the tunnel. Looks like I'll have to play with OpenVPN using the
> provider's credentials and see if I can convince it to play ball.
What is the output of the "route" command? Check for a default gateway
that is pointing to the VPN. If there is one, try removing it and see
what happens.
This is the routing table with the VPN enabled (the virbr stuff is from
a VM, not relevant here):
$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.87.0.53 128.0.0.0 UG 0 0 0 tun0
default ZyXEL-router 0.0.0.0 UG 100 0 0 enp3s0
10.87.0.1 10.87.0.53 255.255.255.255 UGH 0 0 0 tun0
10.87.0.53 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
45.56.130.4 ZyXEL-router 255.255.255.255 UGH 0 0 0 enp3s0
128.0.0.0 10.87.0.53 128.0.0.0 UG 0 0 0 tun0
192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 enp3s0
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
The default points directly to the local router, as expected, but the
router's address has changed. For comparison, here's the table with the
VPN turned off:
$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default ZyXEL-router 0.0.0.0 UG 100 0 0 enp3s0
192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 enp3s0
192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0
poc