pfsync to a peer: a TCP connection's numbers stood still at the make, and a peer taking over refused it; written for the peer now, 2026-11-15
pf sees none of a connection's frames once the flow maker has put it in hardware, so the numbers pf keeps for it
- each end's
[seqlo + window]- stop at the make, and the state is marked sloppy there. pfsync copies what pf has: a peer held a window hundreds of megabytes behind the live connection, and its copy was strict whenever it had been sent before the make. Measured below, a peer with a strict copy refused a segment with the live numbers as a state mismatch - every segment of the connection, on a takeover. Since the change, while pfsync0 is up, the fast path's numbers are written into the connection's pf states at each keepalive pass and handed to pfsync, and each TCP connection's states are given a gigabyte past their right edges at the make; the states stay sloppy on the appliance that carries the connection.
The whole page, with how it was taken and what it does not show: pfsync to a peer: a TCP connection's numbers stood still at the make, and a peer taking over refused it; written for the peer now, 2026-11-15.
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.