From: Al Boldi <a1426z@gawab.com>
To: Valdis.Kletnieks@vt.edu
Cc: Bill Davidsen <davidsen@tmr.com>,
Patrick McHardy <kaber@trash.net>,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFD] iptables: mangle table obsoletes filter table
Date: Sun, 21 Oct 2007 07:31:58 +0300 [thread overview]
Message-ID: <200710210731.58959.a1426z@gawab.com> (raw)
In-Reply-To: <26556.1192855654@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> On Sat, 20 Oct 2007 06:40:02 +0300, Al Boldi said:
> > Sure, the idea was to mark the filter table obsolete as to make people
> > start using the mangle table to do their filtering for new setups. The
> > filter table would then still be available for legacy/special setups.
> > But this would only be possible if we at least ported the REJECT target
> > to mangle.
>
> That's *half* the battle. The other half is explaining why I should move
> from a perfectly functional setup that uses the filter table. What gains
> do I get from doing so? What isn't working that I don't know about? etc?
>
> In other words - why do I want to move from filter to mangle?
This has already been explained in this thread; here it is again:
Al Boldi wrote:
>>>The problem is that people think they are safe with the filter table,
>>>when in fact they need the prerouting chain to seal things. Right now
>>>this is only possible in the mangle table.
>>
>>Why do they need PREROUTING?
>
> Well, for example to stop any transient packets being forwarded. You could
> probably hack around this using mark's, but you can't stop the implied
> route lookup, unless you stop it in prerouting.
Basically, you have one big unintended gaping whole in your firewall, that
could easily be exploited for DoS attacks at the least, unless you put in
specific rules to limit this.
Plus, it's outrageously incorrect to accept invalid packets, just because
your filtering infrastructure can only reject packets after they have been
prerouted.
Thanks!
--
Al
next prev parent reply other threads:[~2007-10-21 4:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 21:31 [RFD] iptables: mangle table obsoletes filter table Al Boldi
2007-10-12 4:35 ` Patrick McHardy
2007-10-12 4:39 ` Patrick McHardy
2007-10-12 5:37 ` Al Boldi
2007-10-12 11:48 ` Patrick McHardy
2007-10-12 12:25 ` Al Boldi
2007-10-12 12:31 ` Patrick McHardy
2007-10-12 13:18 ` Al Boldi
2007-10-12 13:23 ` Patrick McHardy
2007-10-12 22:56 ` Al Boldi
2007-10-17 22:37 ` Bill Davidsen
2007-10-17 23:24 ` Bill Davidsen
2007-10-20 3:40 ` Al Boldi
2007-10-20 4:47 ` Valdis.Kletnieks
2007-10-20 11:10 ` Jan Engelhardt
2007-10-21 4:31 ` Al Boldi [this message]
2007-10-21 4:53 ` Valdis.Kletnieks
2007-10-23 22:27 ` Bill Davidsen
2007-10-12 13:01 ` Jan Engelhardt
2007-10-12 13:30 ` Al Boldi
2007-10-12 13:39 ` Jan Engelhardt
2007-10-12 13:48 ` Patrick McHardy
2007-10-12 14:02 ` Jan Engelhardt
2007-10-12 14:03 ` Patrick McHardy
2007-10-12 22:56 ` Al Boldi
2007-10-12 23:02 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2007-10-12 5:14 Al Boldi
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=200710210731.58959.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=davidsen@tmr.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).