Nope, just left it running and it looks like it timed out a long time ago. Looks like it only lasts about 5 minutes, rain or shine.
> > On Wed, Jul 7, 2010 at 7:53 PM, Matthew Grooms <[email protected]> wrote: > >> On 7/7/2010 8:01 AM, Aaron Sarazan wrote: >> >>> This is an old problem that plagues my Win7-64 machine with all client >>> versions, but doesn't seem to even affect my Ubuntu machine (or any >>> coworkers' machines for that matter). >>> >>> I'll successfully connect to the gateway, ping inside the network, and >>> all is happy. After about five minutes, the connection will silently >>> fail and pings will time out. According to the "Network" tab, it is >>> still established, and the trace utility doesn't show anything but a >>> bunch of keep-alives for phase 1: >>> >>> 10/07/07 08:53:59 DB : phase1 found >>> 10/07/07 08:53:59 -> : send NAT-T:KEEP-ALIVE packet >>> 192.168.2.101:4500 <http://192.168.2.101:4500> -> >>> 98.101.134.218:4500 <http://98.101.134.218:4500> >>> >>> >>> Also the "VPN Connection Status" on the Netgear admin page lists it as >>> "IPsec SA Established". The connection won't return until I do a manual >>> disconnect/reconnect. >>> >>> On a possibly related note, it's listing Dead Peer Detection as >>> disabled, even though I've enabled it on both the client and server >>> side. Any thoughts on that? >>> >>> >> Hi Aaron, >> >> This sounds like a firewall state expired which is odd considering the >> NAT-T keep-alive packets. If you start a ping -t to a host behind the >> gateway and leave it running, does the connection still appear stable after >> 30 mins or so? >> >> -Matthew >> > >
_______________________________________________ vpn-help mailing list [email protected] http://lists.shrew.net/mailman/listinfo/vpn-help
