Hi, On Fri, Nov 04, 2005 at 10:47:59PM +0100, Tobias Walkowiak wrote: > hm, i think i better update the other peer to 3.8, as well - although it's > 550 km from here ... > > > Other workaround, disable nat-t with the -T option. > > but that only works for 3.8 isakmpd, doesn't it? what about the > net.inet.esp.udpencap sysctl setting? should it be set to zero?
the sysctl only affects the kernel, not isakmpd. Using -T on the 3.8 side disables nat-t and the 3.7 isakmpd should be fine again. HJ.
