Skip to content

pfsync to a peer: a UDP connection in hardware lost its state about a minute in, and keeps it now, 2026-11-15

With pfsync between two appliances, the state of a UDP connection the flow maker had put in hardware was replaced 60 to 70 seconds in (#1160). pfsync sends a state's update when pf passes one of its packets, and a connection in hardware passes none: the driver's keepalive refreshed the state's expiry by writing it, and pfsync never heard of it, so the peer's copy expired on udp.multiple (60 s) and the delete its expiry sent back removed the live state. Since the change the keepalive's refresh is handed to pfsync's own update, on the same state under the same lock (octep_pf_sync). That is the XGS 3300's driver: the XGS 136's keepalive did not refresh a state in hardware at all (below).

The whole page, with how it was taken and what it does not show: pfsync to a peer: a UDP connection in hardware lost its state about a minute in, and keeps it 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.