You have a route for 192.168.1.0/24 to both WAN and tun0. You can’t do that.
Why is the route via WAN there?
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
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 downstream router subnet so it looks better and eliminates a possiable problem
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 10.8.0.1 dev tun0
192.168.10.0/24 via 10.8.0.1 dev tun0
192.168.16.0/24 via 10.8.0.1 dev tun0
192.168.20.0/24 via 10.8.0.1 dev tun0
192.168.33.0/24 via 10.8.0.1 dev tun0
192.168.123.0/24 via 10.8.0.1 dev tun0
192.168.175.0/24 dev br-lan proto kernel scope link src 192.168.175.1
203.xxx.xxx.0/24 dev eth0.2 proto kernel scope link src 203.xxx.xxx.226
root@Gargoyle:~#
What does the "route1" section of /etc/config/network show? (it should be at the bottom).
I suspect it shows interface = 'tun0'?
Try making that "tun". I know that might be a bit counterintuitive given the rest of them say tun0.
I can't run a test for you at the moment as i'm in the middle of updating Gargoyle to 23.05 and I haven't got OpenVPN working yet.
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.