From: Patrick McHardy <kaber@trash.net>
To: Eric Leblond <eric@inl.fr>
Cc: Kuzin Andrey <kuzinandrey@yandex.ru>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH]: drop packet without verdict from nfqueue after timeout
Date: Mon, 23 Mar 2009 23:15:09 +0100 [thread overview]
Message-ID: <49C809ED.8070308@trash.net> (raw)
In-Reply-To: <1237845953.4786.47.camel@ice-age>
Eric Leblond wrote:
>> There's a very easy and cheap way to handle this. The packets have
>> sequence numbers and userspace should issues verdicts in ascending
>> order anyways to avoid reordering. Just add something that will drop
>> everything in the queue up to the sequence number contained in the
>> netlink message.
>>
>
> I don't think the described mechanism is generic enough to be a default
> behaviour. It should be useful for projects like snort-inline but it
> will really a problem for software like NuFW which are asynchronous by
> design.
>
> In NuFW, packet authentication is triggered by a user message (signing
> of packet is done is userspace). Thus the ordering of the answer depends
> of the ordering of user messages. As NuFW authenticate packet at network
> scale (there is thus plenty of users), it is not possible to assume that
> the answer will be ordered.
>
> Thus, even if it could be useful, this mechanism should only be
> activated by an explicit userspace query.
Good point. The in-sequence handling is also only necessary per flow,
so this definitely would need to be enabled explicitly.
next prev parent reply other threads:[~2009-03-23 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 18:48 [PATCH]: drop packet without verdict from nfqueue after timeout Kuzin Andrey
2009-03-23 19:18 ` Patrick McHardy
2009-03-23 22:05 ` Eric Leblond
2009-03-23 22:15 ` Patrick McHardy [this message]
2009-03-24 5:23 ` Re[2]: " Kuzin Andrey
2009-03-24 3:17 ` Kuzin Andrey
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=49C809ED.8070308@trash.net \
--to=kaber@trash.net \
--cc=eric@inl.fr \
--cc=kuzinandrey@yandex.ru \
--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