From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: SNAT and IPSEC
Date: Wed, 13 Apr 2005 10:58:46 -0400 [thread overview]
Message-ID: <20050413145846.GA30293@bender.817west.com> (raw)
In-Reply-To: <1113329293.29536.13.camel@fly.in.iantel.com.uy>
On Tue, Apr 12, 2005 at 03:08:12PM -0300, Eduardo Spremolla wrote:
> I have 2 local networks 10.2.2.0/24 and 10.37.130.0/24 interconnected by
> a ipsec tunnel running on kernel 2.6 native ipsec. So far so good.
>
> Now the admin of 10.37.130.0 wants me to NAT my network to 10.3.3.0
> because he had a ip conflict. I cant SNAT because when the packet goes
> to nat post it has been encapsulated in ESP and had the firewalls
> address, as you can see in the bottom log snipe.I try to use NETMAP in
> mangle PREROUTING, but it changes the dest ip , not the source.
>
> Is this possible?
>
> Thanks in advance for any clue.
dunno if this will help or not; as i have lost my test lab, but have you
applied the ipsec patches from PoM:
ipsec-01-output-hooks
ipsec-02-input-hooks
ipsec-03-policy-lookup
ipsec-04-policy-checks
it is my understanding that these patches make packets traverse the
netfilter hooks twice: once clear, and again encrypted.
-j
--
"Peter: I call it... Petoria. I was going to call it Peterland,
but that gay bar by the airport took it."
--Family Guy
next prev parent reply other threads:[~2005-04-13 14:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 18:08 SNAT and IPSEC Eduardo Spremolla
2005-04-12 19:11 ` Daniel Lopes
2005-04-13 12:01 ` Eduardo Spremolla
2005-04-13 14:26 ` Michael Muenz
2005-04-14 14:03 ` Daniel Lopes
2005-04-14 15:19 ` Eduardo Spremolla
2005-04-14 17:01 ` Jason Opperisano
2005-04-13 14:58 ` Jason Opperisano [this message]
2005-04-13 15:45 ` Eduardo Spremolla
2005-04-13 16:00 ` Daniel Lopes
2005-04-13 16:08 ` Daniel Wittenberg
2005-04-13 17:29 ` Eduardo Spremolla
2005-04-13 23:50 ` Taylor Grant
2005-04-14 5:05 ` Alexander Samad
2005-07-15 19:36 ` Trevor Cordes
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=20050413145846.GA30293@bender.817west.com \
--to=opie@817west.com \
--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