All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anatole Denis <natolumin@gmail.com>
To: Fabian Franz <s1410239008@students.fh-hagenberg.at>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [Question] Is there some documentation for nftables development
Date: Wed, 15 Feb 2017 19:37:54 +0100	[thread overview]
Message-ID: <1487183874.795.1@smtp.gmail.com> (raw)
In-Reply-To: <fb394aca-8979-332d-c1f0-cbffef52f581@students.fh-hagenberg.at>

On mer., févr. 15, 2017 at 6:21 , Fabian Franz 
<s1410239008@students.fh-hagenberg.at> wrote:
> 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

 From your description, "query a user space application, if the packet 
is allowed", seems to be exactly nfqueue, which is already developed 
and in mainline kernel, and supported by nftables. The wiki you link to 
has a page on it: 
https://wiki.nftables.org/wiki-nftables/index.php/Queueing_to_userspace.

As you can also see in the link, there is a userspace library for it, 
libnetfilter_queue, as well.

The question is maybe, do you want to solve a problem (in which case I 
believe nfqueue could be a solution), or write a kernel module (in 
which case, sorry to be useless, I don't know about any documentation 
on the kernel side of netfilter) ?

--
Anatole


  reply	other threads:[~2017-02-15 18:37 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
2017-02-15 18:37     ` Anatole Denis [this message]
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=1487183874.795.1@smtp.gmail.com \
    --to=natolumin@gmail.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=s1410239008@students.fh-hagenberg.at \
    /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.