From: Pablo Neira <pablo@eurodev.net>
To: netfilter-devel@lists.netfilter.org
Subject: Re: NF_QUEUE examples
Date: Fri, 16 Apr 2004 01:55:06 +0200 [thread overview]
Message-ID: <407F20DA.2050704@eurodev.net> (raw)
In-Reply-To: <20040415162220.GA5747@maluco.com.br>
Hi Ulysses,
Ulysses Almeida wrote:
> where can i find simple examples of using it?
>
http://cvs.netfilter.org/netfilter/testsuite/tools/intercept.c
it hasn't been modified for quite some time but it works.
> What I understand, is: with NF_QUEUE, I can queue some packet to be
>manipulated on userspace. After this, can this packet be dequeued back
>to kernel space, and continue with it's journey?
>
exactly
> How can I write a
>userspace code, to handle with packetd queued bu NF_QUEUE? Or I didn't
>understand nothing about it?
>
>
as Sven pointed out, if you are interested you could have a look at
ip_queue.c in kernel side.
regards,
Pablo
next prev parent reply other threads:[~2004-04-15 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 16:22 NF_QUEUE examples Ulysses Almeida
2004-04-15 17:25 ` Sven Schuster
2004-04-15 23:55 ` Pablo Neira [this message]
2004-04-16 9:45 ` Henrik Nordstrom
-- strict thread matches above, loose matches on Subject: below --
2004-04-16 8:23 Richard Bishop
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=407F20DA.2050704@eurodev.net \
--to=pablo@eurodev.net \
--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.