Skip to content

Extended sequence numbers on the XGS 136's engine, both ways. Measured, 2026-10-20

Yes, both ways. The XGS 136's crypto engine keeps an association's 64-bit sequence count when SA_ADD asks it to - bit 18 of the control word, ext_seq - and it did, for every frame of three runs at the gigabit link's rate: 4,305,432 frames decrypted on one association, none failed, and 5,796,289 frames encrypted that the peer's kernel checked with no authentication failure and no replay.

The whole page, with how it was taken and what it does not show: Extended sequence numbers on the XGS 136's engine, both ways. Measured, 2026-10-20.

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.