Date: Mon, 26 Jun 2006 17:16:14 +1000 From: Michael Vince <mv@thebeastie.org> To: David DeSimone <fox@verio.net> Cc: freebsd-net@freebsd.org Subject: Re: VPN with FAST_IPSEC and ipsec tools Message-ID: <449F89BE.7070508@thebeastie.org> In-Reply-To: <20060626063010.GB25367@verio.net> References: <449228FA.50303@thebeastie.org> <20060616122855.GA29279@uk.tiscali.com> <20060616154306.GA18578@verio.net> <449B5D50.8000700@thebeastie.org> <20060623062221.GA23272@verio.net> <449F52AA.8080504@thebeastie.org> <20060626040939.GA25367@verio.net> <20060626063010.GB25367@verio.net>
next in thread | previous in thread | raw e-mail | index | archive | help
David DeSimone wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >David DeSimone <fox@verio.net> wrote: > > >>Hmm... In examining my kernel configuration I found these options: >> >> options IPSEC >> options IPSEC_ESP >> options IPSEC_DEBUG >> # options IPSEC_FILTERGIF >> # options FAST_IPSEC >> >>So it appears that I am NOT using FAST_IPSEC. >> >> > >I have now recompiled my kernel with the following options: > > # options IPSEC > # options IPSEC_ESP > # options IPSEC_DEBUG > # options IPSEC_FILTERGIF > options FAST_IPSEC > > device crypto > >After rebooting, I noticed the startup messages show I am indeed using >FAST_IPSEC. > >My other configuration remains unchanged. I can still establish and use >the tunnels I have set up, so I don't believe this is an IPSEC vs >FAST_IPSEC problem you're seeing. > >- -- >David DeSimone == Network Admin == fox@verio.net > Darn, maybe you should try upgrading to 6.1 release and see if that does any thing. Also I am using the latest ipsec-tools in the ports tree 0.6.6 Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?449F89BE.7070508>