From: Fabian Franz <s1410239008@students.fh-hagenberg.at>
To: <netfilter-devel@vger.kernel.org>
Subject: Re: [Question] Is there some documentation for nftables development
Date: Wed, 15 Feb 2017 18:21:47 +0100 [thread overview]
Message-ID: <fb394aca-8979-332d-c1f0-cbffef52f581@students.fh-hagenberg.at> (raw)
In-Reply-To: <d73038eb-3609-d4a8-85af-30c81174eb3d@mindchasers.com>
Dear Mr. Cochran,
even if your document looks good, I am looking for some documentation
related to nftables - iptables is NO option because I want to implement
a kernel module for nftables doing that.
The problem is, that there is a wiki how to use it, but there is no
information how to extend it:
https://wiki.nftables.org/wiki-nftables/index.php/Main_Page
Kind regards
Fabian Franz
Am 2017-02-15 um 17:44 schrieb Bob Cochran:
> If you don't mind using iptables/Xtables instead:
> http://inai.de/documents/Netfilter_Modules.pdf
>
>
>
> On 02/15/2017 08:59 AM, Fabian Franz wrote:
>> Hi there,
>>
>> is there some documentation available how to create a custom match for a
>> firewall rule (nftables).
>>
>> What I want to create is a custom match which will query a user space
>> application, if the packet is allowed (returning a bool value)?
>>
>> Kind regards
>>
>> Fabian Franz
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> netfilter-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
next prev parent reply other threads:[~2017-02-15 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 13:59 [Question] Is there some documentation for nftables development Fabian Franz
[not found] ` <d73038eb-3609-d4a8-85af-30c81174eb3d@mindchasers.com>
2017-02-15 17:21 ` Fabian Franz [this message]
2017-02-15 18:37 ` Anatole Denis
2017-02-15 19:33 ` Fabian Franz
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=fb394aca-8979-332d-c1f0-cbffef52f581@students.fh-hagenberg.at \
--to=s1410239008@students.fh-hagenberg.at \
--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 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.