Gecko [ lms.clinion.com ]

Name	Size	Permission
NAT-HOWTO-1.html	1.05 KB	-rw-r--r--
NAT-HOWTO-10.html	2.39 KB	-rw-r--r--
NAT-HOWTO-11.html	836 B	-rw-r--r--
NAT-HOWTO-2.html	4.17 KB	-rw-r--r--
NAT-HOWTO-3.html	1.34 KB	-rw-r--r--
NAT-HOWTO-4.html	4.22 KB	-rw-r--r--
NAT-HOWTO-5.html	4.95 KB	-rw-r--r--
NAT-HOWTO-6.html	8.13 KB	-rw-r--r--
NAT-HOWTO-7.html	1.22 KB	-rw-r--r--
NAT-HOWTO-8.html	1.04 KB	-rw-r--r--
NAT-HOWTO-9.html	1.97 KB	-rw-r--r--
NAT-HOWTO.html	2.53 KB	-rw-r--r--
packet-filtering-HOWTO-1.html	1.77 KB	-rw-r--r--
packet-filtering-HOWTO-10.html	2.44 KB	-rw-r--r--
packet-filtering-HOWTO-11.html	3.58 KB	-rw-r--r--
packet-filtering-HOWTO-2.html	1.48 KB	-rw-r--r--
packet-filtering-HOWTO-3.html	5.57 KB	-rw-r--r--
packet-filtering-HOWTO-4.html	2.07 KB	-rw-r--r--
packet-filtering-HOWTO-5.html	1.53 KB	-rw-r--r--
packet-filtering-HOWTO-6.html	3.35 KB	-rw-r--r--
packet-filtering-HOWTO-7.html	34.71 KB	-rw-r--r--
packet-filtering-HOWTO-8.html	1.35 KB	-rw-r--r--
packet-filtering-HOWTO-9.html	2.21 KB	-rw-r--r--
packet-filtering-HOWTO.html	2.69 KB	-rw-r--r--

Code Editor : NAT-HOWTO-10.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.72">
 <TITLE>Linux 2.4 NAT HOWTO: Destination NAT Onto the Same Network</TITLE>
 <LINK HREF="NAT-HOWTO-11.html" REL=next>
 <LINK HREF="NAT-HOWTO-9.html" REL=previous>
 <LINK HREF="NAT-HOWTO.html#toc10" REL=contents>
</HEAD>
<BODY>
<A HREF="NAT-HOWTO-11.html">Next</A>
<A HREF="NAT-HOWTO-9.html">Previous</A>
<A HREF="NAT-HOWTO.html#toc10">Contents</A>
<HR>
<H2><A NAME="s10">10.</A> <A HREF="NAT-HOWTO.html#toc10">Destination NAT Onto the Same Network</A></H2>

If you are doing port forwarding back onto the same network, you
need to make sure that both future packets and reply packets pass
through the NAT box (so they can be altered). The NAT code will now
(since 2.4.0-test6), block the outgoing ICMP redirect which is
produced when the NAT'ed packet heads out the same interface it came
in on, but the receiving server will still try to reply directly to
the client (which won't recognize the reply).

The classic case is that internal staff try to access your `public'
web server, which is actually DNAT'ed from the public address
(1.2.3.4) to an internal machine (192.168.1.1), like so:

<BLOCKQUOTE><CODE>
<PRE>
# iptables -t nat -A PREROUTING -d 1.2.3.4 \
 -p tcp --dport 80 -j DNAT --to 192.168.1.1
</PRE>
</CODE></BLOCKQUOTE>

One way is to run an internal DNS server which knows the real
(internal) IP address of your public web site, and forward all other
requests to an external DNS server. This means that the logging on
your web server will show the internal IP addresses correctly.

The other way is to have the NAT box also map the source IP address
to its own for these connections, fooling the server into replying
through it. In this example, we would do the following (assuming the
internal IP address of the NAT box is 192.168.1.250):

<BLOCKQUOTE><CODE>
<PRE>
# iptables -t nat -A POSTROUTING -d 192.168.1.1 -s 192.168.1.0/24 \
 -p tcp --dport 80 -j SNAT --to 192.168.1.250
</PRE>
</CODE></BLOCKQUOTE>

Because the PREROUTING rule gets run first, the packets will
already be destined for the internal web server: we can tell which
ones are internally sourced by the source IP addresses.

<HR>
<A HREF="NAT-HOWTO-11.html">Next</A>
<A HREF="NAT-HOWTO-9.html">Previous</A>
<A HREF="NAT-HOWTO.html#toc10">Contents</A>
</BODY>
</HTML>

${this.title}

Code Editor : NAT-HOWTO-10.html