From: Phil Oester <kernel@linuxace.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Jan Engelhardt <jengelh@medozas.de>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: rfc: reject use of drop in nat table
Date: Mon, 4 Aug 2008 11:05:51 -0700 [thread overview]
Message-ID: <20080804180551.GA20903@linuxace.com> (raw)
In-Reply-To: <489734F1.8040808@trash.net>
On Mon, Aug 04, 2008 at 06:57:21PM +0200, Patrick McHardy wrote:
> Well, first thought is the usual fear of breaking setups.
If they are doing this, their setup is _already_ broken. This
will fix it ;-)
> But I do agree that this makes sense, we've had a number
> of "bugreports" over the years from people how tried to
> do filtering in the nat table and didn't realize it only
> sees the first packet of a connection.
>
> Not sure - anyone else with an opinion? :)
+1
Phil
next prev parent reply other threads:[~2008-08-04 18:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 16:54 rfc: reject use of drop in nat table Jan Engelhardt
2008-08-04 16:57 ` Patrick McHardy
2008-08-04 18:05 ` Phil Oester [this message]
2008-08-04 18:55 ` Jozsef Kadlecsik
2008-08-04 19:08 ` Patrick McHardy
2008-08-10 14:44 ` Jan Engelhardt
2008-08-13 12:42 ` Patrick McHardy
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=20080804180551.GA20903@linuxace.com \
--to=kernel@linuxace.com \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--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