From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Patrick McHardy <kaber@trash.net>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 0/1] Conntrack event generation control, kernel part
Date: Thu, 14 May 2009 12:44:19 +0200 [thread overview]
Message-ID: <4A0BF603.9090600@netfilter.org> (raw)
In-Reply-To: <4A0BE512.9010003@netfilter.org>
Pablo Neira Ayuso wrote:
> Hi Jozsef,
>
> Pablo Neira Ayuso wrote:
>> I see, but something similar to nfnetlink_queue/NFQUEUE (per-process)
>> together with an extended version of the `conntrack match' for events
>> would be more flexible
>
> Another very simple choice can be to add more multicast groups according
> to the sort of events. We can get more fine grain event selection while
> keeping it per-process. Currently, there's only three sort of events:
> NEW, UPDATE and DESTROY. We can add more netlink multicast groups to
> allow user-space to select what kind of events they are interested.
netlink doesn't seem to support overlapping event groups, and UPDATE and
ASSURED groups would overlap. Thus, we'll need to call
netlink_broadcast() twice. I still don't find a non-intrusive way to do
some non-BPF-based filtering :(
--
"Los honestos son inadaptados sociales" -- Les Luthiers
next prev parent reply other threads:[~2009-05-14 10:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 11:52 [PATCH 0/1] Conntrack event generation control, kernel part Jozsef Kadlecsik
2009-05-12 12:46 ` Jan Engelhardt
2009-05-12 13:19 ` Jozsef Kadlecsik
2009-05-12 13:23 ` Pablo Neira Ayuso
2009-05-12 13:19 ` Pablo Neira Ayuso
2009-05-12 13:41 ` Jozsef Kadlecsik
2009-05-12 14:45 ` Pablo Neira Ayuso
2009-05-14 9:32 ` Pablo Neira Ayuso
2009-05-14 10:44 ` Pablo Neira Ayuso [this message]
2009-05-15 19:07 ` Jozsef Kadlecsik
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=4A0BF603.9090600@netfilter.org \
--to=pablo@netfilter.org \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--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 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.