Turris OS 6.3.0 is now in the Testing branch

Community office Testing branches
1

Dear Turris users,

We just released a new Turris OS version to the testing branch. The main change is replacing Netmetr with LibreSpeed. Netmetr will get shut down soon, so we decided to implement a UI for LibreSpeed instead and host our own LibreSpeed server. Unfortunately the librespeed-cli client we are using on the backend is written in go which doesn’t support the Turris 1.x CPU. Users who had Netmetr installed should also get Librespeed installed with this release and in a future version of Turris OS, Netmetr will get uninstalled.

:rocket: New Features

  • Syncthing and Transmission WebApps now use Turris Auth
  • Enabled multiple speed optimizations on Turris Omnia and Turris MOX
  • LibreSpeed reForis plugin for measuring network speed replacing Netmetr

:bug: Bug Fixes

  • Fixed webfinger support in Nextcloud
  • Fixed QoS for guest network
  • Notifications now correctly report reboot date at the end of the month
  • Hide incompatible packages from reForis on Turris 1.x

:pushpin: Updates

  • Linux kernel updated to 5.15.96 (MOX, Omnia) and 5.10.170 (Turris 1.x)
  • Nextcloud updated to 24.0.9
  • Sentinel Common Passwords updated for Q1 2023

We appreciate any feedback regarding this release.

10 Likes
2

6.2.4->6.3.0 RC1 update ok. There was a short cable connection/wifi downtime during the update and WAN had to reconnect. Restart needed.

Librespeed reforis plugin is not present, only the CLI tool. When I manually checked the librespeed package list in Reforis package management, updater only reported this: “Remove fix-guest-network-device-name” and did not install anything.

Syncthing Turris Auth started working out of the box (but only after reboot). Great job!

Turris Omnia 2017, 1 GB RAM, dead eMMC, system running from mSATA SSD, original wifi cards. Storage plugin enabled, LXC containers, tor relay, USB HDD shared over samba4 and minidlna, SQM, Hardwario gateway + MQTT IoT bridge, OpenVPN, PPtP VPN, morce.

3

What kind of optimizations should I imagine?

I found config: Optimize for speed not size (!611) · Merge requests · Turris / Turris OS / Turris Build · GitLab . Anything else?

1 Like
4

Can we get more information about the server? Where is it connected to the Internet, how is it connected to the Internet, what is the hardware used, and is it a physical server or a virtual server? Through what protocols is it accessible?

1 Like
5

You found the right PR, these are the speed optimizations meant by the changelog entry, nothing more, nothing less.

6

It’s a bit older physical server (Dell PowerEdge R430 with Xeon E5-2650 v4 @ 2.20GHz, 12 cores, 32 GB RAM) connected via a bonded 2x10GbE Intel X710. The server is located in our standard Prague datacenter (ČRA DC Tower).

LibreSpeed is running directly on this HW, no virtualization is done. It uses nginx instead of the LibreSpeed standard solution with Apache. It is accessible via HTTP and HTTPS.

5 Likes
7

Thanks for the details. Would librespeed automatically select a better server when the router would be geographically distant from Prague?

8

Is it IPv4 only or does it support the IPv6, too?

9

Yes, that is actually one of the key benefits of this solution.

4 Likes
10

It supports both IPv4 and IPv6 of course. The command-line measurement tool librespeed-cli supports --ipv4 / -4 and --ipv6 / -6 switches that control which protocol to use.

6 Likes
11

We just released rc2 where we fixed the lists and LibreSpeed reForis plugin should be installed now if you had Netmetr enabled.

3 Likes
12

Thanks! RC1->RC2 update without problems. Librespeed reforis plugin is now available and it works.

1 Like
13

this is now out, just got the update on Omnia and Mox

1 Like
14

Turris OS 6.3.0 was released to the stable branch: