From: Harald Welte <laforge@netfilter.org>
To: Elver Loho <kernelpenguin@hot.ee>
Cc: netfilter@lists.netfilter.org
Subject: Re: Possible dangerous flaw in the NAT howto
Date: Tue, 24 Jun 2003 19:10:46 +0200 [thread overview]
Message-ID: <20030624171046.GW2645@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20030622024450.19E60105939@hot.ee>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
On Sun, Jun 22, 2003 at 05:44:49AM +0300, Elver Loho wrote:
> I was on #netfilter (irc.freenode.net) earlier and asked about a
> possible flaw in the NAT howto, but got no reply (people sleeping?) so
> I'm just going to paste what I said here and go to sleep. (nearing 6am
> currently)
>
>
> <elver> I have a question about masquerading. The NAT howto gives an
> example like this: "iptables -t nat -A POSTROUTING -o ppp0 -j
> MASQUERADE", but since it masks the packets that are outgoing on ppp0
> (by the destination IP, interface IP and netmask) then could that rule
> also be exploited by outside hosts tunneling?
> [...]
Well, using nat doens't mean that you don't want to use packet filtering
anymore, does it?
I mean, apart from your MASQUERADE rule you would still have a packet
filtering ruleset in the 'filter' table, just like on any normal non-NAT
firewall.
> Elver Loho
> kernelpenguin@hot.ee
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-06-24 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-22 2:44 Possible dangerous flaw in the NAT howto Elver Loho
2003-06-22 10:49 ` Cedric Blancher
2003-06-22 20:12 ` Ramin Dousti
2003-06-24 17:10 ` Harald Welte [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=20030624171046.GW2645@sunbeam.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=kernelpenguin@hot.ee \
--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