From owner-freebsd-net@FreeBSD.ORG Mon Jun 25 09:30:16 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1172916A46C for ; Mon, 25 Jun 2007 09:30:16 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id C7EC213C4BF for ; Mon, 25 Jun 2007 09:30:15 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 46A6F1FFD6C; Mon, 25 Jun 2007 11:30:13 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id D2B4F1FFAFA; Mon, 25 Jun 2007 11:30:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 98DDD4448D5; Mon, 25 Jun 2007 09:28:04 +0000 (UTC) Date: Mon, 25 Jun 2007 09:28:04 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: blue In-Reply-To: <467F8002.9010803@zyxel.com.tw> Message-ID: <20070625090445.B98813@maildrop.int.zabbadoz.net> References: <467F65A0.9010900@zyxel.com.tw> <20070625070547.GA24243@zen.inc> <467F8002.9010803@zyxel.com.tw> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-net@freebsd.org Subject: Re: Questions about PF_KEY interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2007 09:30:16 -0000 On Mon, 25 Jun 2007, blue wrote: > I have read the manual page for fast_ipsec and ipsec. However, the man page > for fast_ipsec on FreeBSD-6.1Release said currently fast_ipsec does not > support IPv6. However, I thought it could properly deal with IPv6 packets > after tracing code. Could fast_ipsec support IPv6? Another problem is: if the yes, after you apply the patches that were posted the last weeks on this list and will be committed to HEAD shortly. > only difference between fast_ipsec and ipsec is about crypto acceleration, > why fast_ipsec needs to modify a bunch of files (including ip6_input, > ip6_output, ip6_forward, ..., etc.), not only the encap/decap part? If an ipv6 packet arrives that uses IPSec transport or tunnel mode, how should it be dispatched to ipsec processing if there were no hooks? Quite a bit of the code is there make it possible to interchange the ipsec implementations. Parts of that will go away too. > The function, key_output(), which is defined in netkey\keysock.c, does not > lock Giant before key_parse(). According to the comments (see below), maybe Ignore it. It's almost dead code. Apart from that quite a bit of the network stack runs with GIANT compat shims still. > Do you mean FAST_IPSEC feature will be embedded in FreeBSD-7.0 or later > version instead of IPSEC? As IPSEC. Kame IPSEC will go away. Read the archives of this list;-) -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT Software is harder than hardware so better get it right the first time.