At the end of last month we moved Turris OS 6.0 (based on OpenWrt 21.02) from the HBL to the HBK branch. We are now moving it to HBT for final testing before a stable release.
This only affects users who opted in for testing and switched their branch to HBT.
What’s new?
Breaking Changes
Based on the latest OpenWrt 21.02.4 release
LuCI supports L2 and L3 configuration
LTS kernel 5.15
Foris removed (use reForis exclusively now)
Lighttpd uses number prefixes for configuration files to ensure a predictable order
New Features
Morce (integrated IDS)
reForis Nextcloud plugin
Wi-Fi 6 cards supported
Turris Auth (login gateway)
PaKon moved to a separate page
New LEDs driver for all routers
Dashboard in LuCI
NetMetr supports measurement with IPv6 address
Bug Fixes
Fixed Ethernet ports numbering for Turris MOX in reForis
Updates
Python version 3.7 ➔ 3.9
Lighttpd version ➔ 1.4.67
Nextcloud version ➔ 22.2.10
Other Changes
Obsolete SIDN package feed dropped
Known issues
High:
SDIO WiFi module on Turris MOX doesn’t work. The update to 6.0 will not happen on routers with SDIO WiFi for now.
*Turris 1.x routers take a long time to boot which causes other issues. Turris OS 6.0 is not available yet due to this issue. Fixed in RC2.
Also iputils-ping6 is missing, but the command is now in iputils-ping and ping -6 works as well. (I expect there may be multiple packages with similar kind of changes.)
In my case the Omnia froze during update. I could only get it to answer to ping over wire, but no WiFi, no routing, no reForis. It seems OK after reboot (which lost logs about that, etc.)
Just for information, with the self signed certificate WebSocket doesn’t work with Chrome.
To bypass the NET::ERR_CERT_INVALID warning I had to type ‘thisisunsafe’ but after that WebSocket will be “blocked”, I was wondering why Test connection was working.
No problem with Firefox or with Chrome in http. But is not a problem but a behaviour of Chrome.
Edit : I have to same problem with a valid certificate
Edit2: Correction, it works with a valid certificate and lighttpd correctly configured.
Edit3: It works one time and randomly when launching with : lighttpd -f /etc/lighttpd/lighttpd.conf
Yeah mine froze too after autoupdate. No routing, no foris, no luci, no login over sshd, no automatic reboot. Works fine after manual reboot, linux containers (lxc) with devices.allow broke though
Will it be possible to put here correct /etc/config/rainbow for all new LED naming in rainbow config for Omnia and Turris 1x ?
Even after I reinit it from scratch I am unable to set leds correctly on both routers and in LuCi I see some color names in english and some in Czech. Either way it is not reinitialized correctly from LuCI.
sorry I’m not at home now, but it seems this issue will be easily reproducible, I performed multiple 3LED and 4LED resets and the issue is persisting no matter what I set in LUCI or etc/config/network.
It is indeed visual bug and wifi should be working fine regardless of it, thanks for reporting this!
I agree that it is quite easily reproducible, see the issue in our gitlab. Feel free to add aditional details to the issue, in case we missed something.
I guess that you performed simple upgrade to TOS 6.0 with already configured wifi, right?