Not ideal, but the the client is routing all traffic including internet over the vpn, because it has a route for 0.0.0.0 0.0.0.0 . We should be able to select if possible which routes go over the tunnel, just like with the SSL. [:)]
Not ideal, but the the client is routing all traffic including internet over the vpn, because it has a route for 0.0.0.0 0.0.0.0 . We should be able to select if possible which routes go over the tunnel, just like with the SSL. [:)]
what you mean is called "split tunneling" and can be configured on cisco pix/asa/vpn3k just by defining what network to tunnel(*).
what about your ipsec config on the astaro? what networks did you choose as remote networks (dont know if this is the right word for the networks you want to tunnel).
Yes it is split-tunneling, which I have enabled on all my ASA firewalls at work.
Here is a screenshot showing how I only secure routes for the remote networks, and interntet still goes out locally, when I connect to Cisco firewalls.
Yes it is split-tunneling, which I have enabled on all my ASA firewalls at work.
Here is a screenshot showing how I only secure routes for the remote networks, and interntet still goes out locally, when I connect to Cisco firewalls.
[:S] this means its working and you can select which routes go through the tunnel and which not?
No, that screenshot is showing how it works on my Cisco gear. When I use the same client to connect to my beta ASG, the only secured network is 0.0.0.0/0.0.0.0 .
