Release date: 27 Mar 2026 

LORIX OS 1.8 "Niesen" is now available, bringing a major update to the platform with new LoRaWAN features, updated core components, and stronger security defaults.

Highlights

ChirpStack v4 and gateway mesh

LORIX OS now includes full support for the ChirpStack v4 stack, bringing the latest ChirpStack features and tooling to your gateways.

As part of this transition, the ChirpStack Gateway Bridge used in v3 is replaced in v4 by the ChirpStack MQTT Forwarder, which adds more advanced packet filtering capabilities. We have also natively integrated ChirpStack Gateway Mesh, allowing the Wifx L1 to operate as a relay gateway without requiring a network connection of its own.

The new v4 stack is introduced alongside the legacy v3 stack, so you can plan and execute your migration at your own pace. The v3 stack will be removed in a future release, but this is not planned before 2027.

Up-to-Date System Components

With the move to Yocto 5 (Scarthgap), LORIX OS benefits from a broad refresh of core Linux components. This update improves security, stability, and overall system performance while keeping the platform aligned with current upstream technologies.

Stronger Security by Default

New LORIX OS installations now require a password change on first login. This is part of a broader set of security improvements designed to strengthen the platform and support compliance with the EU Radio Equipment Directive 2014/53/EU (RED, EN 18031).

Behind the scenes, we have also improved our internal processes for tracking and handling Common Vulnerabilities and Exposures affecting LORIX OS.

The firewall stack has been upgraded from iptables to nftables, bringing better performance, more advanced capabilities, and a cleaner, safer configuration model.

Wifx Connect Two-Step Registration

The Wifx Connect registration workflow has been improved with a new two-step pairing process.

You can now first create the gateway entry in Wifx Connect, then copy the generated token and paste it into the gateway Manager, either through the GUI or the CLI, to complete pairing. This gives you better control over commissioning and makes it possible to pre-register gateways before deployment.

The same workflow is also available through the Manager CLI and API, making it easier to integrate registration into your own automation tools.

Notes

Update automatic rollback

A new automatic rollback feature has been introduced to help recover from updates that might make your gateway unreachable. 

You must persist the update within two hours, or it will be automatically reverted. 

For future updates, this behavior will be available as a configurable option during the update process.

Changelog