From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: stable@vger.kernel.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
netfilter-devel@vger.kernel.org
Subject: Re: network flow offloading broken in 6.18.45+
Date: Mon, 14 Sep 2026 00:13:47 +0200 [thread overview]
Message-ID: <aqcgG0y-nYz4DWz3@chamomile> (raw)
In-Reply-To: <aqcfvRE3aHoAx8s7@chamomile>
On Mon, Sep 14, 2026 at 12:12:16AM +0200, Pablo Neira Ayuso wrote:
> Hi Hauke,
>
> On Wed, Sep 09, 2026 at 06:29:50PM +0200, Hauke Mehrtens wrote:
> > Hi,
> >
> > flow offloading is currently broken in Linux 6.18.45.
> >
> > Since the backport of commit b5964aac51e0 ("netfilter: flowtable:
> > consolidate xmit path") to Linux 6.18.45. This is happening in a router with
> > traffic from wifi to the Ethernet device when mac80211 returns -EOPNOTSUPP.
> >
> > Upstream fixed it in 871df5007eda ("netfilter: flowtable: bail out if
> > forward path cannot be discovered") by not offloading the flow at all.
> > backporting this change looks more complicated.
> >
> > This cam up in a discussion in an OpenWrt PR:
> > https://github.com/openwrt/openwrt/pull/24800
> >
> > An LLM suggested this change: https://github.com/openwrt/openwrt/pull/24800/changes/394d741e6e76ecd172dbbf1d9ba171e378211734
>
> Patch went away.
>
> > It seams to work, but I do not understand this part of the code god enough
> > to judge if this is correct.
>
> Could you attach the patch to this email for review?
I've found it :)
https://github.com/openwrt/openwrt/commit/d2b53b8043e17087b877bfc2335cbba87dffb4e0
prev parent reply other threads:[~2026-09-13 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 16:29 network flow offloading broken in 6.18.45+ Hauke Mehrtens
2026-09-13 22:12 ` Pablo Neira Ayuso
2026-09-13 22:13 ` Pablo Neira Ayuso [this message]
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=aqcgG0y-nYz4DWz3@chamomile \
--to=pablo@netfilter.org \
--cc=hauke@hauke-m.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.