From: Sebastien Tandel <standel@info.ucl.ac.be>
To: netfilter-devel@lists.netfilter.org
Subject: [Fwd: Re: bloom filter in netfilter?]
Date: Tue, 20 Mar 2007 17:37:51 +0100 [thread overview]
Message-ID: <46000DDF.70509@info.ucl.ac.be> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
forgot to CC to the list ... :-/
Patrick McHardy wrote:
> Pablo Neira Ayuso wrote:
>>> I was then wondering if we could not get rid of these two
>>> list_for_each_entry in the __nf_conntrack_confirm by using the bloom
>>> filters.
>>
>> We can't just get rid of it since bloom filters have false positives, so
>> it could happen that we could miss some new connections that are not
>> actually in the conntrack table.
>
>
> That wouldn't be a big problem in my opinion, you can freely tune the
> probability.
>
In the specific case I was speaking about, you don't expect to find
anything. Therefore, as Patrick says, if you tune the probability of
false positives, you should not expect ones really often. If one occurs,
of course, you have to verify it in the list.
Regards,
Sebastien Tandel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGAA3fw76McB8jGxkRCnGjAJ0diPmS3tmxWs/sqymSuSXS1S/aWgCgm/JO
Abrg/mwtbgdUzbnXhqR9GcA=
=LBzy
-----END PGP SIGNATURE-----
next reply other threads:[~2007-03-20 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 16:37 Sebastien Tandel [this message]
2007-03-20 19:27 ` bloom filter in netfilter? Pablo Neira Ayuso
2007-03-20 21:41 ` Sebastien Tandel
2007-03-21 12:45 ` Sebastien Tandel
2007-03-21 12:46 ` Sebastien Tandel
2007-03-21 15:00 ` Jozsef Kadlecsik
-- strict thread matches above, loose matches on Subject: below --
2007-03-20 16:38 [Fwd: Re: bloom filter in netfilter?] Sebastien Tandel
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=46000DDF.70509@info.ucl.ac.be \
--to=standel@info.ucl.ac.be \
--cc=netfilter-devel@lists.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 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.