well... the 'right' way would be to have your dial-in VPNs get 10.x.x.x IPs instead and pass the correct netmask so that the connecting workstation knows to use that path for all relivent IP addesses.
alternatives would include using the ROUTE command from the command prompt on the laptop to add a route for the 10.x.x.x subnet that uses the router for the remote VPN as it's next hop.
Type ROUTE at the command prompt for more info. but the command might look something like:
route -p ADD 10.20.30.0 MASK 255.255.0.0 192.168.1.1
Main Topics
Browse All Topics





by: fpoisonPosted on 2008-07-02 at 11:30:24ID: 21919225
access-list Split_Tunnel_List standard permit 192.168.100.0 255.255.255.0
Adding this as a split tunnel network-list will mean that anything which goes to 192.168.100.0/24 will enter the tunnel and the rest will be treated as "splitted tunnel". I suggest to add the 10.10.0.0/16 network to this access list (or any network you would like) and it'll start working. Also a routing table output from bot the client and the ASA would be helpful.