IPv6 through the coprocessor, and the XGS 136's transmit queues, 2026-10-18
Two measurements of the same night's driver work, each taken in a window of its own and photographed when it finished:
Two measurements of the same night's driver work, each taken in a window of its own and photographed when it finished:
The first measurement of a connection crossing the XGS 136 in its coprocessor's fast path rather than through the host: the same traffic, the same ports, once with the host forwarding it and once with the flow maker on, both ways. Each run was taken in a window of its own and photographed when it finished.
A small update on the same day as the first release: the problem reporter tells crashes apart correctly, and the chipset's own record of why the host last reset is kept at every boot. The Updates page shows a progress bar while it installs. The repository gains its community files.
The first release: everything merged until this day, as one version an appliance can be updated to
and back from. Nothing here is advised for a firewall carrying real traffic - read the notice at the
top of the README first read the README's "Getting it onto an appliance" first (the work-in-progress notice
was lifted on 2026-10-18). What each appliance has and lacks, side by side:
docs/families/parity.md.
The first measurements with a hardware peer at both ends of every tunnel: until this night the far end of a measured tunnel was a firewall doing ESP in software, so a figure could be that firewall's rather than the appliance's. Every window a number came from was photographed when the run finished, and the pictures are below each table.
Measured 2026-10-17 on the bench: one TCP stream for ten seconds in each
direction, in clear text and through the IPsec tunnels (AES-GCM-256, in the engines at both ends),
at eight MTUs from the smallest to the largest. Every run's window was photographed when it
finished; the 52 pictures are in docs/images/measurements/mtu-2026-10-17/ and below each table.