03-28-2012 02:12 PM - edited 03-28-2012 03:36 PM
I received a SSG5 router to play around with and get my feet wet in the world of routing. I configured a dialup VPN and I can get the client to connect and get an IP address, but I cannot ping the default gateway. Also, the VPN session only stays up for about 3 minutes then the security association expires. Not sure about that one either. Any help is greatly appreciated.
03-28-2012 07:40 PM
I'm assuming that by "default gateway" you mean the xx.xx.xx.1 address listed as gateway for eth0/0.
So, you have the gateway address of xx.xx.xx.1 in the Untrust zone, and the VPN client in the Untrust zone as well, but your dial-up VPN policy is for traffic between zone Untrust and Trust, hence there's no policy to facilitate traffic between the VPN client and the default gateway.
The SA would normally expire if there's no traffic (e.g. real traffic, or keep-alives, or something else). Depending on the client, it can be "dialed up" again when there's a need. To see if there's a problem, try, for example, pinging continuously an IP in your Trust zone from the VPN client, and see if the SA will get destroyed while doing that.
03-29-2012 03:03 PM
No, I'm still unable to ping 184.108.40.206 or any IP in the trust zone. I did notice this notification pop up on the SSG5 monitor: VPN monitoring for VPN <vpnclient_tunnel> has deactivated the SA with ID 0x00008C. Could this have something to do with the VPN dropping the client after a couple of minutes?
03-29-2012 03:17 PM
What is the VPN client you're using? Could you please post the IP address of the client (not the VPN-assigned one) and a trace-route between the client and 220.127.116.11 before and after VPN is established.
03-29-2012 04:48 PM
I'm using Shrewsoft as the client. If there's a better one out there, let me know. As far as the traceroutes go, there isn't much to say. Before the VPN connection, it gets out to the internet and dies and when the VPN is connected, it doesn't go anywhere.
03-29-2012 06:08 PM