From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter <netfilter@lists.samba.org>
Subject: Re: Want to do NAT for internal machines
Date: Sat, 1 Jun 2002 17:05:53 +0100 [thread overview]
Message-ID: <200206011605.g51G5rA04402@Networker.rockstone.co.uk> (raw)
In-Reply-To: <ENEBKGGOKDOEALIKAJMBMEDDCHAA.neil@JAMMConsulting.com>
On Saturday 01 June 2002 4:04 pm, Neil Aggarwal wrote:
> I have several static IPs that I can bind to the
> Internet-facing interface (eth0) of the Linux server.
> Let say that they are 11.22.33.44 to 11.22.33.99.
>
> What I want to do is set up routing so that the outside
> world can connect to one of my public IPs and that
> connection is routed to a given internal machine.
> I also want the internal machine to be able to connect
> to the outside world and go out as the public
> IP that is matched to it.
>
> Here is what I came up with:
>
> # Bind the IP to eth0
> /sbin/ifconfig eth0:1 11.22.33.55 netmask 255.255.255.0 broadcast
> 11.22.33.255
A slightly outdated way of doing it, but it'll certainly do the job. It's
the way I still do it.
> # Route incoming connections to the internal machine
> /sbin/iptables -t nat -A PREROUTING -d 11.22.33.55 -j DNAT --to
> 192.168.1.55 # Route outgoing connections from the internal machine
> /sbin/iptables -t nat -A POSTROUTING -s 192.168.1.55 -j SNAT --to
> 11.22.33.55
>
> Is this close?
Is it close ???? Absolutely spot on :-)
....so long as you accept that netfilter isn't going to be providing you with
any security whatever in a setup like this...
ie it's going to forward all packets in and out of your internal machines -
you may as well have just plugged them straight into the Internet. Put some
decent security measures on those servers, and you'll be okay.
Regards,
Antony.
next prev parent reply other threads:[~2002-06-01 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 15:04 Want to do NAT for internal machines Neil Aggarwal
2002-06-01 16:05 ` Antony Stone [this message]
2002-06-01 17:59 ` Nick Drage
2002-06-01 18:15 ` Antony Stone
2002-06-01 20:54 ` Neil Aggarwal
2002-06-01 20:59 ` Antony Stone
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=200206011605.g51G5rA04402@Networker.rockstone.co.uk \
--to=antony@soft-solutions.co.uk \
--cc=netfilter@lists.samba.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