Date: Tue, 14 Apr 2009 16:24:44 -0400 From: Scott Ullrich <sullrich@gmail.com> To: VANHULLEBUS Yvan <vanhu@freebsd.org> Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, freebsd-net@freebsd.org Subject: Re: NATT patch and FreeBSD's setkey Message-ID: <d5992baf0904141324g6a0e9678k4754f3ac6c808589@mail.gmail.com> In-Reply-To: <20090226141138.GA91564@zeninc.net> References: <85c4b1850902170448p7a59d50bt6bdaa89aa01c51d7@mail.gmail.com> <20090217143425.GA58591@zeninc.net> <20090217143409.J53478@maildrop.int.zabbadoz.net> <20090226141138.GA91564@zeninc.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 26, 2009 at 10:11 AM, VANHULLEBUS Yvan <vanhu@freebsd.org> wrot= e: > On Tue, Feb 17, 2009 at 02:41:41PM +0000, Bjoern A. Zeeb wrote: [snip] >> We have about 3 months left to get that patch in for 8; ideally 6 >> weeks. =A0Can you update the nat-t patch in a way as discussed here >> before so that the extra address is in etc. and we can move forward? > > Done, new version is available here: > http://people.freebsd.org/~vanhu/NAT-T/experimental/patch-FreeBSD-TRUNK-N= ATT-pfkey-clean-2009-02-26.diff Hello, We recently tested this patch on a up to date current as of a couple hours ago and it seems to break all outgoing UDP traffic (DNS included). Has anyone else experienced this issue? Backing the patch out of our pfSense patch roster cleared up the problem. Is there a newer patch available by chance? Thanks, Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d5992baf0904141324g6a0e9678k4754f3ac6c808589>