[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZtG/Ai88bIRFZZ6Y@gmail.com>
Date: Fri, 30 Aug 2024 05:45:54 -0700
From: Breno Leitao <leitao@...ian.org>
To: Florian Westphal <fw@...len.de>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, Pablo Neira Ayuso <pablo@...filter.org>,
Jozsef Kadlecsik <kadlec@...filter.org>,
David Ahern <dsahern@...nel.org>, rbc@...a.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
netfilter-devel@...r.kernel.org,
"open list:NETFILTER" <coreteam@...filter.org>
Subject: Re: [PATCH nf-next v4 1/2] netfilter: Make IP6_NF_IPTABLES_LEGACY
selectable
Hello Florian,
On Thu, Aug 29, 2024 at 06:25:12PM +0200, Florian Westphal wrote:
> Breno Leitao <leitao@...ian.org> wrote:
> > This option makes IP6_NF_IPTABLES_LEGACY user selectable, giving
> > users the option to configure iptables without enabling any other
> > config.
>
> I don't get it.
>
> IP(6)_NF_IPTABLES_LEGACY without iptable_filter, mangle etc.
> is useless,
Correct. We need to have iptable_filter, mangle, etc available.
I would like to have ip6_tables as built-in
(IP(6)_NF_IPTABLES_LEGACY=y), all the other tables built as modules.
So, I am used to a configure similar to the following (before
a9525c7f6219c ("netfilter: xtables: allow xtables-nft only builds"))
CONFIG_IP6_NF_IPTABLES=y
CONFIG_IP6_NF_MANGLE=m
CONFIG_IP6_NF_RAW=m
...
After a9525c7f6219c ("netfilter: xtables: allow xtables-nft only
builds"), the same configuration is not possible anymore, because
CONFIG_IP6_NF_IPTABLES is not user selectable anymore, thus, in order to
set it as built-in (=y), I need to set the tables as =y.
Sorry for not being clear before, and thanks for reviewing it.
--breno
Powered by blists - more mailing lists