Date: Thu, 31 May 2007 11:24:58 +0200 From: VANHULLEBUS Yvan <vanhu_bsd@zeninc.net> To: freebsd-net@freebsd.org Subject: Re: Applying NAT-T patch Message-ID: <20070531092458.GA29156@zen.inc> In-Reply-To: <20070531084559.T3053@maildrop.int.zabbadoz.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070531092458.GA29156>