From: Eric Leblond <eric@regit.org>
To: Kees-Jan Hermans <hermans@fox-it.com>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: Alternatively
Date: Wed, 15 Apr 2015 13:25:36 +0200 [thread overview]
Message-ID: <1429097136.30959.4.camel@regit.org> (raw)
In-Reply-To: <EF695DA0-9C90-4E93-BDDD-875FE7F6AE00@fox-it.com>
Hi,
On Wed, 2015-04-15 at 11:21 +0000, Kees-Jan Hermans wrote:
> Could someone please explain how the nfq_set_verdict function works? More specifically, what must be in the data_len and buf parameters - an IP packet (like the one you get out of nfq_get_payload())? Must it be the same pointer as you get out of nfq_get_payload or may it be different? The documentation is a bit terse on that.
0 and NULL are ok if you don't want to do packet modification. It you
wanna modify packet then you pass the raw IP data and the length. Please
note that if you set checksum to 0 they will be compute by the kernel.
Please check:
https://home.regit.org/netfilter-en/using-nfqueue-and-libnetfilter_queue/
BR,
--
Eric Leblond <eric@regit.org>
prev parent reply other threads:[~2015-04-15 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 11:21 Alternatively Kees-Jan Hermans
2015-04-15 11:25 ` Eric Leblond [this message]
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=1429097136.30959.4.camel@regit.org \
--to=eric@regit.org \
--cc=hermans@fox-it.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox