From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pablo Neira Ayuso Subject: Re: [PATCH 0/1] Conntrack event generation control, kernel part Date: Thu, 14 May 2009 11:32:02 +0200 Message-ID: <4A0BE512.9010003@netfilter.org> References: <4A097752.4030303@netfilter.org> <4A098B7F.6050605@netfilter.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Patrick McHardy , netfilter-devel@vger.kernel.org To: Jozsef Kadlecsik Return-path: Received: from mail.us.es ([193.147.175.20]:43840 "EHLO mail.us.es" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752882AbZENJR2 (ORCPT ); Thu, 14 May 2009 05:17:28 -0400 In-Reply-To: <4A098B7F.6050605@netfilter.org> Sender: netfilter-devel-owner@vger.kernel.org List-ID: 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. I'm going to send a patch for this. The point here is to make event groups generic enough to make them useful for all sort of applications. -- "Los honestos son inadaptados sociales" -- Les Luthiers