Hello,

I'm wondering if someone can help with being able to connect to all private IP subnets from the VPN? I am using 172.16.0.0/12 for all my internal infrastructure stuff and then using 10.0.0.0 for my customers and would like to be able to access all of those internal IP's while I'm VPN'd in.

I have VPN setup on 172.31.1.1/24 and am able to connect to VPN no problem but I can't access or ping anything beyond the subnet that VPN is in. I'm thinking I need to add some specific routes to make this happen? Appreciate any input anyone has!

Thanks,
Mark

Update. . .I am able to ping my router now because I set the VPN range lower and widened the subnet to cover the whole 172.16 range. I still can't ssh or get to it over web though. Any ideas?

Hi

Is the vpn server running on the router itself? If so it will know all the networks involved, and you don't need to do anyting there.

Then all that remains is to tell your client OS how to reach these networks. Two options:
* make vpn de default route (with exception of the vpn server itself, so the vpn will keep on working)
* add route entry for each network you want to reach

Hi

Is the vpn server running on the router itself? If so it will know all the networks involved, and you don't need to do anyting there.

Then all that remains is to tell your client OS how to reach these networks. Two options:
* make vpn de default route (with exception of the vpn server itself, so the vpn will keep on working)
* add route entry for each network you want to reach

Thanks sebastia. Yes the VPN is running on the RB4011. I still can't seem to see the 172.16.5.1/24 network. How do I add a route for VPN to access 172.16.5.1/24? I can repeat that process when I add other networks and VLANs. Thanks!

Adding route over VPN on client side, is client OS dependent.

For windows: