From owner-freebsd-current@FreeBSD.ORG Wed Feb 4 14:05:04 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 1D86116A4CF for ; Wed, 4 Feb 2004 14:05:04 -0800 (PST) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDDC543D53 for ; Wed, 4 Feb 2004 14:04:42 -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 (rwcrmhc12) with ESMTP id <2004020422044201400862lre>; Wed, 4 Feb 2004 22:04:42 +0000 Received: from blossom.cjclark.org (localhost. [127.0.0.1]) by blossom.cjclark.org (8.12.9p2/8.12.8) with ESMTP id i14M4e43033127; Wed, 4 Feb 2004 14:04:40 -0800 (PST) (envelope-from cristjc@comcast.net) Received: (from cjc@localhost) by blossom.cjclark.org (8.12.9p2/8.12.9/Submit) id i14M4YZk033126; Wed, 4 Feb 2004 14:04:34 -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 14:04:34 -0800 From: "Crist J. Clark" To: Guido van Rooij Message-ID: <20040204220434.GB33050@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> <20040204212147.GA32947@blossom.cjclark.org> <20040204213651.GA43137@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040204213651.GA43137@gvr.gvr.org> 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: Andrew Thomson 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 22:05:04 -0000 On Wed, Feb 04, 2004 at 10:36:51PM +0100, Guido van Rooij wrote: > On Wed, Feb 04, 2004 at 01:21:47PM -0800, Crist J. Clark wrote: > > 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... > > > True. Is KAME aware of this problem or is it FBSD specific? I believe it's FreeBSD specific, but I also believe it is a result of the effort to sync up the KAME stuff in the FreeBSD repository with more recent KAME SNAPs. There was quite a bit of chatter on the list about fixing some IPsec panics. I thought the same people were looking into this too, but when 5.2 passed by without a lot of concern... ? There have been commits to KAME IPsec code in the last day or so, but I haven't reviewed them or tried them out to see if they have anything to do with these issues. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org