LORIX OS 1.8 “Niesen” is available for all our gateways. It brings the ChirpStack v4 stack and gateway mesh to your infrastructure, strengthens security by default, and refreshes the platform your gateway runs on.<\/p>\n\n\n\n
LORIX OS now includes full support for the ChirpStack v4 stack, bringing the latest ChirpStack features and tooling to your gateways. 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 \u2014 ideal for extending coverage to hard-to-reach installations.<\/p>\n\n\n\n
The new v4 stack is introduced alongside the legacy v3 stack, so you can plan and execute your migration at your own pace. v3 will be removed in a future release, but this is not planned before 2027.<\/p>\n\n\n\n
New LORIX OS installations now require a password change on first login \u2014 freshly deployed gateways can no longer keep an unchanged default password. 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). The firewall stack has also been upgraded from iptables to nftables, bringing better performance, more advanced capabilities and a cleaner, safer configuration model.<\/p>\n\n\n\n
The move to Yocto 5 (Scarthgap) brings a broad refresh of core Linux components, including the Linux kernel 6.12 \u2014 improving security, stability and overall system performance. Your gateway stays aligned with current upstream technologies.<\/p>\n\n\n\n
The Wifx Connect registration workflow has been improved with a new two-step pairing process: first create the gateway entry in Wifx Connect, then copy the generated token and paste it into the gateway Manager \u2014 through the GUI or the CLI \u2014 to complete pairing. This gives you better control over commissioning and makes it possible to pre-register gateways before deployment. The same workflow is available through the Manager CLI and API, making it easier to integrate registration into your own automation tools.<\/p>\n\n\n\n
LORIX OS 1.8 adds an automatic rollback feature that helps recover from updates that might make a gateway unreachable: if the update is not confirmed within two hours, it is automatically reverted. Gateways also save and restore their logs across reboots, so you keep visibility on what happened, and LORIX OS 1.8 ships with LORIX Manager v1.0.<\/p>\n\n\n\n