[Openswan dev] [PATCH] Force NAT-T per connection

Ken Bantoft ken at xelerance.com
Sun Jun 27 02:32:17 CEST 2004

Okay, where I'm staying at is really usefull.  Fearghas has real IP WLAN, 
and neighbours have NAT'd WLAN, so I can switch networks as the drop of an 

So... the results are sort-of in:

It works in that my client forces the encaps, but since the other side 
thinks there is no NAT, it doesn't respond.  I think this is correct, in 
that force sides will need to force it (have forceencaps=yes) on the conn 
for this to work.

Nate, your patch had the same requirements, correct?

On Sun, 27 Jun 2004, Ken Bantoft wrote:

> Needed something to kill a few hours on the train to Scotland, so I
> thought about this and implemented it on a per-connection basis.  
> 'forceencaps=yes' is the new config parameter.  Untested, but builds and
> runs for me.  Haven't been able to test it, as I'm behind a NAT again.

Ken Bantoft			VP Business Development
ken at xelerance.com		Xelerance Corporation
sip://toronto.xelerance.com	http://www.xelerance.com

More information about the Dev mailing list