<feed xmlns='http://www.w3.org/2005/Atom'>
<title>firewall4/tests/01_configuration/12_flow_offloading_hw_encaps, 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-11-08T16:27:23Z</updated>
<entry>
<title>fw4: list the software flowtable devices for hardware offloading too</title>
<updated>2026-11-08T16:27:23Z</updated>
<author>
<name>Julius Bairaktaris</name>
</author>
<published>2026-11-08T11:57:14Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/firewall4/commit/?id=3722eadc088c3ab81389596ca9796112b436583a'/>
<id>urn:sha1:3722eadc088c3ab81389596ca9796112b436583a</id>
<content type='text'>
With flow_offloading_hw, fw4 lists only the devices below the zone
devices. A hardware flowtable is a software flowtable too: the flows the
hardware does not take run through the same ingress hooks. A WireGuard
flow and a container flow then find no hook for their device and stay
on the classic path.

List the same devices for both. A device without hardware offload
support is accepted in a hardware flowtable (pending patch 701), so the
hardware check keeps its meaning.

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