Release date:  

Announcement

We are glad to release LORIX OS v1.3. This release focuses on log improvements, Wireguard support and new connectivity basements.

Regressions

The following regressions have been discovered after the release of this version.

US region default frequency plan changed from FSB2 to FSB1

  • Introduced: LORIX OS v1.2.0
  • Details: The default FSB for US is now FSB1 instead of FSB2 (this is not a true regression, only a undocumented and undesired change). Gateways with the region/frequency plan already defined are not affected, only new installs.
  • Workaround: when you use US region, be sure to double check the used frequency plan and select FSB2 if needed.
  • Fix: default has been reverted to FSB2 in LORIX OS v1.2.3 and LORIX OS v1.3.3.

Kernel memory leak done by syslog-ng

  • Introduced: LORIX OS v1.3.0
  • Details: Upon logging, syslog-ng does a small memory leak in the kernel.
  • Consequences: after a few weeks to a few years (depending on logging frequency), the gateway RAM will be full and random services will get killed
  • Severity: very high
  • Workaround: restart the gateway upon a regular basis (e.g. once a week)
  • Fix: syslog-ng has been updated to v3.33.2 in LORIX OS 1.3.2

Do not use this version for production. Upgrade to LORIX OS >= 1.3.2.


Essential improvements

The full changelog is available below.

Log improvements

Working in the networking field is not easy. There are thousands of things that can go wrong, either when you setup a device of during operation. Sometimes, a device that works fine for many year suddenly fails just because of a configuration change made by some network administrator.

We want to help you setup your LORIX One easily even in very specific use cases, where the networking condition are not good at all. For this, we improved the logs of the gateway. This is directly visible through the Manager GUI, on the logs page, where the different services now log in different section, so you can focus on the essential part. You can also use the provided filter to easily find an event at a specific date or regarding a known service.

To do so, we changes the underling logging engine, migrating from busybox-syslog to syslog-ng. This powerful logging engine allows you to add log exports and filters very easily so you can centralize your logs or send notifications on critical events. Please check the related documentation so see the possibilities you have.

Wireguard support

Wireguard is a new and innovative VPN protocol that is blazing fast, very secured and easy to setup. Many of you asked for support of Wireguard in LORIX OS, and that's now available! You can setup it easily though the Manager GUI by importing your Wireguard profile, though the wg-quick files you are used to.

New connectivity basements

To improve the user experience of the Manager GUI, it is now connected totally through websockets. This change is totally transparent and you don't need to adapt anything in your infrastructure. The REST API is still available and will be simplified to the essential features to make it more convenient. We now use nats as the underlying transfer protocol as it will allow us to provide new possibilities of connectivity that you'll surely appreciate, stay tuned!

Changelog

LORIX OS

v1.3.0

Added

  • [LOR-445] Add LoRa concentrator reset script to the BasicStation configuration
  • [LOR-426] Update the GPIO control system (add libgpio tools)
  • [LOR-444] Enable standard cron directories (hourly, daily, weekly, monthly)
  • [LOR-173] Restrict the size of /var/log

Changed

  • [LOR-389] Rename OpenRC service "reset-lgw" to "lora-concentrator"
  • [LOR-439] Reset lora-concentrator with libgpio tools
  • [LOR-422] Upgrade NetworkManager to 1.28.0
  • [LOR-449] Upgrade pmonitor to v0.8
  • [LOR-450] Update ChirpStack Gateway Bridge to 3.10.0
  • [LOR-447] Upgrade manager to v0.11

Manager

v0.11.2

Changed

  • [MAN-352] Improve updater memory usage

Fixed

  • [MAN-353] Memory leak on update cancellation
  • [MAN-354] When system temperature fails to fetch, no system info are available

v0.11.1

Fixed

  • [MAN-350] Cannot read server configuration when only CUPS is used

v0.11.0

Added

  • [MAN-340] Show media usage stats
  • [MAN-333] Add wireguard support

Changed

  • [MAN-339] Use nats.ws as main connection between GUI and backend
  • [MAN-334] Adapt log output for new syslog-ng format and files path
  • [MAN-185] GUI compression

Fixed

  • [MAN-336] Cannot get/set channel plan if not defined
  • [MAN-327] Cannot change timezone if symlink is broken
  • [MAN-349] BasicStation : packet parsing error when modulation is FSK

Manager GUI

v0.11.1

Fixed

  • Safe update process fixed

v0.11.0

Added

  • [MAN-332] Add RSSI and SNR unit in GUI
  • [MAN-333] Add wireguard support
  • [MAN-335] Allow user to use onboard certificates for the Basic Station server auth
  • [MAN-340] Show media usage stats
  • [MAN-341] Add hostname in title and footer

Changed

  • [MAN-326] Remove LTS channel from GUI
  • [MAN-339] Use nats.ws as main connection between GUI and backend
  • [MAN-334] Adapt log output for new syslog-ng format and files path
  • [MAN-185] GUI compression
  • [MAN-344] Replace dashboard disk usage chart with a circle chart
  • Upgrade dependencies
  • [MAN-345] Show all certificates in a bundle
  • [MAN-346] Improve notifications and notification center

Fixed

  • [MAN-342] Widget skeleton loaders not shown properly
  • [MAN-343] Chart theme not turning to dark mode

pmonitor

v0.8.0

Changed

  • [PMON-111] Write config files synchronously