The issue I am having is that while my machine at 192.168.0.2 can access the outside world either via 192.168.0.1 or 192.168.0.250 as its gateway, as can my machine at 10.0.0.10 access the outside world without accessing anything at 192.168.0.X, my machine at 192.168.0.2 cannot access either 10.0.0.1 or 10.0.0.10, and a tracert from the windows command prompt results in If i remove the two sandboxgateway lines i can access 10.0.0.1 but anything in the 10.0.0.X range is accessing the internet through the VPN, which is not what i want.Īnd its iptable looks like this: Chain INPUT (policy ACCEPT) Ip route add default via 192.168.0.1 dev eth0 table sandboxgateway Ip rule add from 10.0.0.0/24 table sandboxgateway

I add the routes via ip rule add from 192.168.0.0/24 table default Now that I have explained the network i want, here is my setup and what i am experiencing: I also have a third gateway for bridging the two subnets, another Ubuntu VM with 2 NICS, the first being 192.168.0.251 and the second being 10.0.0.1 On top of this, in the 192.168.0.0/24 range i also want 2 gateways, the first being the default gateway (currently in the form of an Ubuntu VM) which routes traffic via a vpn, its address is 192.168.0.250 and the second gateway (which is the internet-facing TP-Link wireless router) at 192.168.0.1 (also the DHCP & DNS server for the 192.168.0.0/24 range) I do not want machines with a source within 10.0.0.0/24 to be able to access machines in the 192.168.0.0/24 range but i do want it to be able to go outside. the second subnet on range 10.0.0.0/24 is restricted to only being able to access the outside world. I am attempting to operate 2 subnets, the first subnet on range 192.168.0.0/24 is free to access anything it wants, including machines on the second subnet.

10.0.0.0.1 gateway