It's a bit like having a route on a router that instead of using the next hop IP address uses an outgoing interface instead.
So your default-gateway for the VPN client is the outgoing interface with IP address of the client end of the VPN tunnel. So all traffic no matter which subnet it is destined for will be sent down the tunnel.
I know this post was a while back, but like a good little boy I searched for my problem before starting a new post. :)
I had the same question Haitham did about why my VPN clients get their own IP set as their default GW. You answered that question... thanks! I still have another question though:
My ASA 5520 (which is what my remote clients VPN into) is connected on the inside interface to a VLAN network. I have a Cisco 6500 managing and routing this VLAN and others. When I connect in with my VPN client, I get assigned an IP address from the VLAN network that the ASA is connected to, but I cannot get to anything on that network or on any of my other VLAN networks. However, if I ssh into my ASA, I can ping anything on the ASA's inside network and other VLAN networks. Any idea why this is happening? I have static routes configured in the ASA for all of my other VLANs that point to the gateway of the ASA's inside network.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...