A CARP failover with a TCP connection in hardware: it dies without the numbers for pfsync and goes on with them, 2026-11-15
A planned failover between the second XGS 3300 and the XGS 136, with a TCP stream through them that the master carries in hardware and that began with the host, so that the backup's pfsync copy of it is strict. Before the numbers written for pfsync, the new master refused the connection and it died; with them it went on. A carp hook that empties the old master's hardware when it is master of nothing any more was measured too, and is a setting, off by default.
The whole page, with how it was taken and what it does not show: A CARP failover with a TCP connection in hardware: it dies without the numbers for pfsync and goes on with them, 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.