From: Eric Leblond <eric@regit.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [RFC ulogd patch 0/1] Implement conntrack event filter in NFCT input
Date: Mon, 03 Sep 2012 09:36:50 +0200 [thread overview]
Message-ID: <1346657810.5194.44.camel@tiger.regit.org> (raw)
In-Reply-To: <20120802112344.GB25007@1984>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
Hello,
Sorry for being late to reply here.
Le jeudi 02 août 2012 à 13:23 +0200, Pablo Neira Ayuso a écrit :
> On Wed, Aug 01, 2012 at 11:33:28PM +0200, Eric Leblond wrote:
> >
> > Hello,
...
> Note that ulogd2 initially dumps the entire table. The filtering will
> not apply to dumping, only to events.
Why is this needed ? This gave us more accurate stats about existing
connection by filling the hash at start ?
>
> You need to filter filter dumps.
>
> conntrackd already has a framework for user-space filtering, that is
> used for filter. You can grab it. We can probably later move it to
> libnetfilter_conntrack to avoid code redundancy.
I've looked at this part of the code but the implementation seems to
need a lot of conntrackd things like vector. This seems a bit too big to
include inside ulogd.
BR,
--
Eric Leblond
Blog: http://home.regit.org/ - Portfolio: http://regit.500px.com/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-09-03 7:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 21:33 [RFC ulogd patch 0/1] Implement conntrack event filter in NFCT input Eric Leblond
2012-08-01 21:33 ` [RFC ulogd PATCH] nfct: implement src and dst filter Eric Leblond
2012-08-02 11:21 ` Pablo Neira Ayuso
2012-08-02 11:23 ` [RFC ulogd patch 0/1] Implement conntrack event filter in NFCT input Pablo Neira Ayuso
2012-09-03 7:36 ` Eric Leblond [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=1346657810.5194.44.camel@tiger.regit.org \
--to=eric@regit.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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;
as well as URLs for NNTP newsgroup(s).