From: Patrick McHardy <kaber@trash.net>
To: Krzysztof Oledzki <ole@ans.pl>
Cc: Netfilter Developer Mailing List <netfilter-devel@lists.netfilter.org>
Subject: Re: What should we do with packets marked as INVALID?
Date: Mon, 15 Jan 2007 15:35:00 +0100 [thread overview]
Message-ID: <45AB9114.2040804@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0701151131080.13986@bizon.gios.gov.pl>
Krzysztof Oledzki wrote:
>
> On Wed, 10 Jan 2007, Patrick McHardy wrote:
>
>> Krzysztof Oledzki wrote:
>>
>>> So OK, REJECT is wrong (possibly kills valid connections), DROP (makes
>>> invalid connections hang "forever") is also wrong, so maybe we should
>>> forward such packets and allow dst hosts to handle it
>>> (ignore/reset/etc). Bzzzz... no, wait, it is also wrong as we lose one
>>> of the most important netfilter feature.
>>
>>
>>
>> DROP shouldn't make sessions hang (otherwise they would break with NAT
>> as well)
>
>
> It blocks until timeout which sometimes simply takes to long.
Not sure if I understand you correctly, but if dropping INVALID packets
makes the session hang, this would mean that valid packets are
incorrectly marked as INVALID, which would surprise me, since that
would also break with NAT (INVALID packets are not NATed) and I haven't
seen any reports of something like that.
prev parent reply other threads:[~2007-01-15 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-25 1:33 What should we do with packets marked as INVALID? Krzysztof Oledzki
2006-12-25 12:29 ` Jan Engelhardt
2006-12-25 14:08 ` Krzysztof Oledzki
2006-12-28 2:26 ` Pablo Neira Ayuso
2006-12-28 10:06 ` Krzysztof Oledzki
2006-12-28 16:25 ` Pablo Neira Ayuso
2006-12-28 16:36 ` Krzysztof Oledzki
2007-01-10 6:06 ` Patrick McHardy
2007-01-15 10:41 ` Krzysztof Oledzki
2007-01-15 14:35 ` Patrick McHardy [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=45AB9114.2040804@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=ole@ans.pl \
/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.