Turris OS 4.0.5 is released into HBT branch

Dear Turris users,

This time we are proud to release Turris OS 4.0.5. This release is now available in the HBT (Testing branch).

This release is for all of our routers including Turris 1.x, which needs to boot from microSD card and it is based on the OpenWrt version 18.06.6. It includes the latest development version of ReForis, multiple CVE fixes and package updates.

Full changelog:

  • Based on the latest OpenWrt 18.06.6
  • kernel: update to version 4.14.162
  • python3: update to version 3.6.10
  • nextcloud: update to version 16.0.7
  • mariadb: update to version 10.4.11
  • foris: fix for three-level name timezones
  • wget: fix CVE-2019-5953
  • unbound: update to version 1.9.6
  • php7: update to version 7.2.26
    Fixes: CVE-2019-11044, CVE-2019-11045, CVE-2019-11046, CVE-2019-11047, CVE-2019-11050
  • nano: update to version 4.7
  • openssl: update to version 1.0.2u
  • bird: update to version 1.6.8
  • reforis: update to the latest development version, adds openvpn-plugin
  • ffmpeg: update to version 4.0.5
    Fixes: CVE-2019-12730, CVE-2019-17539, CVE-2019-17542
  • e2fsprogs: fix CVE-2019-5094
  • christmas: removed from default installation

If you would like to try this release, you need to login to your router via SSH and run following
command: switch-branch hbt
It will switch you to HBT branch. If you will want to use again stable release, you need to run this command switch-branch hbs

When you found any bugs, please let us know about them, so we can fix it.


Where is Turris OS 4.0.4?

MOX: reboot works, reForis works, Managed devices (client for TOS 3.11.12) works.

1 Like

The name would speak for itself, is like in China the number 4 which brings bad luck. 4.0.4 looks like 404 errors.
Joking aside, I have no idea why the number was skipped.

Best regards

Not really a bug, but maybe it is possible to unmark the kmod-ath10k as critical package on omnia devices. so it can be replaced by a user-updater.lua, with kmot-ath10k-ct, as it is more stable on my device/setup then the default kernel drivers.

This does not work me, because of the critical flag an kmod-ath10k, or maybe i’m configuring it wrong:

Uninstall("ath10k-firmware-qca988x", { priority = 60 })
Uninstall("kmod-ath10k", { priority = 60})
1 Like

MOX classic, simple config, reboot after instalation of 4.0.5 stuck, after power down/up OK, both WiFi working,

Hi, after this update my CPU usage jumped from cca 0 - 10 % to 51 -52 % on my Omnia. Strange thing was that after updating the CPU jumped to 100 % and router responded slowly. So I rebooted it - it worked only with the button. And after that everyting works (only with the higher CPU usage). After the first try I decided to flash the newest medkit. After updating I experienced same behavior - CPU jump vrom 10 to 52 % and “lagging” after update to 4.0.5 with need to reboot via button on the back side of the case.

In that case, we need more details such which process were causing it, output from the /var/log/messages would be helpful. What will help us the most are diagnostics. They contains a lot of useful details for troubleshooting the issue, which you experienced.

You do not have to use Uninstall in this case. Package you want provides critically requested package so switch can be done without making it non-critical.

Repository index for kmod-ath10k
Package: kmod-ath10k-ct
Version: 4.14.162+2018-03-16-30827f7d-3-0a66bb0316b4402bf65555c64ceed313.14
Depends: kernel (=4.14.162-1-0a66bb0316b4402bf65555c64ceed313.0), kmod-mac80211, kmod-ath, kmod-hwmon-core
Provides: kmod-ath10k
License: GPLv2
Section: kernel
Architecture: arm_cortex-a9_vfpv3
Installed-Size: 182441
Filename: kmod-ath10k-ct_4.14.162+2018-03-16-30827f7d-3-0a66bb0316b4402bf65555c64ceed313_arm_cortex-a9_vfpv3.ipk
Size: 181615
SHA256sum: 988e2f7ade5840dde7efa6ba86b91dc363895af621f90f02d043ce70e2c2baae
Description:  ath10k-ct driver optimized for CT ath10k firmware

Package: kmod-ath10k
Version: 4.14.162+2017-11-01-10-0a66bb0316b4402bf65555c64ceed313.14
Depends: kernel (=4.14.162-1-0a66bb0316b4402bf65555c64ceed313.0), kmod-ath
Section: kernel
Architecture: arm_cortex-a9_vfpv3
Installed-Size: 154046
Filename: kmod-ath10k_4.14.162+2017-11-01-10-0a66bb0316b4402bf65555c64ceed313_arm_cortex-a9_vfpv3.ipk
Size: 153487
SHA256sum: d8f1c7c00e8307e06fc412be24d24c7fbad4e323b6f6189451ef9da3163ce55f
Description:  This module adds support for wireless adapters based on
 Atheros IEEE 802.11ac family of chipsets. For now only
 PCI is supported.

Just use


and run pkgupdate. For me it suggests following change which is what you want:

INFO:Queue install of kmod-hwmon-core/core/4.14.162-1-0a66bb0316b4402bf65555c64ceed313.0
INFO:Queue install of kmod-ath10k-ct/core/4.14.162+2018-03-16-30827f7d-3-0a66bb0316b4402bf65555c64ceed313.15
INFO:Queue install of ath10k-firmware-qca988x-ct-htt/base/2018-05-12-952afa49-1.23
INFO:Queue removal of ath10k-firmware-qca988x
INFO:Queue removal of kmod-ath10k
1 Like

Turris Mox RC 4.0.5

Router after the update an openvpn key etc/hdparam/dh2048.pem is created.
CPU 100%, one core - 10 minutes.


Chyba z 16. 01. 2020 10:57:33

Updater selhal:

inconsistent: Requested package lxc that is not available.

Thank you for reporting it. We are sorry. This was latest build seccomp update and we missed that LXC failed to compile. We hope to fix that with next RC release.

Is there a plan to update nextcloud to major version 17? The current version is 17.0.2

I would like to update Nextcloud to it’s the latest major version, but we want to ensure a smooth upgrade we need to update the current version, which is still supported to version 16.0.7. This was done in this version.

Hello guys,

This time we are releasing an RC2 version of Turris OS 4.0.5.

  • We have managed to fix the compile of the LXC package, which was reported by you. It was caused by a security update of the library seccomp. Recently, there was introduced a new header file, which required by LXC. The fix will be sent to OpenWrt as well.

  • In this version, we have added Atlas SW Probe package.
    More details about it can be found in community documentation.

Thanks to anyone, who tested the first RC version.


OK, I’ll send you that.