リリース
すべてのリリースを新しい順に。機器は XGS: Updates ページからリリースを取得します - アップデート、英語。新しい機器はイメージビルダーのイメージで最新版を受け取ります。
0.1.0-alpha.5.3
2026-10-21
0.1.0-alpha.5.2
2026-10-21
0.1.0-alpha.5.1
2026-10-21
0.1.0-alpha.5
2026-10-21
A gathered release. On both families, the appliance's own traffic through a tunnel that strongSwan has moved onto a narrower path no longer loops in the kernel. On the XGS 3300, a receive ring whose interrupt was raised and never handled is found within two ticks instead of up to 50 ms, every ring's interrupt has a CPU of its own, and an arriving ESN association is decrypted by the engine. Every model of both families now installs, its front ports named from one table by the assembly number on its board; every model but the XGS 136 and the XGS 3300 is added untested - its status page says so, and its first boot checks its ports against what its coprocessor reports. The drivers changed: the Updates page asks for a reboot.
0.1.0-alpha.4.3
2026-10-20
A fix for the XGS 136 that 0.1.0-alpha.4.2 made urgent: reading the switch's port counters every five minutes - installed everywhere by that release - made the 136's coprocessor report linked ports down, sometimes for as long as no cable moved (#639). The 136 no longer reads them; after the update, a reboot of the 136 clears any port it still believes down. And on the XGS 3300, XGS: Ports counts F1, F2 and the expansion module's ports from the coprocessor's own MACs. No driver changed.
0.1.0-alpha.4.2
2026-10-20
Checking for updates no longer runs out of GitHub's hourly allowance: XGS: Updates and its Plugins tab ask npuforge.org's copy of GitHub's answers first, and what is installed is still confirmed with GitHub itself. The switch's port counters on XGS: Ports work - their script was never installed - a first install fetches the kernel's sources it needs to build the driver, and an appliance is counted on npuforge.org as soon as it is installed or updated. On the XGS 136 the receive runs on the coprocessor's doorbells by default, with a setting to turn them off; the driver changed, so it takes effect at the next boot.
0.1.0-alpha.4.1
2026-10-20
Three things on the pages of 0.1.0-alpha.4, found on the first appliance it was installed on: the dates at the top of XGS: Updates read "Invalid Date" (since 0.1.0-alpha.3), its Channel menu cut its text off, and XGS: Ports' switch counters showed empty headings until their first reading. And XGS: About has a Releases tab: every release's changes, the one installed here marked. Nothing in the drivers changed; no reboot.
0.1.0-alpha.4
2026-10-20
A reload of the XGS 136's driver could stop the host when the coprocessor held the tunnel's encrypting association at that moment (#603); the association now gets the kernel's own ESP transform back first. XGS: Ports shows the switch's own counters for each port behind it - the errors and drops the host never sees. The XGS 136 can take its receive from the coprocessor's doorbells (hw.npuep.giu.rx_msix, off by default until a soak with it on), and a reload of its driver applies what a boot applies. The XGS 136's driver changed, so it asks for a reboot; the switch tool on the coprocessor is replaced at the next boot.
0.1.0-alpha.3
2026-10-20
Power over Ethernet on the XGS 136, read and switched from XGS: Ports. The XGS 136's tunnel connections in its own flow table, their encrypting direction in hardware, with what they encrypt handed to the kernel's association, and a connection an IPsec policy covers kept out of hardware. What the Traffic Shaper and the Captive Portal name is kept with the host, where ipfw sees it. XGS: About, a Plugins tab on XGS: Updates, the coprocessor's own uptime, load and memory on the Overview, and the IPsec page counting the XGS 136's associations right. Both drivers changed, so both appliances ask for a reboot.
0.1.0-alpha.2.3
2026-10-20
Two IPsec features on the XGS 136's own engine, both measured at the gigabit link's rate in both directions: extended sequence numbers, and IPv6 - a tunnel between IPv6 addresses and IPv6 packets inside one. The XGS 3300's coprocessor console is now driven only once its Linux is up, and a slow handshake is given six minutes. From this release an appliance also counts itself once a day for the site's home page: a random identifier it made for itself, its model and this release, and nothing else - XGS: Problem Reports turns it off. The rest is the project's site, npuforge.org. The XGS 136's driver changed, so it asks for a reboot.
0.1.0-alpha.2.2
2026-10-19
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.
0.1.0-alpha.2.1
2026-10-19
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.
0.1.0-alpha.2
2026-10-19
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.
0.1.0-alpha.1.1
2026-10-18
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.
0.1.0-alpha.1
2026-10-18
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.