From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: netfilter@lists.netfilter.org
Subject: Re: NATing on a single interface?
Date: Thu, 26 Oct 2006 18:52:44 -0500 [thread overview]
Message-ID: <ehrhod$17a$1@sea.gmane.org> (raw)
In-Reply-To: <ehr6m6$v00$1@sea.gmane.org>
Philip Pemberton wrote:
> It appears to be mangling the packets - e.g. an inbound packet from
> 12.34.56.78 to 98.76.54.32 (PPP_IP) gets its destination IP changed to
> the DMZ address (e.g. 10.0.0.1 for my server). Return packets are sent
> to the source (e.g. 12.34.56.78 in the example) using the DSL router
> (10.1.0.2) as the gateway.
>
> What I need to figure out is how to actually set up the firewall. I >
> did find a nice IPTables tutorial, but it's 357 pages long! Guess I'd
> better stop procrastinating and start reading....
If your other machines are set up to use the DSL router as the default
route, of course that's where the return packets will go. You have
two choices:
1. (Preferable) Set up the default route on your other machines so
that they use the firewall machine as their gateway to the outside
world.
2. SNAT the forwarded packets so that they appear to come from the
firewall machine. This really screws up logging on your other
machines (all traffic will appear to originate on the firewall
machine), so you probably don't want to do it that way.
If that's Oskar Andreasson's tutorial you've got, you'll find you
really don't need to read through the whole thing. The section on
the DNAT target is what you need right now.
--
Bob Nichols Yes, "NOSPAM" is really part of my email address.
next prev parent reply other threads:[~2006-10-26 23:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 9:08 NATing on a single interface? Philip Pemberton
2006-10-26 15:45 ` Robert Nichols
2006-10-26 20:44 ` Philip Pemberton
2006-10-26 23:52 ` Robert Nichols [this message]
2006-10-27 9:09 ` Philip Pemberton
2006-10-27 14:40 ` Robert Nichols
2006-10-27 19:33 ` Port forwarding fun (was NATing on a single interface?) Philip Pemberton
2006-10-27 20:26 ` Philip Pemberton
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='ehrhod$17a$1@sea.gmane.org' \
--to=rnicholsnospam@comcast.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 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.