Gargoyle Forum

I can't believe it, I got it to work It just opens up a whole new world of possibilities C:\Users\User>tracert 192.168.1.118 Tracing route to SVR [192.168.1.118] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms Gargoyle.lan [192.168.10.1] 2 35 ms 28 ms 33 ms 10.8.0.1 3 23 ms 33 ms 28 ms 192.168.1.1 4 ...

@Lantis what version of OpenVPN are we currently using?

My current thinking is another solution could be a different OpenVPN configuration

Try making that "tun". I know that might be a bit counterintuitive given the rest of them say tun0.

Bad things happen

The router is slow and then gets into a reboot loop

Tried to remove the rule but it made no difference

In the end, router reset was required

ill try tun current file config route 'route1' option target '192.168.1.0' option interface 'tun0' option gateway '10.8.0.1' option netmask '255.255.255.0' The whole file just in case config interface 'loopback' option device 'lo' option proto 'static' option ipaddr '127.0.0.1' option netmask '255.0...

It appears that the custom route is not added to the route table root@Gargoyle:~# ip route default via 203.xxx.xxx.254 dev eth0.2 proto static src 203.xxx.xxx.226 10.8.0.0/24 dev tun0 proto kernel scope link src 10.8.0.5 10.64.0.0/24 dev wg0 proto kernel scope link src 10.64.0.1 192.168.2.0/24 via 1...

Looks like this person might be trying to do a similar thing

https://forum.openwrt.org/t/how-to-set- ... ble/122766

Double Nating removed

There is something else in the client VPN router that forces traffic to use the VPN route

Good spot I'm double Natting, I've still got the VLAN 10 problem I've found in the past that the VPN takes precedence over the WAN so if the downstream router is 192.168.1.1 and the VPN router on the other end is also 192.168.1.1 it will ignore the downstream router. Tomorrow I will change the downs...

BTW I had to edit the route file via the command line

Trace route didn't really tell me much