Date: Mon, 18 Sep 2006 15:04:04 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: VANHULLEBUS Yvan <vanhu_bsd@zeninc.net> Cc: freebsd-net@freebsd.org Subject: Re: FAST_IPSEC NAT-T support Message-ID: <20060918145727.F2478@maildrop.int.zabbadoz.net> In-Reply-To: <20060918145200.GA26025@zen.inc> References: <20060914093034.A83805@gta.com> <d5992baf0609141843t5b81cf77w4d35a3a36beced1c@mail.gmail.com> <20060915091430.A45488@gta.com> <d5992baf0609150907p64ce6394y4b1fbb3309e76d53@mail.gmail.com> <20060917125531.GA1611@jayce.zen.inc> <d5992baf0609170858y107897c9k3039dbcb3d61d39a@mail.gmail.com> <20060918145200.GA26025@zen.inc>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 18 Sep 2006, VANHULLEBUS Yvan wrote: > By default in FreeBSd's port, NAT-T support is enabled if support is > detected on the system (checks for some structs in > include/net/pfkeyv2.h). > > Can you compile again ipsec-tools port, but not clean it, and check in > config.h if you have NAT-T support enabled. What I had found in the past is that the port (more exactly ipsec-tools) does not complain if configure is run with --enable-natt but the correct header files are no there. It silently continues and just disables natt support. That beahvior would be fine for "autodetect" but not for a command line option that says "I want natt support and you give me". -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060918145727.F2478>