[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2mi8BfZGa57pxicf4pXNT_oDJ3bvV7pByJOBhG8e7u_3eBbjubS3YJ88xHp4oDiMi3iY20zcG6FgF8_m5nsJJ_3CYHNftjAL_4EAqN5zeU0=@protonmail.com>
Date: Tue, 27 Jan 2026 12:44:45 +0000
From: "Remy D. Farley" <one-d-wide@...tonmail.com>
To: Florian Westphal <fw@...len.de>
Cc: Donald Hunter <donald.hunter@...il.com>, Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org, Pablo Neira Ayuso <pablo@...filter.org>, Jozsef Kadlecsik <kadlec@...filter.org>, Phil Sutter <phil@....cc>, netfilter-devel@...r.kernel.org, coreteam@...filter.org
Subject: Re: [PATCH v6 5/6] doc/netlink: nftables: Add getcompat operation
On Tuesday, January 27th, 2026 at 12:33, Florian Westphal <fw@...len.de> wrote:
> Remy D. Farley one-d-wide@...tonmail.com wrote:
>
> > > Whats the intent here? nft_compat isn't used by nftables, this
> > > is iptables-nft compatibility glue.
> >
> > I noticed getcompat operation used by `nft list ruleset` command, and it
> > doesn't seem to be defined anywhere else. Should I re/move it?
>
>
> Its used by compatibility mode, it requires an nft binary linked
> to libxtables, native nftables doesn't need it.
>
> I would prefer not to mention its existence.
Ah, I see. Netlink-bindings have a tool to decode netlink communication, so
it's a bit awkward to show a bunch of unkown-operations on a common command.
I'm fine keeping it downstream.
Powered by blists - more mailing lists