From: Jeff Largent <jlargent@imagelinks.com>
To: linux-admin@vger.kernel.org
Cc: rita jacques <ritajacques@lycos.fr>
Subject: Re: NAT (iptables) problem (help)
Date: Wed, 22 May 2002 15:02:22 -0400 [thread overview]
Message-ID: <3CEBEB3E.4030101@imagelinks.com> (raw)
In-Reply-To: 1022091957007296@lycos.fr
I found you also have to make sure you are allowing forwarding of
port 80 to the host, and in some cases I've had to do postrouting
something like:
iptables -t nat -A PREROUTING -i eth0 -p tcp --dport www -j DNAT --to-dest
192.168.1.20 )
iptables -t nat -A POSTROUTING -o eth0 -p tcp --sport 80 -j SNAT --to-source
xxx.xxx.xxx.xxx
iptables -A FORWARD -d 192.168.1.20 -p tcp -m tcp --dport 80 -j ACCEPT
rita jacques wrote:
> hi
> I have a LAN (linux mandrake boxes, with IP 192.168.0.1 to
> 20). I have also a gateway (linux mandrake with 2 Network
> cards eth0 with real IP AAA.BBB.CCC.DDD and eth1 with
> 192.168.0.1).
> What sould I do to redirect for example web request to
> 192.168.0.20 machine in the LAN...
> I tried iptables...not working
> (iptables -t nat -A PREROUTING -i eth0 -p tcp --dport www -
> j DNAT --to-dest 192.168.1.20 )
>
> Should I use iptables on the gateway only or on the linux
> boxes on the LAN also?
>
> What about SNAT?
> is this correct
> iptables -t nat -A POSTROUTING -o eth0 -j SNAT --to-
> source AAA.BBB.CCC.DDD
>
> Thanks
> Rita
>
> ______________________________________________________
> Boîte aux lettres - Lycos - http://www.lycos.fr
>
--
Jeff Largent ImageLinks, Inc.
Sr System Admin Melbourne, Fl 32935
(321) 253-0011 fax:(321) 253-5559
perl -e 'print unpack(u, "3=W=W+FEM86=E;&EN:W,N8V]M\"@``");'
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2002-05-22 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 18:25 NAT (iptables) problem (help) rita jacques
2002-05-22 19:02 ` Jeff Largent [this message]
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=3CEBEB3E.4030101@imagelinks.com \
--to=jlargent@imagelinks.com \
--cc=linux-admin@vger.kernel.org \
--cc=ritajacques@lycos.fr \
/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;
as well as URLs for NNTP newsgroup(s).