From: "Ellad G. Yatsko" <eyatsko@ngs.ru>
To: netfilter@vger.kernel.org
Subject: Iptables NAT with two external Interfaces
Date: Thu, 03 May 2012 13:14:17 +0400 [thread overview]
Message-ID: <4FA24C69.4000607@ngs.ru> (raw)
Hello!
May you help me in one very specific issue?
- I have Ubuntu router with several interfaces with Quagga/BGP working
on it, and of course IPTables with NAT for internal users;
- One interface is used to connect to ISP, it has ISP's IP-address. For
definiteness it is 89.222.233.165. Ubuntu connects to ISP's network via
this IP;
- Another interface - DMZ with own IP-address (delegated by RIPE NCC) of
own Autonomous System: 91.223.181.1;
- DMZ is terminated on Cisco 2821 (one subinterface 91.223.181.2) which
is connected to second ISP (via second subinterface with IP from second
ISP: 188.35.132.79).
- There is specific routing: each of my "borders" marks a part of
prefixes received from corresponding ISP by higher LocalPref: Ubuntu
marks prefixes 0.0.0.0-127.0.0.0, and Cisco marks prefixes 128.0.0.0 up
to 224.0.0.0.
That is if destination IP is more than 128.0.0.0 Ubuntu prefers to send
the current packet to directly connected ISP, if it is less than
128.0.0.0 Ubuntu prefers to route the packet through DMZ. It is made to
utilize both uplinks evenly.
I need to explain one important detail: both of my ISPs are connected to
the same higher-level ISP, which uses the only ISP from the pair of mine
to direct incoming traffic into my AS. So there is no other opportunity
to make balancing except egress traffic.
- Ubuntu has internal interfaces to give to its internal users access to
Internet. Internal users have "private" IPs which are "NATted" on
external Ubuntu's interfaces.
- Actually the question: with probability 50% a packet from internal
users can be sent through one external Ubuntu's interface and reply can
return through another. In that case NAT is not working. Here my
relevant part of configuration:
$IPTABLES -t nat -A POSTROUTING -o $EXT_IF -s $INTERNAL -d $EXTERNAL -j
SNAT --to $DMZ_IP
$IPTABLES -t nat -A POSTROUTING -o $DMZ_IF -s $INTERNAL -d $EXTERNAL -j
SNAT --to $DMZ_IP
What can I do except:
$IPTABLES -t nat -A POSTROUTING -o $EXT_IF -s $INTERNAL -d $EXTERNAL -j
SNAT --to $EXT_IP
$IPTABLES -t nat -A POSTROUTING -o $DMZ_IF -s $INTERNAL -d $EXTERNAL -j
SNAT --to $DMZ_IP
Difference with above two is "$EXT_IP" in the first line. In that case
all works fine. But I need to hide ISP's IP from External World. I need
to show to others my own IPs only. It's the highest priority. Again, may
you help me to find an answer? Are there some "secret commands" for
IPTables to make NAT to ignore ingress interface to de-NAT replies? For
example, FreeBSD's PF can do correct "back" translations independently
from interface where reply-packet has come on. Ubuntu has changed
FreeBSD on the place of central router due to rank of reasons (one of
them is stability), but now I have big trouble! :-)
He-e-e-lp!...
Kind regards,
Ellad
next reply other threads:[~2012-05-03 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 9:14 Ellad G. Yatsko [this message]
2012-05-03 14:46 ` Iptables NAT with two external Interfaces Ellad G. Yatsko
2012-05-03 15:06 ` Lloyd Standish
2012-05-06 13:51 ` Jan Engelhardt
2012-05-04 0:17 ` Humberto Jucá
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=4FA24C69.4000607@ngs.ru \
--to=eyatsko@ngs.ru \
--cc=netfilter@vger.kernel.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.