On Fri, 21 Dec 2012 01:37:41 +0400, Emre Erenoglu <[email protected]> wrote: > Hi Andrew, > It seems I found the solution. When shrew connects, I can see in route > table that it does not add a specific route to the VPN server to go through > my home router. There's just default route which is now the VPN internal IP > & tap0 interface . > So, since packets destined to the vpn server can't go through, the VPN > fails. > When I added the manual route to the vpn server, then it started working. > But this shall not be like this, it shall normally add the specific route > to the vpn host when changing the default route, have you seen > any behavior like this? > Yes! I just have fogotten this! If I used default settings I had a default route to VPN (it was set by VPN GW on other end), so I had to set specific routes in Shrew VPN in Policy -> External network resources
-- -- Andrew _______________________________________________ vpn-help mailing list [email protected] http://lists.shrew.net/mailman/listinfo/vpn-help
