netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Murray <30179198@student.murdoch.edu.au>
To: Eric Leblond <eleblond@inl.fr>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Caching packets with libipq
Date: Mon, 19 Jan 2009 09:31:23 +0900	[thread overview]
Message-ID: <4973C9DB.4060902@student.murdoch.edu.au> (raw)
In-Reply-To: <1232090567.3789.2.camel@ice-age>

Eric Leblond wrote:
>
> What about:
> 	http://www.nufw.org/doc/libnetfilter_queue/
>
> Real question: what is missing here ?
>
> BR,
>   
Thanks for the reply Eric. In my own opinion (things that could be done 
to improve that documentation:

1. Navigation seems a little cluttered. I think it would be better to 
just have a link to documentation on the first page and then a link on 
every subsequent page to page x + 1.

2. On the main page it would be nice to have a description of why 
libnetfilter_queue is better than libipq

3. The page needs to be easier to find. Why is there not a link to it on 
the netfilter site?

4. You don't specify the compile time commands that must be used with 
libnet filter -lnfnetlink -lnetfilter_queue

5. The example code you give includes a callback function. Can you write 
a libnetfilter_queue program without a call back? It might be easier for 
people without lots of c experience to modify and start doing things.

All of these suggestions might not be correct / easy to implement. It is 
just my opinion that they might improve the site.

Thanks for your time
Dave

  reply	other threads:[~2009-01-19  0:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16  1:41 Caching packets with libipq David Murray
2009-01-16  7:22 ` Eric Leblond
2009-01-19  0:31   ` David Murray [this message]
2009-01-19  0:47     ` Pablo Neira Ayuso
2009-01-19  3:06       ` David Murray

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=4973C9DB.4060902@student.murdoch.edu.au \
    --to=30179198@student.murdoch.edu.au \
    --cc=eleblond@inl.fr \
    --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 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).