Dragonfly turned on: it inspects, its exports reach nothing seen, and it loses a tunnel's traffic, 2026-10-25
Discovery 22 of the discoveries.
The XGS 3300's coprocessor starts Dragonfly - a DPI and threat-detection engine built on nDPI - at
every boot, and nothing turns it on for any interface. Two questions were left: how it is turned on,
and where its alerts leave the coprocessor. Measured on both XGS 3300s - the second on SFOS 22's
coprocessor software, the first on SFOS 23's - and read on the XGS 136 (SFOS 21's), with octep.ko
6cde3fde (main of the morning plus the receive instrument below) and npuep.ko 590205fb
(images/deploy/lab-dragonfly.sh, lab-dragonfly-report.sh).
The whole page, with how it was taken and what it does not show: Dragonfly turned on: it inspects, its exports reach nothing seen, and it loses a tunnel's traffic, 2026-10-25.
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.