My local network operates on 192.168.1.x with a subnet of 255.255.255.0. The default Gateway is 192.168.1.1. I would like to run a Wireguard client on an Rpi (192.168.1.10) to VPN to a remote private network running Wireguard Server on 192.168.2.x and a subnet of 255.255.255.0. My problem is the EE Smart router on my local network does not support static routes (ironically) for me to say that traffic destined for 192.168.2.x should be forwarded to 192.168.1.10 (for RPi to send over WireGuard).
I can configure the EE router IP and Subnet mask to be 192.168.1.1 and 255.255.0.0 (instead of 255.255.255.0). If I do this, it should keep both .1.x and .2.x traffic on the local network and not try to route it out over its WAN connection to the Internet. Am I correct in thinking that I can setup the PI on 192.168.1.10 to listen out for .2.x traffic and to perform the routing function to send it over Wireguard and vice versa? A quick overview of how, would also be appreciated.
EDIT Alternatively, would it be simpler to disable DHCP on the EE Smart Router and setup the RPi as the DHCP server with 192.168.1 10 as the default gateway. That way the Rpi can make the decision on how to route traffic for .1.x or .2.x networks. If traffic is not intended for either network, it sends it on to 192.168.1.1 (the EE router) for it to handle (like it does now).
