From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Eric Leblond <eric@regit.org>
Cc: credzba@gmail.com, dorian33@o2.pl, netfilter@vger.kernel.org
Subject: Re: libnetfilter_queue issues
Date: Sun, 13 Jan 2013 12:29:40 +0100 [thread overview]
Message-ID: <20130113112940.GA15424@1984> (raw)
In-Reply-To: <1358017441.18655.1.camel@tiger2>
On Sat, Jan 12, 2013 at 08:04:01PM +0100, Eric Leblond wrote:
> Hello,
>
> On Sat, 2013-01-12 at 07:23 -0600, Felix wrote:
> > excellent question !
> > I too am interested in this.
> >
> > Another similar, related question is do packets that are not filtered
> > wait on a verdict for a filtered packet?
> > Again, if not, it means we can change packet order?
> > If so,it means we can degrade system performance unrelated to our
> > filtered packets.
>
> I've just wrote an article describing libnetfilter_queue and NFQUEUE. It
> has been written to answer your questions:
> https://home.regit.org/netfilter-en/using-nfqueue-and-libnetfilter_queue/
It would be good to integrate part of this information to the doxygen
library documentation:
http://www.netfilter.org/projects/libnetfilter_queue/
Or simply add reference to Eric's page in the main page of the doxygen.
Regards.
next prev parent reply other threads:[~2013-01-13 11:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 12:43 libnetfilter_queue issues dorian
2013-01-12 13:23 ` Felix
2013-01-12 19:04 ` Eric Leblond
2013-01-12 19:00 ` Felix
2013-01-12 21:16 ` dorian
2013-01-12 22:12 ` Eric Leblond
2013-01-12 22:34 ` dorian
2013-01-13 11:29 ` Pablo Neira Ayuso [this message]
2013-01-13 22:46 ` Eric Leblond
2013-01-13 22:49 ` [libnetfilter_queue PATCH 1/2] doxygen: improve fail-open documentation Eric Leblond
2013-01-13 22:49 ` [libnetfilter_queue PATCH 2/2] doxygen: improve documentation Eric Leblond
2013-01-14 14:24 ` libnetfilter_queue issues dorian
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=20130113112940.GA15424@1984 \
--to=pablo@netfilter.org \
--cc=credzba@gmail.com \
--cc=dorian33@o2.pl \
--cc=eric@regit.org \
--cc=netfilter@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.