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

[Ken Bantoft]

I lied... this was a simple fix.  Committed into CVS (will be on anoncvs 
at 12:00 CET (we sync hourly from the master).

Works for me, please test.  *now* I'm on vacation!


On Sun, 27 Jun 2004, Ken Bantoft wrote:

> On Sat, 26 Jun 2004, Nate Carlson wrote:
> 
> > On Sun, 27 Jun 2004, Ken Bantoft wrote:
> > > 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?
> > 
> > Actually, no - with the patch I submitted, the other end thought it was
> > NAT'd, without having the forceencaps global option enabled.
> 
> Okay, so I missed a change somewhere - shouldn't be too hard to track 
> down.  There now a connection variables forceencaps, so you can use 
> st->st_connection->forceencaps to check it at any time.  It's a boolean.
> 
> I'll see about tracking it down tomorrow or so - I'm officially on 
> vacation here in Scotland for a few days :)
> 
> Ken