From: "Bryan Martin" <bmartin@myplaceinspace.com>
To: netfilter@lists.netfilter.org
Subject: Internal NAT Translation:
Date: Wed, 30 Jun 2004 21:43:08 -0400 [thread overview]
Message-ID: <002101c45f0c$c2b90c50$0c02a8c0@bryanhome> (raw)
Setup looks like this
Internet
^
Redhat 9 iptables nat/masq (200.200.200.200 public address = eth1;
192.168.2.1 private address = eth0)
^
windows web server (192.168.2.254) | windows clients. (all 192.168.2.X)
Now the rh box is masquerading for the private boxes. Only thing not
standard is that any inbound http connections to the public address
200.200.200.200 is being dnatted to 192.168.2.254 which is the address of
the windows server. This is working as expected. The problem arises when a
internal client tries to connect to the public website.
For instance client request www.mycompany.com and DNS says go here
200.200.200.200 which would be correct if I was sitting on the outside
looking in. I need iptables to basically say if any http request comes from
the internal network addressed to my public address dnat the public
200.200.200.200 to the private address. I have tried the following without
success. Only other thing I know is to setup a internal DNS just so the
internal clients get the internal address. That would however be an extreme
waste of resources.
-A PREROUTING -i eth1 -d 200.200.200.200 -p tcp --dport 80 -j
DNAT --to-destination 192.168.2.254
Can someone help?
Bryan
next reply other threads:[~2004-07-01 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 1:43 Bryan Martin [this message]
2004-07-04 13:04 ` Internal NAT Translation: Antony Stone
2004-07-05 12:05 ` ro0ot
-- strict thread matches above, loose matches on Subject: below --
2004-07-01 1:45 Bryan Martin
2004-07-01 3:18 ` John A. Sullivan III
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='002101c45f0c$c2b90c50$0c02a8c0@bryanhome' \
--to=bmartin@myplaceinspace.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.