From owner-freebsd-net@FreeBSD.ORG Thu May 31 09:24:59 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 D6E2316A421 for ; Thu, 31 May 2007 09:24:59 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25]) by mx1.freebsd.org (Postfix) with ESMTP id 8931A13C4B7 for ; Thu, 31 May 2007 09:24:59 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: by smtp.zeninc.net (smtpd, from userid 1000) id 568AC3F6D; Thu, 31 May 2007 11:24:58 +0200 (CEST) Date: Thu, 31 May 2007 11:24:58 +0200 From: VANHULLEBUS Yvan To: freebsd-net@freebsd.org Message-ID: <20070531092458.GA29156@zen.inc> References: <053120070319.25073.465E3EB3000078F2000061F122007348309709090E999C@comcast.net> <20070531072304.GA28098@zen.inc> <864plth28d.fsf@srvbsdnanssv.interne.kisoft-services.com> <20070531083738.GA28806@zen.inc> <20070531084559.T3053@maildrop.int.zabbadoz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070531084559.T3053@maildrop.int.zabbadoz.net> User-Agent: All mail clients suck. This one just sucks less. Subject: Re: Applying NAT-T patch 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: Thu, 31 May 2007 09:24:59 -0000 On Thu, May 31, 2007 at 08:52:03AM +0000, Bjoern A. Zeeb wrote: > On Thu, 31 May 2007, VANHULLEBUS Yvan wrote: [...] > > Maybe you could start addressing the things I posted last September? > http://lists.freebsd.org/pipermail/freebsd-net/2006-September/011807.html You're right: I was sure that this patch had been reported to "official" NAT-T patch, but it hasn't been yet, I appologize for that. While re-reading it, I remember now that I wanted to check again the minlen computation. The rest of the patch is ok and will be included today. > Also lately someone in my digital neighborhood had problems compiling > the patch for kernels with and without NAT-T support, for KAME and > fast_ipsec. Seems some #ifdef and #includes were not worked out > properly. I do not know which verion of the patch was used because > they, unfortunately, always had the same name and no versioning. Well, the file is versionned as it's in a CVS, but I'm not sure this specific CVS is available to public (this is the CVS used to update sourceforge's projects web sites). Now I know that the patch stayed there for a long time, I know that I should have putted it somewhere else, with better versionning informations available...... Yvan. -- NETASQ http://www.netasq.com