From owner-freebsd-current@FreeBSD.ORG Wed Feb 4 13:36:53 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 DC02616A4CE for ; Wed, 4 Feb 2004 13:36:53 -0800 (PST) Received: from gvr.gvr.org (gvr-gw.gvr.org [80.126.103.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BF8443D39 for ; Wed, 4 Feb 2004 13:36:52 -0800 (PST) (envelope-from guido@gvr.org) Received: by gvr.gvr.org (Postfix, from userid 657) id E04F612; Wed, 4 Feb 2004 22:36:51 +0100 (CET) Date: Wed, 4 Feb 2004 22:36:51 +0100 From: Guido van Rooij To: cjclark@alum.mit.edu Message-ID: <20040204213651.GA43137@gvr.gvr.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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040204212147.GA32947@blossom.cjclark.org> 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 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:36:54 -0000 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? -Guido