<feed xmlns='http://www.w3.org/2005/Atom'>
<title>firewall4/tests/01_configuration/03_flow_offloading, branch master</title>
<subtitle>OpenWrt nftables firewall</subtitle>
<id>https://git.openwrt.org/project/firewall4/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/project/firewall4/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/firewall4/'/>
<updated>2026-10-25T10:19:25Z</updated>
<entry>
<title>fw4: list lower devices for software flow offloading</title>
<updated>2026-10-25T10:19:25Z</updated>
<author>
<name>Julius Bairaktaris</name>
</author>
<published>2026-10-18T13:43:11Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/firewall4/commit/?id=a3296754c154c9a0203a8ab72820da0b381aaddd'/>
<id>urn:sha1:a3296754c154c9a0203a8ab72820da0b381aaddd</id>
<content type='text'>
Since Linux commit 871df5007eda ("netfilter: flowtable: bail out if
forward path cannot be discovered"), a flow is offloaded only if the
ingress device at the bottom of its forward path is a flowtable device.
For a bridge that is the bridge port, such as a DSA user port or a
wireless interface, not the bridge itself. With software offloading,
fw4 lists only the zone devices, so flows through br-lan or a VLAN
under the WAN stay on the classic path.

Resolve the lower devices for software offloading as for hardware
offloading.

Assisted-by: Claude:claude-opus-5-5
Signed-off-by: Julius Bairaktaris &lt;julius@bairaktaris.de&gt;
Link: https://github.com/openwrt/firewall4/pull/108
Signed-off-by: Robert Marko &lt;robimarko@gmail.com&gt;
</content>
</entry>
</feed>
