Skip to content

The XGS 136 keeps the state of a UDP connection in hardware now, 2026-11-15

The XGS 136's keepalive asked whether a connection's state still existed and gave pf the coprocessor's counts, and refreshed nothing: npuep_pf_touch, which restamps a state as a packet would, had no caller since the driver's flow table began. So the state of a UDP connection in hardware lapsed at its own timeout - udp.multiple, 60 seconds - and the connection left hardware with it. Since the change the keepalive restamps a connection's states when the coprocessor has counted traffic for it since the last restamp, at most every five seconds a connection (counted in flow.ka_touched), and each restamp is told to pfsync (npuep_pf_sync), as the XGS 3300's driver does (pfsync to a peer).

The whole page, with how it was taken and what it does not show: The XGS 136 keeps the state of a UDP connection in hardware now, 2026-11-15.

Discussion

The discussion of this page is held in the project's GitHub Discussions. Showing it here loads giscus from giscus.app and GitHub, and writing in it needs a GitHub account - what that means.