A small update on the same day: the Updates page, as the three appliances were updated to 0.1.0-alpha.2 from it. An appliance installed from a test branch is offered the release, a reboot is asked for only when the driver changed, and the changes are listed with their links. Every step of an update is photographed in the guide, docs/guide/updating.md.
A small update: from this release an appliance sends its problem reports to the project's own
domain, reports.npuforge.org. The earlier address keeps answering, for the appliances that have not
updated yet.
Two days of work on both appliances, gathered. The XGS 136 forwards connections in its coprocessor through a takeout that works, revives a connection its fast path gives back and holds one that keeps coming back, and reads the coprocessor's own counts into pf and the interfaces. Block lists and TLS fingerprints cut connections already open, and unusual traffic is reported. Every page of the XGS menu renders again on appliances set up by the installer, and each cage reports the medium its module carries.
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.