From: Joy Latten <latten@austin.ibm.com>
To: sreeniva@cse.psu.edu
Cc: netdev@vger.kernel.org
Subject: Re: Labeled IPsec with NAT
Date: Tue, 11 Dec 2007 23:03:10 -0600 [thread overview]
Message-ID: <200712120503.lBC53AYb028820@faith.austin.ibm.com> (raw)
>I am working on setting up Labeled IPsec along with iptables nat
>rules. Once I insert nat related rules, the ipsec connection breaks
>and the system tries to re-negotiate and creates multiple SAs. I am
>using 2.6.19 kernel (with Venkat's MLSXFRM patches & bugfixes). I
>guess those were incorporated into the 2.6.20 kernel.
Are you using racoon in ipsec-tools to create labeled SAs?
If so, I recall seeing duplicate SA pairs being created
while using racoon for labeled ipsec. We determined userspace
should manage this.
I posted a patch to ipsec-tools, but I don't think they
ever picked it up... I do not know if this is same problem,
but you could give it a try.
regards,
Joy
next reply other threads:[~2007-12-12 5:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 5:03 Joy Latten [this message]
2007-12-12 6:10 ` Labeled IPsec with NAT sreeniva
-- strict thread matches above, loose matches on Subject: below --
2007-12-12 3:37 Yogesh Raju Sreenivasan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200712120503.lBC53AYb028820@faith.austin.ibm.com \
--to=latten@austin.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=sreeniva@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox