Turris OS 5.0 is released!

Dear Turris users,

We would like to inform you about a new major version Turris OS 5.0, which was released to HBS :snail: (Stable) branch from HBT :turtle: (Testing) branch.

This version is based on the latest OpenWrt version 19.07.3 with our features, our userspace, and our kernel configuration. Among security updates, there are new packages and the most important new features and new packages.

All Turris routers, which are using automatic updates and has version Turris OS 4.0.5, they will get this update soon. There is experimental support for Turris 1.x routers as if you would like to give it try, you need to boot from microSD card and using Btrfs. When you are using Approvals, there’s going to be a notification for you.

I’m going to show you some highlights in this version:

  • We have been working on our redesigned Foris (reForis), which has now a few amazing features like snapshots integration and remote control, but it is in the development.
  • In default configurations, there is enabled support for USB Mass Storage devices by default to use Storage plugin without installing package list NAS.
  • There is added support for secondary IP addresses for DNS servers and enabled TLS for Google DNS servers.
  • There is a basic migration from samba3 to samba4.
  • As a time-based job scheduler, we are using cronie instead of vixie-cron, which is no longer under development.
  • For webapps, there is an automatic redirect to HTTPS, if it is possible.
  • LuCI is using client-side rendering for improved performance.
  • There is a new version of Updater, which should take less memory during the update.
  • Removed sysupgrade from the system as it is dangerous.
  • New package gerbera, which should be a replacement for MiniDLNA, and someone had some issues with MiniDLNA.
  • Added hack for ppp, which improves stability in some cases.
  • There is an updated RIPE Atlas Probe to its latest version.
    Some of you experienced that in some cases that probe is shown on the website as disconnected. These should be narrowed be in a few minutes and in some cases it takes hours.
  • Optional WPA3 support

More information can be found on our Gitlab or in the OpenWrt changelog. We want to thank anyone, who tested this release in the HBT (Testing) branch.

All Turris routers, which are using automatic updates and has version Turris OS 4.0.5, they will get this update soon. There is experimental support for Turris 1.x routers as if you would like to give it try, you need to boot from microSD card and using Btrfs. When you are using Approvals, there’s going to be a notification for you.

If you find out any bugs, please write an e-mail to tech.support@turris.cz and don’t forget to include if possible outputs.

We appreciate any feedback for this release.

10 Likes

Known bugs since Turris OS 4.0 release:

  • In some cases, Turris MOX is not correctly rebooted.
  • MOX SDIO Guest networking is still not supported, yet. This is going to be fixed in upcoming fixup releases.

Known bugs which were discovered in HBT branch:

  • ReForis is still experimental and if you were using Delayed updates or updates on Approvals, it might be possible that in reForis, which is not default you might experience - An unknown API error occured when you are going to save packages, but this is working on Foris.

Known bugs in this release:

  • syslog-ng does not start if you have disabled interface for IPv6.
  • package v4l-utils was not compiled

Removed packages:

  • zip
1 Like

MOX SDIO 5 GHz networking is still not stable, yet. This could be fixed in upcoming fixup releases.

Patch was available in older releases of TOS 4.

When will be released new u-boot for older Omnias? I can’t find any current information in forum or TOS 5 changelog. With upgrade from TOS 3 does not work automatic SFP switching.

My Omnia just got updated in the middle of the day! Fortunately, everything seems to be working except the new “redesigned Foris (reForis)”. I still have foris version: 100.7, do I have to switch it manually or something? Thanks.

From which version you upgrade?

Install reForis via Foris.

1 Like

It was an automatic update. I think I had Turris OS 4.0.5.

All righty, thanks.

Great! Thanks for feedback.

Congratulations on the release!

Since I’ve been testing the RCs, my Omnia is set to the hbt branch. Do I need to manually switch it to hbs, to get the “real” 5.0.0? The last set of updates that got installed were from last night, which would seem to correspond to 5.0.0-RC7.

Also, with the release of 5.0.0, now might be a good time to clarify the security update/EOL policy for OS 3.x/4.x/5.x. I’ve seen various threads on the forum with slightly contradictory/confusing comments as to what versions get/will get security updates, and till when.

Is the canonical reference for this policy intended to be https://docs.turris.cz/basics/tos_versions/?

HBS and HBT are same for now.

TOS 3 is supported, obsolete and stable (and for somebody not completely safe)
TOS 4 is unsupported, vulnerable and not fully stable
TOS 5 is supported, secure and with next minor releases also stable

1 Like

opkg update doesn’t work after auto update from 4.0.5 to 5.0. Probably because wget is not present in the system.

log
root@turris:~# opkg update
Downloading https://repo.turris.cz/hbs/omnia/packages/core/Packages.gz
*** Failed to download the package list from https://repo.turris.cz/hbs/omnia/packages/core/Packages.gz

Downloading https://repo.turris.cz/hbs/omnia/packages/base/Packages.gz
*** Failed to download the package list from https://repo.turris.cz/hbs/omnia/packages/base/Packages.gz

Downloading https://repo.turris.cz/hbs/omnia/packages/cesnet/Packages.gz
*** Failed to download the package list from https://repo.turris.cz/hbs/omnia/packages/cesnet/Packages.gz

Downloading https://repo.turris.cz/hbs/omnia/packages/luci/Packages.gz
*** Failed to download the package list from https://repo.turris.cz/hbs/omnia/packages/luci/Packages.gz

Downloading https://repo.turris.cz/hbs/omnia/packages/node/Packages.gz
*** Failed to download the package list from https://repo.turris.cz/hbs/omnia/packages/node/Packages.gz

Downloading https://repo.turris.cz/hbs/omnia/packages/openwisp/Packages.gz
*** Failed to download the package list from https://repo.turris.cz/hbs/omnia/packages/openwisp/Packages.gz

Downloading https://repo.turris.cz/hbs/omnia/packages/packages/Packages.gz
*** Failed to download the package list from https://repo.turris.cz/hbs/omnia/packages/packages/Packages.gz

Downloading https://repo.turris.cz/hbs/omnia/packages/routing/Packages.gz
*** Failed to download the package list from https://repo.turris.cz/hbs/omnia/packages/routing/Packages.gz

Downloading https://repo.turris.cz/hbs/omnia/packages/sidn/Packages.gz
*** Failed to download the package list from https://repo.turris.cz/hbs/omnia/packages/sidn/Packages.gz

Downloading https://repo.turris.cz/hbs/omnia/packages/telephony/Packages.gz
*** Failed to download the package list from https://repo.turris.cz/hbs/omnia/packages/telephony/Packages.gz

Downloading https://repo.turris.cz/hbs/omnia/packages/turrispackages/Packages.gz
*** Failed to download the package list from https://repo.turris.cz/hbs/omnia/packages/turrispackages/Packages.gz

Collected errors:
 * opkg_download: Failed to download https://repo.turris.cz/hbs/omnia/packages/core/Packages.gz, wget returned 255.
 * opkg_download: Failed to download https://repo.turris.cz/hbs/omnia/packages/base/Packages.gz, wget returned 255.
 * opkg_download: Failed to download https://repo.turris.cz/hbs/omnia/packages/cesnet/Packages.gz, wget returned 255.
 * opkg_download: Failed to download https://repo.turris.cz/hbs/omnia/packages/luci/Packages.gz, wget returned 255.
 * opkg_download: Failed to download https://repo.turris.cz/hbs/omnia/packages/node/Packages.gz, wget returned 255.
 * opkg_download: Failed to download https://repo.turris.cz/hbs/omnia/packages/openwisp/Packages.gz, wget returned 255.
 * opkg_download: Failed to download https://repo.turris.cz/hbs/omnia/packages/packages/Packages.gz, wget returned 255.
 * opkg_download: Failed to download https://repo.turris.cz/hbs/omnia/packages/routing/Packages.gz, wget returned 255.
 * opkg_download: Failed to download https://repo.turris.cz/hbs/omnia/packages/sidn/Packages.gz, wget returned 255.
 * opkg_download: Failed to download https://repo.turris.cz/hbs/omnia/packages/telephony/Packages.gz, wget returned 255.
 * opkg_download: Failed to download https://repo.turris.cz/hbs/omnia/packages/turrispackages/Packages.gz, wget returned 255.
root@turris:~# wget
-ash: wget: not found

update1: Issue was fixed by running pkgupdate.

update2: 5Ghz wifi didn’t worked. Solved by running opkg remove kmod-ath10k && opkg install kmod-ath10k-ct

update3: pkgupdate produces:

INFO:Target Turris OS: 5.0.0
WARN:Package wpad is in cyclic dependency. It might fail its post-install script.
WARN:Package hostapd is in cyclic dependency. It might fail its post-install script.
WARN:Requested package luci-i18n-rainbow-en that is missing, ignoring as requested.
WARN:Requested package luci-i18n-sqm-en that is missing, ignoring as requested.

Is it expected?

2 Likes

30 posts were split to a new topic: Samba 4 changes

My Turris 1.0 got updated automatically to TOS 5.0 from 4.0.x . There was error shown - “You deinstalled btrfs support but your router is still using it, so it will likelly break.”

Do I need to be concerned ?

Router seems to be running fine after restart …

It is common condition.

Was it? The hack was present in Turris OS 3.x. It was not included in Turris OS 4.0.

Wasn’t it beautiful? Would you rather receive an update during the midnight? In the Updater tab, there is a possibility to use Delayed updates or Approved updates.

In the past, I wrote some posts about it, and hopefully, those were not confusing nor contradictory. If yes, please say it loud next time, ok?

  • Turris OS 3.x version is still supported. Today we released a new release 3.11.17 and the next one is coming! If you are asking about automatic migration, there is going to be and I can not give you an exact date when migration at least for advanced users will be possible. However, this will not cover all cases. If you are not sure or don’t you want to wait for whatever reason just jump on the Turris OS 5.0 way by medkit.
  • Support has been ended Turris OS 4.0.x once Turris OS 5.0 was released.

Documentation is going to be updated. We are aware of it and thanks for reporting!

HBS and HBT are the same for now. This is going to be changed once we release a new release in HBT.

Can you please provide me some logs to know what happened? Did you do a restart of your router?

This means that you have installed rainbow and sqm packages, which does not have separated the English language and it could mean that the English language is part of the standalone package. It is a common behavior that English packages have their own package. These are harmless. I checked it for you and the warning for luci-i18n-sqm will be gone once OpenWrt 20.xx is released, because it is fixed in their master and rainbow is our package.

This happened because turris-btrfs package was renamed to turris1x-btrfs that’s why it sent you the scary notification. You just need to check it that you have it installed and it’s going to be just fine.

Thanks,
I’ve the same issues. No wget and missing 5GHz wifi card.

Omnia on 4.0.5, updated during the day.

This update was very strange. Wifi stopped, all leds on router were lighting except WAN led that blinked. So I’ve restarted omnia and later on I’ve found, that it was probably caused by update :open_mouth:

When my Omnia auto updated earlier (without me knowing), it knocked out the wifi so I went and powered it off and on again since I thought something had crashed. I think this may have been mid-update as it came back on okay, but a few things (like OpenVPN) weren’t working properly.

I reinstalled 4.0.5 with medkit, restored a config backup and let it update again and all seems good now.

I noticed /etc/config/backups was overwritten though (I’d added extra directories to backup).

1 Like

Do you have any logs? It seems to me like unfinished update. What means missing 5 GHz card? Is is not visible in lspci? Is there anything in /var/log/messages?

This was not reported in the Testing branch and it was not reported it to us on support.

In any case → Support: Getting help.

I’ve found dmesg on terminal:

[   29.995259] NET: Registered protocol family 24
[   30.015868] pci 0000:00:02.0: enabling device (0140 -> 0142)
[   30.023898] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[   30.264017] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
[   30.274772] ath10k_pci 0000:02:00.0: Falling back to user helper
[   30.536590] firmware ath10k!pre-cal-pci-0000:02:00.0.bin: firmware_loading_store: map pages failed
[   30.545713] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
[   30.556157] ath10k_pci 0000:02:00.0: Falling back to user helper
[   30.566649] firmware ath10k!cal-pci-0000:02:00.0.bin: firmware_loading_store: map pages failed
[   30.575448] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-6.bin failed with error -2
[   30.586199] ath10k_pci 0000:02:00.0: Falling back to user helper
[   30.596679] firmware ath10k!QCA988X!hw2.0!firmware-6.bin: firmware_loading_store: map pages failed
[   30.605771] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-5.bin failed with error -2
[   30.616517] ath10k_pci 0000:02:00.0: Falling back to user helper
[   30.626940] firmware ath10k!QCA988X!hw2.0!firmware-5.bin: firmware_loading_store: map pages failed
[   30.636033] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-4.bin failed with error -2
[   30.646775] ath10k_pci 0000:02:00.0: Falling back to user helper
[   30.657178] firmware ath10k!QCA988X!hw2.0!firmware-4.bin: firmware_loading_store: map pages failed
[   30.666269] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-3.bin failed with error -2
[   30.677007] ath10k_pci 0000:02:00.0: Falling back to user helper
[   30.687400] firmware ath10k!QCA988X!hw2.0!firmware-3.bin: firmware_loading_store: map pages failed
[   30.696488] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/firmware-2.bin failed with error -2
[   30.707226] ath10k_pci 0000:02:00.0: Falling back to user helper
[   30.717615] firmware ath10k!QCA988X!hw2.0!firmware-2.bin: firmware_loading_store: map pages failed
[   30.726667] ath10k_pci 0000:02:00.0: Failed to find firmware-N.bin (N between 2 and 6) from ath10k/QCA988X/hw2.0: -11
[   30.737320] ath10k_pci 0000:02:00.0: could not fetch firmware files (-11)
[   30.744130] ath10k_pci 0000:02:00.0: could not probe fw (-11)
[   30.759497] usbcore: registered new interface driver qcserial
[   30.765309] usbserial: USB Serial support registered for Qualcomm USB modem

I fixed this by installing kmod-ath10k-ct package as MightyWarrior suggested on Turris OS 5.0 is released!

Note: I had the -ct firmware installed before update:

root@turris:/tmp# opkg remove kmod-ath10k
Package unison version 2.51.2-1 has no valid architecture, ignoring.
Package libexpat version 2.2.9-1.0 has no valid architecture, ignoring.
Removing package kmod-ath10k from root...
WARNING: You probably just removed a package that was installed as part of a user list or the basic system. This package will return durring the next updater run. We suggest you disable the user list instead.
root@turris:/tmp# opkg install kmod-ath10k-ct
Installing kmod-ath10k-ct (4.14.180+2019-09-09-5e8cd86f-1-58f4a00531100abb0e5ec1c98b13b78d.0) to root...
Downloading https://repo.turris.cz/hbs/omnia/packages/core/kmod-ath10k-ct_4.14.180%2b2019-09-09-5e8cd86f-1-58f4a00531100abb0e5ec1c98b13b78d_arm_cortex-a9_vfpv3-d16.ipk
Installing kmod-hwmon-core (4.14.180-1-58f4a00531100abb0e5ec1c98b13b78d.0) to root...
Downloading https://repo.turris.cz/hbs/omnia/packages/core/kmod-hwmon-core_4.14.180-1-58f4a00531100abb0e5ec1c98b13b78d_arm_cortex-a9_vfpv3-d16.ipk
Configuring kmod-hwmon-core.
Configuring kmod-ath10k-ct.

This sounds great.
Nevertheless there’s one important thing missing for me to start the upgrade procedure 3.11.x to 5.x on both of my TO: would you please please write an official guide on how to correctly use VLAN-tagging?
Yes, there are various threads on this, but no clear main description on how to do it… My network depends on working VLANs, therefore I really need this to work.

2 Likes