From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Ahern <dsahern@kernel.org>,
coreteam@netfilter.org,
"netdev-driver-reviewers@vger.kernel.org"
<netdev-driver-reviewers@vger.kernel.org>,
Hangbin Liu <liuhangbin@gmail.com>,
netfilter-devel@vger.kernel.org
Subject: Re: [netfilter-core] [ANN] net-next is OPEN
Date: Wed, 24 Jan 2024 21:02:16 +0100 [thread overview]
Message-ID: <ZbFsyEfMRt8S+ef1@calendula> (raw)
In-Reply-To: <20240124114057.1ca95198@kernel.org>
On Wed, Jan 24, 2024 at 11:40:57AM -0800, Jakub Kicinski wrote:
> On Wed, 24 Jan 2024 20:16:39 +0100 Pablo Neira Ayuso wrote:
> > > Ah, BTW, a major source of failures seems to be that iptables is
> > > mapping to nftables on the executor. And either nftables doesn't
> > > support the functionality the tests expect or we're missing configs :(
> > > E.g. the TTL module.
> >
> > I could only find in the listing above this:
>
> Thanks for taking a look!
>
> > https://netdev-2.bots.linux.dev/vmksft-net-mp/results/435141/37-ip-defrag-sh/stdout
> >
> > which shows:
> >
> > ip6tables v1.8.8 (nf_tables): Couldn't load match `conntrack':No such file or directory
> >
> > which seems like setup is broken, ie. it could not find libxt_conntrack.so
>
> Hm, odd, it's there:
>
> $ ls /lib64/xtables/libxt_conntrack.so
> /lib64/xtables/libxt_conntrack.so
>
> but I set a custom LD_LIBRARY_PATH, let me make sure that /lib64
> is in it (normal loaded always scans system paths)!
Could you also check your ./configure output for iptables? It shows
the directory where the .so file are search and found:
...
Xtables extension directory: /usr/lib/xtables
> > What is the issue?
>
> A lot of the tests print warning messages like the ones below.
> Some of them pass some of them fail. Tweaking the kernel config
> to make sure the right CONFIG_IP_NF_TARGET_* and CONFIG_IP_NF_MATCH_*
> are included seem to have made no difference, which I concluded was
> because iptables CLI uses nf_tables here by default..
Please, check if the symlink refers to -legacy or -nft via:
$ ls -la /usr/sbin/iptables
> [435321]$ grep -nrI "Warning: Extension" .
> ./6-fib-tests-sh/stdout:305:# Warning: Extension MARK revision 0 not supported, missing kernel module?
This could come from either legacy or nftables:
libxtables/xtables.c: "Warning: Extension %s revision 0 not supported, missing kernel module?\n",
iptables/nft.c: "Warning: Extension %s revision 0 not supported, missing kernel module?\n",
both have the same error.
if that is the nftables backend, it might be also that .config is
missing CONFIG_NF_TABLES and CONFIG_NFT_COMPAT there, among other
options.
next prev parent reply other threads:[~2024-01-24 20:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240122091612.3f1a3e3d@kernel.org>
[not found] ` <Za98C_rCH8iO_yaK@Laptop-X1>
[not found] ` <20240123072010.7be8fb83@kernel.org>
[not found] ` <d0e28c67-51ad-4da1-a6df-7ebdbd45cd2b@kernel.org>
[not found] ` <65b133e83f53e_225ba129414@willemb.c.googlers.com.notmuch>
[not found] ` <20240124082255.7c8f7c55@kernel.org>
2024-01-24 17:01 ` [ANN] net-next is OPEN Jakub Kicinski
2024-01-24 18:35 ` Matthieu Baerts
2024-01-24 19:00 ` Jakub Kicinski
2024-01-24 19:18 ` [netfilter-core] " Pablo Neira Ayuso
2024-02-06 18:31 ` Matthieu Baerts
2024-02-07 9:49 ` Pablo Neira Ayuso
2024-02-07 11:33 ` Matthieu Baerts
2024-02-16 15:38 ` Pablo Neira Ayuso
2024-02-16 15:51 ` Matthieu Baerts
2024-01-24 19:16 ` Pablo Neira Ayuso
2024-01-24 19:40 ` Jakub Kicinski
2024-01-24 20:02 ` Pablo Neira Ayuso [this message]
2024-01-24 20:13 ` Jakub Kicinski
2024-01-25 5:07 ` Jakub Kicinski
2024-01-25 8:52 ` Florian Westphal
2024-01-25 17:30 ` Jakub Kicinski
2024-01-25 9:29 ` Pablo Neira Ayuso
2024-01-25 17:34 ` Jakub Kicinski
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=ZbFsyEfMRt8S+ef1@calendula \
--to=pablo@netfilter.org \
--cc=coreteam@netfilter.org \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev-driver-reviewers@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=willemdebruijn.kernel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).