login
Header Space

 
 

Re: OpenBSD4.1 IPSEC - transport_send_messages: giving up on exchange

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Douglas Secco dos Santos <douglas@...>, OpenBSD <misc@...>
Date: Thursday, December 6, 2007 - 11:39 am

We've got similar problems about a year ago, when we deployed a
massive installation of vpn/ipsec clients based on isakmpd.

When testing the client robustness to a series of events, like physically
disconnecting network cables, simulating power failures and such, we
saw the same pattern.

Our solution was to use an external program to send simple icmp
packets to our internal network and restart isakmpd once "detecting"
the tunnel is down.

A web search has showed us that tunnel "recreation" is complex and
frequently involves non-standard implemmentations. Sometimes, this
process fails and it should be considered an external watchdog to
be on the safe side.

So we cooked an in-house solution using "monit" to restart isakmpd in
case of failure. Obviously you'll need to define a simple set of rules
to classify a connection as "failed".

<snip>


<snip>
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
OpenBSD4.1 IPSEC - transport_send_messages: giving up on exc..., Douglas Secco dos Santos, (Wed Dec 5, 2:16 pm)
Re: OpenBSD4.1 IPSEC - transport_send_messages: giving up on..., Marcus Andree, (Thu Dec 6, 11:39 am)
speck-geostationary