All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Frank Myhr <fmyhr@fhmtech.com>
Cc: vtol@gmx.net, "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: [libnftnl] documentation?
Date: Thu, 26 Mar 2020 10:45:29 +0100	[thread overview]
Message-ID: <20200326094529.GD878@breakpoint.cc> (raw)
In-Reply-To: <d29b4165-34cc-ab98-e2cd-d83b2cc7f815@fhmtech.com>

Frank Myhr <fmyhr@fhmtech.com> wrote:
> On 2020/03/26 04:38, ѽ҉ᶬḳ℠ wrote:
> > Been trying to find some documentation in these places:
> > 
> > * https://netfilter.org/projects/libnftnl/
> > * https://www.netfilter.org/documentation/
> > * https://git.netfilter.org/libnftnl/tree/
> > *
> > https://wiki.nftables.org/wiki-nftables/index.php/Portal:DeveloperDocs/nftables_internals
> > 
> > 
> > but either I missed it - and thus appreciate a pointer - or there is none?
> > 
> > The aim/goal is to utilise libnftnl with json.
> 
> Do these help you?:
> https://git.netfilter.org/nftables/tree/doc/libnftables.adoc
> https://git.netfilter.org/nftables/tree/doc/libnftables-json.adoc
> 
> AFAIK libnftnl=libnftables, the older name just persists (confusingly) in
> many places.

No, these are different libraries. libnftnl is a standalone library
with low-level helpers.

libnftables is the highlevel library, its part of nftables itself.

libnftables contains the ruleset parser, for example.

  parent reply	other threads:[~2020-03-26  9:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26  8:38 [libnftnl] documentation? ѽ҉ᶬḳ℠
2020-03-26  9:32 ` Frank Myhr
2020-03-26  9:36   ` ѽ҉ᶬḳ℠
2020-03-26  9:45   ` Florian Westphal [this message]
2020-03-26  9:58     ` ѽ҉ᶬḳ℠
2020-03-26 10:12       ` Pablo Neira Ayuso
2020-03-26 10:41       ` Florian Westphal

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=20200326094529.GD878@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=fmyhr@fhmtech.com \
    --cc=netfilter@vger.kernel.org \
    --cc=vtol@gmx.net \
    /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.