[Openswan Users] Checkpoint - OpenSwan connection dropping
petermcgill at goco.net
Mon Jan 8 12:42:00 EST 2007
> -----Original Message-----
> Date: Mon, 8 Jan 2007 10:13:12 -0000
> From: <Mike.Peters at opengi.co.uk>
> Subject: [Openswan Users] Checkpoint - OpenSwan connection dropping
> To: <users at openswan.org>
> I currently have a Checkpoint <-> OpenS/WAN connection. It works fine
> for a while, in both directions, however the connection drops fairly
> frequently and I cannot re-initiate the connection from the
> OpenSwan end
> of the connection - the connection re-establishes if I ping from the
> Checkpoint network to the OpenSwan network.
> Does anyone have any ideas what the workaround may be (or any other
> My ipsec.conf is as follows:
> # basic configuration
> config setup
> conn %default
> conn net-openswan-net
> conn checkpoint-openswan
When you say "I cannot re-initiate the connection from the OpenSwan end",
Do you mean only auto-renew fails, or manual too?
I see no reason why manual would fail here.
ie) ipsec auto --up checkpoint-openswan
(pings will not renew an openswan conn, they are not "on-demand" in that sense.)
However, to fix auto-renewal, try setting rekey=yes, and keyingtries=%forever in the appropriate conn.
They are defaults, however putting keyingtries=3 in the %default conn, will have overridden the default.
Also make sure that keylife and ikelifetime match the values in the checkpoint configuration.
You can also try enabling dead peer detection if supported by checkpoint.
In openswan is, dpddelay=30, dpdtimeout=120, dpdaction=restart.
All this may help, however I suspect your biggest problem is keyingtries=3 in the %default conn.
Experience has taught me that keyingtries does not reset after a connection is made, so at best
You'll get 2 renewals, before openswan gives up. This doesn't afect incoming conns, so it would
Still allow the checkpoint to renew it, as your ping has done.
More information about the Users