From: Kevin Buhr <buhr@telus.net>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stateless dropping of packets
Date: 02 Apr 2003 09:00:18 -0800 [thread overview]
Message-ID: <87wuickf6l.fsf@saurus.asaurus.invalid> (raw)
In-Reply-To: <87wuidndre.fsf@deneb.enyo.de>
Florian Weimer <fw@deneb.enyo.de> writes:
>
> Is this extremely important application of the PREROUTING chain
> documented somewhere? Should I feel embarrassed? 8-)
No, I haven't seen it documented explicitly. It's just a fortunate
side effect of the fact that the DROP target can be used anywhere and
there's a fairly general-purpose table ("mangle") that has a
PREROUTING chain.
There's no particular reason for the "filter" table *not* to implement
PREROUTING and POSTROUTING chains (at least not that I can see) except
for a very small performance hit. I guess no one thought there'd be
much of a use for them. And it would break the nice rule of thumb
that a packet only passes through one of the three chains of the
"filter" table (not counting packets throught the loopback interface
which pass through OUTPUT then back through INPUT).
--
Kevin <buhr@telus.net>
prev parent reply other threads:[~2003-04-02 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 20:54 Stateless dropping of packets Florian Weimer
2003-04-01 22:50 ` Kevin Buhr
2003-04-02 15:02 ` Florian Weimer
2003-04-02 17:00 ` Kevin Buhr [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=87wuickf6l.fsf@saurus.asaurus.invalid \
--to=buhr@telus.net \
--cc=fw@deneb.enyo.de \
--cc=linux-kernel@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