From: "Nicolás Velásquez O." <gnicolax@gmail.com>
To: netfilter@lists.netfilter.org
Subject: define what to nat
Date: Tue, 26 Apr 2005 13:17:28 -0500 [thread overview]
Message-ID: <200504261317.29179.gnicolax@gmail.com> (raw)
Hello there,
I've done some research, and yet I couldn't find any information.
I want to define what is natted, not only filter what is natted.
An example where it could be needed:
Let's say that I have openswan and 2.6 native ipsec. That means no
virtual ipsec iface. I want to connect various site LANs to my hq LAN
through VPN, so no nat should be done between those LAN-LAN
connections.
An example of one site-hq lan-lan connection:
LAN A <---> FW A / VPN A <---> INTERNET <---> FW B / VPN B <---> LAN B
segment A: 192.168.0.0/24 (HQ)
segment B: 192.168.1.0/24 (site)
I could use:
On FW A:
iptables -t nat -A POSTROUTING -o eth0 -d ! 192.168.1.0/24 -j MASQUERADE
On FW B:
iptables -t nat -A POSTROUTING -o eth0 -d ! 192.168.0.0/24 -j MASQUERADE
That would work, yet if the number of site-hq lan-lan connections grows,
it becomes either not useful and/or difficult to maintain.
So I was wondering if there is a way to do something like:
iptables -t nat -A POSTROUTING -o eth0 -d 192.168.0.0/24 -j "DO NOT NAT"
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
This way even if the number of sites to connect using VPN grows, it will
be easy to maintain.
Is there a way to achieve what I want??
Ps: I tried the mangle table too.
Ps2: Sorry for my english.
--
Atentamente,
Nicolás Velásquez O.
Bogotá, Colombia
(^) ASCII Ribbon Campaign
X NO HTML/RTF in e-mail
/ \ NO Word docs in e-mail
next reply other threads:[~2005-04-26 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 18:17 Nicolás Velásquez O. [this message]
2005-04-26 18:32 ` define what to nat Jason Opperisano
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=200504261317.29179.gnicolax@gmail.com \
--to=gnicolax@gmail.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 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.