From: "Federico Cruciani" <f.cruciani@oxys.it>
To: netfilter@lists.netfilter.org
Subject: 1:1 NAT
Date: Sat, 1 Feb 2003 19:20:01 +0100 [thread overview]
Message-ID: <000101c2ca1e$8c3b6e90$0a00a8c0@oxys.lan> (raw)
> What I am trying to do is like how its done on cisco PIX i.e
> "static (inside,outside) 208.15.232.12 192.168.1.167 netmask
255.255.255.255
> 0 0"
Cisco PIX does proxy-arp automatically if the external IP address in the nat
statement is not assigned on its outside interface. So, to build something
similar, what you need is to activate proxy-arp on your Iptables box and
publish on the external network the public IP address you want to nat which
are not physically assigned on the iptables box.
Following your example, suppose that your iptables Linux box have an
<fw_outside_address> on the external interface, eth0, different from the one
you want to nat, <public_address> (which is 208.15.232.12 in your example),
to an host in your internal network which has <internal_address>. Eth1 is
the firewall internal interface with address <fw_internal_address>.
First you need two iptables rules, one for inbound packets and one for
translating outbound packets:
iptables -t nat -A PREROUTING -i eth0 -d <public_address> -j DNAT
--to-destination <internal_address>
iptables -t nat -A POSTROUTING -o eth0 -s <internal_address> -j SNAT
--to-source <public_address>
This is not sufficient for Linux and iptables to make the <internal_address>
host work on the internet as expected. We have to add commands to activate
proxy arp and to tell your firewall where the packets for <public_address>
have to be sent.
So, in the second step we have to pubilsh the <public_address> on the
external interface with the arp command:
arp -Ds <public_address> eth0 pub
(If you like, I have a patched version of the Red Hat /etc/init.d/network
script which read and set static ARPs from a file, /etc/init.d/static-arp)
Finally the most important step consists in adding a static route on the
iptables box for the <public_address> toward the inside interface where the
internal host live:
route add -host <public_address> dev eth1
This is the solution I have found working and that I'm using in a lot of
different network scenarios.
Hope this could help you.
Iok
next reply other threads:[~2003-02-01 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 18:20 Federico Cruciani [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-21 17:00 1:1 NAT Walther
2003-01-21 16:00 Mike
2003-01-21 16:41 ` Maciej Soltysiak
2003-01-22 5:21 ` Raymond Leach
2003-01-22 6:42 ` Martin Josefsson
2003-01-22 6:50 ` Raymond Leach
2003-01-22 7:02 ` Martin Josefsson
2003-01-22 7:03 ` Raymond Leach
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='000101c2ca1e$8c3b6e90$0a00a8c0@oxys.lan' \
--to=f.cruciani@oxys.it \
--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