From: Pablo Neira Ayuso <pablo@netfilter.org>
To: ratheesh kannoth <ratheesh.ksz@gmail.com>
Cc: Netfilter mailing list <netfilter@vger.kernel.org>
Subject: Re: nft for bridge.
Date: Mon, 18 Aug 2025 16:20:32 +0200 [thread overview]
Message-ID: <aKM2sOMlivuUJHOJ@calendula> (raw)
In-Reply-To: <CAGZFCEGKWfnuXdXvSBQEJFfHeKsDKLx0E+SLorBs6HWRUs1kFg@mail.gmail.com>
On Mon, Aug 18, 2025 at 05:35:49PM +0530, ratheesh kannoth wrote:
> hi,
>
> inet offload is working fine for me.
> ++++++++++++++++++++++++
> /etc/nftables/inet.nft
>
> table inet x {
>
> flowtable f {
> hook ingress priority 0
> devices = { eth0, sdp1-0 }
> flags offload;
> }
>
> chain forward {
> type filter hook forward priority 0; policy accept;
> ct state { established, related } flow add @f
> }
> }
> ++++++++++++++++++
> But bridge nft fails. Could you help with correct configuration? i
> have already enabled below config
> CONFIG_NF_TABLES_BRIDGE=y
> CONFIG_NF_CONNTRACK_BRIDGE=y
>
>
> /etc/nftables/ibridge-raw.nft
> --------------
> table bridge x {
>
> flowtable f {
> hook ingress priority 0
> devices = { br0 }
> flags offload;
> }
>
> chain forward {
> type filter hook forward priority 0; policy accept;
> ct state { established, related } flow add @f
> }
> }
> ~# nft -f /etc/nftables/ipv4-raw.nft
> /etc/nftables/ipv4-raw.nft:7:16-16: Error: Could not process rule: No
> such file or directory
> flowtable f {
> ^
> /etc/nftables/ipv4-raw.nft:15:43-53: Error: Could not process rule: No
> such file or directory
> ct state { established, related } flow add @f
> ^^^^^^^^^^^
No flowtable support for the bridge family yet, sorry.
next prev parent reply other threads:[~2025-08-18 14:20 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 [this message]
2025-10-05 7:03 ` ratheesh kannoth
2025-10-05 11:45 ` Florian Westphal
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=aKM2sOMlivuUJHOJ@calendula \
--to=pablo@netfilter.org \
--cc=netfilter@vger.kernel.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