From: Patrick McHardy <kaber@trash.net>
To: aton <aton@packetdropped.org>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: netfilter_queue reinjecting packets
Date: Sun, 12 Mar 2006 20:35:40 +0100 [thread overview]
Message-ID: <4414780C.60907@trash.net> (raw)
In-Reply-To: <20060312202133.08f8d8ee.aton@packetdropped.org>
aton wrote:
>>nfnql_test already reinjects packets by the call to nfq_issue_verdict.
>>It seems you need to read the documentation ..
>>
>
> sorry, but i cannot find any call to nfq_issue_verdict in this file.
> perhaps you mean nfq_set_verdict(qh, id, NF_ACCEPT, 0, NULL); ?
Yes, thats what I meant.
> i thought nfq_set_verdict was used to specify a handling routine for the packets... in the case of nfq_test.c set the handling routine for packets to the print_pkt() function.
> am i wrong?
Yes. nfq_set_verdict is used to tell the kernel to pass the packet
on and possibly exchange it. Both print_pkt and nfq_set_verdict
are called from the packet callback in the example code.
> what documentation? i would _love_ to read some documentation about libnetfilter_queue.
> i have looked through http://netfilter.org/documentation/index.html#documentation-howto but i cannot find anything specific about libnetfilter_queue...
I don't think there is specific libnetfilter_queue documentation yet
(but its very simple and exports only a few functions, look at the
code). But we have ip_queue documentation, which should at least
help you understand it better conceptually.
next prev parent reply other threads:[~2006-03-12 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-11 23:24 volunteer tcl script writer needed for iptables application John A. Sullivan III
2006-03-12 14:10 ` netfilter_queue reinjecting packets aton
2006-03-12 14:44 ` Patrick McHardy
2006-03-12 19:21 ` aton
2006-03-12 19:35 ` Patrick McHardy [this message]
2006-03-14 12:54 ` aton
2006-03-14 16:46 ` Patrick McHardy
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=4414780C.60907@trash.net \
--to=kaber@trash.net \
--cc=aton@packetdropped.org \
--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.