From: "Michael Muenz" <linux@leute.server.de>
To: netfilter@lists.netfilter.org
Subject: Re: SNAT and IPSEC
Date: Wed, 13 Apr 2005 16:26:10 +0200 [thread overview]
Message-ID: <d3j9vh$tnf$1@sea.gmane.org> (raw)
In-Reply-To: 1113393681.4244.3.camel@fly.in.iantel.com.uy
Hi,
> "Eduardo Spremolla" <edspremolla@antel.com.uy> schrieb im
> Newsbeitragnews:1113393681.4244.3.camel@fly.in.iantel.com.uy...
> Yes, the OpenSwan is mutch more clear, yuo have the packet with the
> originals ip in the nat post chain to the tunn0 device.
> Is there any chance to aplay NETMAP to the source
> ip on PREROUTING ?
I never used NETMAP but this is from the description:
It can be applied to the PREROUTING chain to alter the destination of
incoming connections, to the POSTROUTING chain to alter the source
of outgoing connections, or both (with separate rules).
You want to alter the source (10.2.2.0/24) and that's an outgoing conn.
(Of course vice versa) ..
So perhaps this will work:
iptables -t nat -A POSTROUTING -s 10.2.2.0/24 -d 10.37.130.0/24 \
-j NETMAP --to 10.3.3.0/24
iptables -t nat -A PREROUTING -s 10.37.130.0/24 -d 10.3.3.0/24 \
-j NETMAP --to 10.2.2.0/24
- Michael
next prev parent reply other threads:[~2005-04-13 14:26 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 [this message]
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
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='d3j9vh$tnf$1@sea.gmane.org' \
--to=linux@leute.server.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.