From: Jakub Kicinski <kuba@kernel.org>
To: Florian Westphal <fw@strlen.de>
Cc: Simon Horman <horms@kernel.org>,
Hangbin Liu <liuhangbin@gmail.com>,
Jaehee Park <jhpark1013@gmail.com>,
Petr Machata <petrm@nvidia.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Ido Schimmel <idosch@nvidia.com>,
Davide Caratti <dcaratti@redhat.com>,
Matthieu Baerts <matttbe@kernel.org>,
netdev@vger.kernel.org
Subject: Re: [TEST] Flake report
Date: Fri, 10 May 2024 07:47:16 -0700 [thread overview]
Message-ID: <20240510074716.1bbb8de8@kernel.org> (raw)
In-Reply-To: <20240510083551.GB16079@breakpoint.cc>
On Fri, 10 May 2024 10:35:51 +0200 Florian Westphal wrote:
> Jakub Kicinski <kuba@kernel.org> wrote:
> > To: Florian Westphal <fw@strlen.de>
> >
> > These are skipped because of some compatibility issues:
> >
> > nft-flowtable-sh, bridge-brouter-sh, nft-audit-sh
> >
> > Please LMK if I need to update the CLI tooling.
> > Or is this missing kernel config?
>
> No, its related to the userspace tooling.
> This should start to work once amazon linux updates nftables.
>
> bridge-brouter-sh would work with the old ebtables-legacy instead
> of ebtables-nft, or a more recent version of ebtables-nft.
>
> ATM it uses a version of ebtables-nft that lacks "broute" table emulation.
Amazon Linux is more of a base OS for loading containers it seems.
I build pretty much all the tools from source.
So I just built nft too.. Whether it will actually work we'll find
out in about 15 min :)
next prev parent reply other threads:[~2024-05-10 14:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 23:09 [TEST] Flake report Jakub Kicinski
2024-05-10 3:24 ` Hangbin Liu
2024-05-10 8:35 ` Florian Westphal
2024-05-10 14:47 ` Jakub Kicinski [this message]
2024-05-10 16:03 ` Jakub Kicinski
2024-05-10 16:41 ` Florian Westphal
2024-05-10 18:02 ` Jakub Kicinski
2024-05-11 0:14 ` Jakub Kicinski
2024-05-11 6:50 ` Florian Westphal
2024-05-10 14:28 ` Matthieu Baerts
2024-05-30 17:35 ` Matthieu Baerts
2024-05-30 17:41 ` Jakub Kicinski
2024-05-31 7:52 ` Matthieu Baerts
2024-05-10 14:45 ` Nikolay Aleksandrov
2024-05-11 13:27 ` Simon Horman
2024-05-14 13:52 ` Aaron Conole
2024-05-13 11:58 ` Davide Caratti
2024-05-13 16:52 ` Petr Machata
2024-05-14 13:43 ` Jakub Kicinski
2024-05-21 16:29 ` Petr Machata
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=20240510074716.1bbb8de8@kernel.org \
--to=kuba@kernel.org \
--cc=dcaratti@redhat.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jhpark1013@gmail.com \
--cc=liuhangbin@gmail.com \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
/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).