[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZbIqBU9I009KVqZT@calendula>
Date: Thu, 25 Jan 2024 10:29:41 +0100
From: Pablo Neira Ayuso <pablo@...filter.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Willem de Bruijn <willemdebruijn.kernel@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
David Ahern <dsahern@...nel.org>, coreteam@...filter.org,
"netdev-driver-reviewers@...r.kernel.org" <netdev-driver-reviewers@...r.kernel.org>,
Hangbin Liu <liuhangbin@...il.com>, netfilter-devel@...r.kernel.org
Subject: Re: [netfilter-core] [ANN] net-next is OPEN
On Wed, Jan 24, 2024 at 09:07:24PM -0800, Jakub Kicinski wrote:
> On Wed, 24 Jan 2024 12:13:43 -0800 Jakub Kicinski wrote:
> > > 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.
> >
> > FWIW full config:
> >
> > https://netdev-2.bots.linux.dev/vmksft-net-mp/results/435321/config
> >
> > CONFIG_NFT_COMPAT was indeed missing! Let's see how it fares with it enabled.
>
> NFT_COMPAT fixed a lot! One remaining warning comes from using
> -m length. Which NFT config do we need for that one?
May I have a look at the logs? How does the error look like?
Powered by blists - more mailing lists