From: Sheldon Hearn <sheldonh@starjuice.net>
To: Michael Rowley MD <mrowleymd@earthlink.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: routing external IP's to internal machines.... Confustion
Date: Thu, 10 Jun 2004 01:18:51 +0200 [thread overview]
Message-ID: <1086823131.5011.30.camel@axl.seasidesoftware.co.za> (raw)
In-Reply-To: <6781F74D-BA66-11D8-8DB6-000A95675988@earthlink.net>
On Thu, 2004-06-10 at 00:43, Michael Rowley MD wrote:
> I have a block of IP's from Sprint, 209.26.244.33/29. I have 2 servers
> inside the firewall that I would like to have accessible from the
> internet on an external fixed IP. Currently the internal network is on
> 192.168.1.0/24, the firewall is working, and I can ssh into the
> firewall, but would like to ssh into all the servers, and need web
> access to both also. I will try and diagram this, just to ellucidate.
Do source nat and destination nat in both PREROUTING and POSTROUTING,
ignoring the interface on which the packets are seen. E.g.
-A PREROUTING -j dst-nat
-A POSTROUTING -j src-nat
-A dst-nat -d 209.26.244.33 -j DNAT --to-destination 192.168.1.33
...
-A src-nat -s 192.168.1.33 -j SNAT --to-source 209.26.244.33
...
This assumes that you don't want to set up a DNS server that gives
"fake" answers to clients on 192.168.1.0/24.
Both approaches work for me. YMMV.
Ciao,
Sheldon.
prev parent reply other threads:[~2004-06-09 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 22:43 routing external IP's to internal machines.... Confustion Michael Rowley MD
2004-06-09 22:59 ` John A. Sullivan III
2004-06-09 23:18 ` Sheldon Hearn [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=1086823131.5011.30.camel@axl.seasidesoftware.co.za \
--to=sheldonh@starjuice.net \
--cc=mrowleymd@earthlink.net \
--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