On 08/22/2018 08:59 AM, Patrick O'Callaghan wrote:
This is the routing table with the VPN enabled (the virbr stuff is
from
a VM, not relevant here):
(I rearranged the table.)
$ 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
128.0.0.0 10.87.0.53 128.0.0.0 UG 0 0 0 tun0
This is very weird routing! The first one matches any address that
doesn't have the highest bit set and the second one matches any address
that does. Together they match everything.
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
These are strange too.
default ZyXEL-router 0.0.0.0 UG 100 0
0 enp3s0
45.56.130.4 ZyXEL-router 255.255.255.255 UGH 0 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
I would suggest trying to get your own openvpn config working if
possible. There might be a script that the binary uses to configure the
routing, see if you can find that. Try running "strings" on the binary.
You could also just create your own script that starts up the VPN and
then modifies the routing table. Remove those first two entries and
then add entries for whatever range you do want to go over the VPN.