[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aXi26_vIXqQPhopG@strlen.de>
Date: Tue, 27 Jan 2026 14:00:27 +0100
From: Florian Westphal <fw@...len.de>
To: "Remy D. Farley" <one-d-wide@...tonmail.com>
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
Remy D. Farley <one-d-wide@...tonmail.com> wrote:
> > 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.
No, showing unknown-operations is even worse.
Maybe just document in commit message that this is to avoid
clutter and present something more readable.
And perhaps mention that this is only for iptables-nft in the yaml file too.
(nft uses it on 'nft list' only if it encounters a rule added by iptables-nft).
Powered by blists - more mailing lists