This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Routing

Hi, i have a routing question!

10.2.8.0---IPSec----10.3.8.0---IPSec---192.168.2.0
                                 |
                                 |
                            L2TP/PPTP
                           (Static Pools)

EDIT: my picture doesnt format right!
Ok... What i would really like is the VPN clients (L2TP/PPTP) to be able to ping 10.2.8.0 & 192.168.2.0.  VPN clients connect to the public side (internet) of the 10.3.8.0 subnet.

As of right now, the VPN clients can only ping machines on the 10.3.8.0 subnet.
I have tried setting up packet filters and the best i could get was "Reply from:10.70.179.1: 10.2.8.1: Destination Host unreachable."  Without the filter, ping would just time out.

Does anyone have some recommendations?  Will i need to setup masquerading for the L2TP/PPTP pools?

This thread was automatically locked due to age.

Parents

0 hemirunner1 over 19 years ago

alright i got it working by setting up SNAT between the IPSec pool, 10.2, and 192.168. addresses.

BTW, this is with remote gateway OFF for L2TP.

However, right off the bat the vpn clients can ping the 10.2 addresses but to ping the 192.168 addresses i have to maually add the route in the command prompt.

Is there a way to automatically set the client up with the 192.168 route so it does not need to be manually inputted?
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 hemirunner1 over 19 years ago

alright i got it working by setting up SNAT between the IPSec pool, 10.2, and 192.168. addresses.

BTW, this is with remote gateway OFF for L2TP.

However, right off the bat the vpn clients can ping the 10.2 addresses but to ping the 192.168 addresses i have to maually add the route in the command prompt.

Is there a way to automatically set the client up with the 192.168 route so it does not need to be manually inputted?
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data