Date: Sat, 9 Aug 2003 12:39:39 +0200 From: lupe@lupe-christoph.de (Lupe Christoph) To: Kevin Glick <glitch@ridiculum.woohaw.com> Cc: freebsd-security@freebsd.org Subject: Re: IPSec delays Message-ID: <20030809103939.GC25445@lupe-christoph.de> In-Reply-To: <20030808004556.GA2051@ridiculum.woohaw.com> References: <20030808004556.GA2051@ridiculum.woohaw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 2003-08-07 at 17:45:56 -0700, Kevin Glick wrote: > I've been using IPSec and racoon alot lately creating tunnels between FreeBSD machines. Everything works as it should once I've got it running. I do however seem to get delays when one, or both ends of the tunnel drop or are rebooted. On reboot, once the machine starts racoon, it takes two or three minutes for the tunnel to come back up. If I stop and restart racoon, it takes only 60 seconds. I'd prefer to cut this time down on both to 30 seconds or less. Below is my racoon.conf. I've watched the racoon logs, and it doesn't give me any errors, or failed negotiations. Any ideas? I had something like this with a Racoon/FreeS/WAN setup. I found out that the algorithms did no match, and the tunnel would only be built from the Racoon side. Seems FreeS/WAN was set up to accept a wider range of algorithms than Racoon. I have to confess I did not understand if you can specify more than one algorithm to Racoon. Switch on debugging and look for rejected connection attempts. HTH, Lupe Christoph -- | lupe@lupe-christoph.de | http://www.lupe-christoph.de/ | | "Violence is the resort of the violent" Lu Tze | | "Thief of Time", Terry Pratchett |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030809103939.GC25445>