[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zuq3ns-Ai05Hcooj@calendula>
Date: Wed, 18 Sep 2024 13:21:02 +0200
From: Pablo Neira Ayuso <pablo@...filter.org>
To: Breno Leitao <leitao@...ian.org>
Cc: fw@...len.de, davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, rbc@...a.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, netfilter-devel@...r.kernel.org
Subject: Re: [PATCH nf-next v5 0/2] netfilter: Make IP_NF_IPTABLES_LEGACY
selectable
On Wed, Sep 18, 2024 at 01:13:32PM +0200, Pablo Neira Ayuso wrote:
> On Mon, Sep 09, 2024 at 01:46:17AM -0700, Breno Leitao wrote:
> > These two patches make IP_NF_IPTABLES_LEGACY and IP6_NF_IPTABLES_LEGACY
> > Kconfigs user selectable, avoiding creating an extra dependency by
> > enabling some other config that would select IP{6}_NF_IPTABLES_LEGACY.
>
> This needs a v6. There is also:
>
> BRIDGE_NF_EBTABLES_LEGACY
>
> We have more copy and paste in the bridge.
>
> Would you submit a single patch covering this too?
There is also:
# ARP tables
config IP_NF_ARPTABLES
tristate
which has never had a description. Could you also add?
arptables is a legacy packet classification.
This is not needed if you are using arptables over nftables
(iptables-nft).
There is no need for _LEGACY in this case.
Single patch to update them all should be fine.
Thanks
Powered by blists - more mailing lists