<feed xmlns='http://www.w3.org/2005/Atom'>
<title>firewall4/tests/01_configuration/11_flow_offloading_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 layer 3 devices of zones in the software flowtable</title>
<updated>2026-11-08T16:27:23Z</updated>
<author>
<name>Julius Bairaktaris</name>
</author>
<published>2026-11-08T11:55:54Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/firewall4/commit/?id=b25508586879c84607ca5d47443c291dc8e9442f'/>
<id>urn:sha1:b25508586879c84607ca5d47443c291dc8e9442f</id>
<content type='text'>
fw4 builds the software flowtable from the device each zone network is
set up on. A WireGuard interface has no such device, so its device is
never listed and none of its flows is offloaded. A PPPoE interface
contributes the Ethernet or VLAN device below it, while its pppoe
device is listed only when another interface, such as wan6, names it.

List the layer 3 device of each zone network as well. In QEMU (x86-64
r37896, 6.18.55), a TCP transfer through WireGuard took the forward
chain with 11024 to 45276 packets in 6 s before and with 6 to 7 after,
IPv4 and IPv6, both directions, 3 runs each.

11_flow_offloading_encaps covers the device list for each encapsulation
a zone network can use, from netifd's interface and device status in
that setup: plain, 802.1Q, 802.1ad, PPPoE and PPPoE over VLAN, macvlan,
a VLAN-filtering bridge, a VXLAN and a bond as bridge ports, GRE, IPIP,
SIT, ip6tnl and WireGuard.

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>
