From: Philip Pemberton <usenet06@philpem.me.uk>
To: netfilter@lists.netfilter.org
Subject: Re: NATing on a single interface?
Date: Thu, 26 Oct 2006 21:44:06 +0100 [thread overview]
Message-ID: <ehr6m6$v00$1@sea.gmane.org> (raw)
In-Reply-To: <ehql65$f08$1@sea.gmane.org>
Robert Nichols wrote:
> There's no reason a forwarded packet can't go back out the same
> interface on which it arrived. There's an obvious compromise in
> security when you have both sides of the firewall on the same
I do trust my own machines, basically because they're mine - I'm very
obsessive about keeping the OS and virus scanners up to date.
> physical network, but if you trust your own machines and just
> want to protect against external attacks you should be OK as
> long as the DSL router forwards packets to the firewall machine
> only.
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....
Thanks.
--
Phil. | (\_/) This is Bunny. Copy and paste Bunny
usenet06@philpem.me.uk | (='.'=) into your signature to help him gain
http://www.philpem.me.uk/ | (")_(") world domination.
If mail bounces, replace "06" with the last two digits of the current year.
next prev parent reply other threads:[~2006-10-26 20:44 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 [this message]
2006-10-26 23:52 ` Robert Nichols
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='ehr6m6$v00$1@sea.gmane.org' \
--to=usenet06@philpem.me.uk \
--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.