From: Scott Mcdermott <smcdermott@questra.com>
To: netfilter@lists.netfilter.org, linux-kernel@vger.kernel.org
Subject: Re: SNAT interaction with kernel-based IPSEC (in 2.6)
Date: Thu, 4 Sep 2003 07:15:43 -0400 [thread overview]
Message-ID: <20030904111543.GT17837@questra.com> (raw)
In-Reply-To: <20030904091525.GO17837@questra.com>
To netfilter@lists.netfilter.org on Thu 4/09 05:15 -0400:
> I'm having some difficulty doing simple pings over an
> IPSEC tunnel using the implementation in 2.6.0-test4 (with
> Racoon, and successful Phase 1 and 2, I get the IPSEC SA
> fine), in combination with iptables.
Nevermind this, I had set the security policy with the wrong
/24 on the remote end. It's now working great with IPSEC
and doing SNAT only when it doesn't traverse the tunnel.
I'm really surprised that it "just works." The IPSEC in 2.6
is very good IMO, basically turnkey.
It still would be nice to know where IPSEC fits in to the
Netfilter engine (ie, why it does "just work" and not SNAT
when it goes over the tunnel), but it works great now...I
think RTFS is in order.
next prev parent reply other threads:[~2003-09-04 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 9:15 SNAT interaction with kernel-based IPSEC (in 2.6) Scott Mcdermott
2003-09-04 11:15 ` Scott Mcdermott [this message]
2003-09-04 18:34 ` Mark E. Donaldson
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=20030904111543.GT17837@questra.com \
--to=smcdermott@questra.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter@lists.netfilter.org \
/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