From: Florian Westphal <fw@strlen.de>
To: ratheesh kannoth <ratheesh.ksz@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Netfilter mailing list <netfilter@vger.kernel.org>
Subject: Re: nft for bridge.
Date: Sun, 5 Oct 2025 13:45:39 +0200 [thread overview]
Message-ID: <aOJaY6oQnYPTcVAn@strlen.de> (raw)
In-Reply-To: <CAGZFCEHxw0VkH0JJYjxNHevJ69BMZQ9zbhT=YbYS6ti2j8DAwg@mail.gmail.com>
ratheesh kannoth <ratheesh.ksz@gmail.com> wrote:
> On Mon, Aug 18, 2025 at 7:50 PM Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > No flowtable support for the bridge family yet, sorry.
> Thanks. For routed flow, Openvswitch case, it pushes Original and
> reply direction with the same cookie. But nft case, it pushes Original
> direction tuple twice. Is this expected ? or is this issue fixed with
> the latest kernel or nft ?
You will need to figure that out yourself. Most of us a volunteers.
> MY nft version : nftables v1.1.5 (Commodore Bullmoose #6)
> My kernel : kernel 6.6
>
> ADD cookie=18446462603462596360 (00:00:00:00:00:00,
> 192.168.11.200:30443) to (00:00:00:00:00:00, 192.168.9.100:35091) IPv4
> TCP
> ADD cookie=18446462603462596360 (00:00:00:00:00:00,
> 192.168.11.200:30443) to (00:00:00:00:00:00, 192.168.9.100:35091) IPv4
> TCP
I don't even know where these messages come from.
next prev parent reply other threads:[~2025-10-05 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 12:05 nft for bridge ratheesh kannoth
2025-08-18 14:20 ` Pablo Neira Ayuso
2025-10-05 7:03 ` ratheesh kannoth
2025-10-05 11:45 ` Florian Westphal [this message]
2025-10-05 12:26 ` ratheesh kannoth
2025-10-06 10:03 ` Pablo Neira Ayuso
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=aOJaY6oQnYPTcVAn@strlen.de \
--to=fw@strlen.de \
--cc=netfilter@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=ratheesh.ksz@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