[nSLUG] network over WAN
me at jonwatson.ca
Mon Jan 14 12:56:52 AST 2008
On Jan 14, 2008 12:55 PM, Ian Campbell <ian at slu.ms> wrote:
> On Mon, Jan 14, 2008 at 12:46:53PM -0400, Jon wrote:
> > The only downside I've found to OpenVPN (and possibly this extends to
> > most/all VPNs) is that it is not aware of itself and does not know if
> > connection has been broken. I ended up writing a stupid little BASH
> > on either end that attempted to ping through the tunnel to the OpenVPN
> IP on
> > the other side every 30 mins. If it failed, it restarted the daemon and
> > reconnected. Of course, some thought has to go into timing these pings
> > either side so you don't enter a loop :)
> It's *supposed* to be.
> From my config:
> # The keepalive directive causes ping-like
> # messages to be sent back and forth over
> # the link so that each side knows when
> # the other side has gone down.
> # Ping every 10 seconds, assume that remote
> # peer is down if no ping received during
> # a 120 second time period.
> keepalive 10 120
Wow, look at that. I wonder if I didn't have that active or if it just
didn't work right. The mists of time are clouding my memory.
Is that the default setting?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nSLUG