A very brief note here – I recently setup a network virt-network on my KVM setup at home on the 192.168.101.0/24 network – that all my VM’s connect to, and then route out via eth0 (192.168.1.15) – but naturally I cannot access them from my laptop here at work via the VPN because I dont have a route to that subnet.
So, after some poking around on the CLI on Windows (gulp), I finally added a route:
route add 192.168.101.0 mask 255.255.255.0 192.168.1.15
I come into the work the next day, and nope – cant access it again. A “route print” shows that the route has dissappeared! What we need to do it use a persistent flag:
route -p add 192.168.101.0 mask 255.25.255.0 192.168.1.15
This will keep the route after reboots, DHCP/Route table updates, etc so you dont have to mess around with .bat files!
Hope this helps someone.
Sam.