What the coprocessor counts of a connection, measured, 2026-10-19¶
Once a connection is in hardware the host stops seeing it: its frames go from port to port inside
the coprocessor, and pf's state, the interface counters and every graph built on them stop growing -
which is why every throughput on these pages is read at the far end, not on the appliance. The
coprocessor itself counts every connection it forwards, and the XGS 3300's sends those counts to the
host unasked, about once a second, as control messages on tag 254 - which the driver had dropped
unread since the receive path was written. Since this change it reads them
(octep_dp_cmsg_rx in contrib/octep/octep_dp.c): each connection in the table keeps the packets and
bytes the coprocessor counted for each direction, dev.octep.0.dp.flow_table prints them, and the
Offloaded Flows page shows them as Counted in hardware.
The whole page, with how it was taken and what it does not show: What the coprocessor counts of a connection, measured, 2026-10-19.
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.