From owner-freebsd-current@FreeBSD.ORG Wed Feb 4 13:21:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E24BB16A4CE for ; Wed, 4 Feb 2004 13:21:59 -0800 (PST) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BC1943D1D for ; Wed, 4 Feb 2004 13:21:58 -0800 (PST) (envelope-from cristjc@comcast.net) Received: from blossom.cjclark.org (c-24-6-186-224.client.comcast.net[24.6.186.224]) by comcast.net (sccrmhc13) with ESMTP id <200402042121570160016h9qe>; Wed, 4 Feb 2004 21:21:57 +0000 Received: from blossom.cjclark.org (localhost. [127.0.0.1]) by blossom.cjclark.org (8.12.9p2/8.12.8) with ESMTP id i14LLt43032965; Wed, 4 Feb 2004 13:21:55 -0800 (PST) (envelope-from cristjc@comcast.net) Received: (from cjc@localhost) by blossom.cjclark.org (8.12.9p2/8.12.9/Submit) id i14LLlmU032964; Wed, 4 Feb 2004 13:21:47 -0800 (PST) (envelope-from cristjc@comcast.net) X-Authentication-Warning: blossom.cjclark.org: cjc set sender to cristjc@comcast.net using -f Date: Wed, 4 Feb 2004 13:21:47 -0800 From: "Crist J. Clark" To: Andrew Thomson Message-ID: <20040204212147.GA32947@blossom.cjclark.org> References: <1074650025.701.82.camel@itouch-1011.prv.au.itouchnet.net> <20040122110929.GA767@gvr.gvr.org> <20040203070435.GB46486@blossom.cjclark.org> <20040203155309.GA22676@gvr.gvr.org> <1075893572.29017.1.camel@oblivion> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1075893572.29017.1.camel@oblivion> User-Agent: Mutt/1.4.1i X-URL: http://people.freebsd.org/~cjc/ X-Mailman-Approved-At: Thu, 05 Feb 2004 05:14:12 -0800 cc: current@freebsd.org Subject: Re: ipsec changes in 5.2R X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: cjclark@alum.mit.edu List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Feb 2004 21:22:00 -0000 On Wed, Feb 04, 2004 at 10:19:33PM +1100, Andrew Thomson wrote: > Thanks, that worked a treat for me too.. everything back to normal! > > So what's the go with this fast_ipsec business. Is this going to be the > main implementation for Freebsd? I believe the main reason FAST_IPSEC came to be is support for crypto hardware. However, FAST_IPSEC cannot replace KAME IPsec. FAST_IPSEC is IPv4-only whereas KAME is IPv6 with its required IPsec abilities "back-ported" into the IPv4 stack. It would be really, really nice to get this bug out of KAME IPsec before 5.2.1, but if 5.2 didn't wait... > On Tue, 2004-02-03 at 16:53 +0100, Guido van Rooij wrote: > > On Mon, Feb 02, 2004 at 11:04:36PM -0800, Crist J. Clark wrote: > > > > I have seen the same. Somehow it looks like ISAKMP traffic, which used to > > > > go around the ipsec policy, is now included. The only workaround I know > > > > of is to replace "require" with "use". > > > > > > A little late on this, but FAST_IPSEC rather than KAME IPsec will fix > > > the problem. > > > > Thanks! That helped! > > > > -Guido -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org