Shrew VPN Client gives default route- changing the policy stops me from accessing VPN network
Posted
by
Lock
on Server Fault
See other posts from Server Fault
or by Lock
Published on 2012-12-02T23:02:48Z
Indexed on
2012/12/02
23:08 UTC
Read the original article
Hit count: 359
I am using the shrew client to connect to what I believe is a Netscreen VPN.
Now, when connected, the client adds the VPN as the default route. I do not want this- there is only 1 network behind the VPN that I need to access.
I found that with the shrew client, you can change the "Policy" settings on the connection, and can add your own networks in that should tunnel over the VPN.
I do this, and add my network in, but when I connect the VPN, I get nothing. Can't access the network.
Any idea why this would be? I can see my network in the routing table, and its correctly pointing to the correct gateway. A traceroute shows all time-outs, so I can't be 100% sure that it is trying to tunnel over the VPN. Any idea how I can troubleshoot this?
© Server Fault or respective owner