From: Breno Leitao <leitao@debian.org>
To: Florian Westphal <fw@strlen.de>
Cc: rbc@meta.com, netfilter-devel@vger.kernel.org
Subject: Re: netfilter: Kconfig: IP6_NF_IPTABLES_LEGACY old =y behaviour question
Date: Thu, 22 Aug 2024 10:55:18 -0700 [thread overview]
Message-ID: <Zsd7hk8SMQoHKjwR@gmail.com> (raw)
In-Reply-To: <20240822132022.GA25665@breakpoint.cc>
Hello Florian,
On Thu, Aug 22, 2024 at 03:20:22PM +0200, Florian Westphal wrote:
> Breno Leitao <leitao@debian.org> wrote:
> > On Thu, Aug 22, 2024 at 01:23:39PM +0200, Florian Westphal wrote:
> > In certain environments, iptables needs to run, but there is *no*
> > permission to load modules.
> >
> > For those cases, I have CONFIG_IP6_NF_IPTABLES configured as y in
> > previous kernels, and now it becomes a "m", which doesn't work because
> > iptables doesn't have permission to load modules, returning:
> >
> > $ ip6tables -L
> > modprobe: FATAL: Module ip6_tables not found in directory /lib/modules/....
> > ip6tables v1.8.10 (legacy): can't initialize ip6tables table `filter': Table does not exist (do you need to insmod?)
> > Perhaps ip6tables or your kernel needs to be upgraded.
>
> Hmm, but how can that work? If you can't load modules, you can't load
> ip6t_filter either.
This happens inside a container that has no support for module loading, and
expects the tables to be =y.
> And if thats builtin, then IP6_NF_IPTABLES_LEGACY is supposed to become
> =y too.
Correct, both of them (IP6_NF_IPTABLES_LEGACY and IP_NF_IPTABLES_LEGACY)
was able to be user selectable, and they are not anymore, causing this
behaviour change.
Thanks for your support,
--breno
prev parent reply other threads:[~2024-08-22 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 9:01 netfilter: Kconfig: IP6_NF_IPTABLES_LEGACY old =y behaviour question Breno Leitao
2024-08-22 11:23 ` Florian Westphal
2024-08-22 12:45 ` Breno Leitao
2024-08-22 13:20 ` Florian Westphal
2024-08-22 17:55 ` Breno Leitao [this message]
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=Zsd7hk8SMQoHKjwR@gmail.com \
--to=leitao@debian.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=rbc@meta.com \
/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.