Why Sentinel behind Omnia?
Read more carefuly - all extras like sentinel are on Omnia!
Would you mind to try it and let us know, how it goes? 
If anything goes wrong, you can always use rollback to previous snapshot.
nah, also the wifi 2.4 is rather crucial/important, or the wrath of some employees will crush me 
So, thats a nogo…sorry.
According to configurator Qualcomm card can be set to 5 or 2.4 GHz… I don’t have experience about it, but you can try it…
Running pkgupdate from CLI on MOX there were a lot of warnings like
WARN:Collision with existing path. Moving /lib/preinit/00_preinit.conf to /usr/share/updater/collided/lib/preinit
Is it OK?
Partial copy of pkgupdate output
TurrisOS 6.0, Turris Mox
BRANCH: hbk
…
INFO:Target Turris OS: 6.0
INFO:Queue upgrade of base-files/core/1454-6.0-r16672+128-fc86176363[1454-6.0-r16670+128-c670dfb733]
Press return to continue, CTRL+C to abort
INFO:Downloading packages
INFO:Executing preupdate hook: 05_schnapps.sh
Snapshot number 83 created
INFO:Unpacking download packages
INFO:Checking for file collisions between packages
INFO:Running pre-install and pre-rm scripts and merging packages to root file system
WARN:Collision with existing path. Moving /lib/preinit/00_preinit.conf to /usr/share/updater/collided/lib/preinit
— a lot of similar lines —
…
Just delete everything from:
root@router:/usr/share/updater/collided
To save space.
Hi, i’m trying to install TOS6 to my turris1.x . But when i switch branch to hbk, and when putting command pkgupdate in console, it targeting to version 5.4.4 . What am i doing wrong?
Switch-branch already sets the repo and runs the pkgupdate for you. Just switch-branch hbk and wait for it to finish and reboot
Edit: @Vituhlos also read Known Issues as there is problem now with turris1.x you should wait until Turris Team finds the cause of problem and fix it
@Pepe are this CVEs fixed in this release?
Package : lighttpd
CVE ID : CVE-2022-37797 CVE-2022-41556
I saw it on Debian Security mailinglist and wondered if its fixed also in TurrisOS.
Lighttpd is indeed updated in Turris OS 6.0 to its newest version, but…
CVE-2022-37797
- Affects only mod_wstunnel. It is shipped in the standalone package
lighttpd-mod-wstunnel. Based on the users, who are willing to send us data from Turris Survey (It is entirely voluntary and opt-in in reForis), I found that only one guy has this package installed. - Not included in default installations.
CVE-2022-41556
- Turris OS is not affected by this CVE due to a non-zero lighttpd.conf setting
server.stream-request-bodysince Turris OS 5.3.0.
We need to thank @gstrauss, the lighttpd developer, who reached us several days ago and let us know privately about these vulnerabilities.
6 Likes
This I tried once, doesn’t work good.
I upgraded an Omnia Turris from HBS (5.4.4) to HBK (6.0) and experiences the following bugs / issues:
- After the update a notification with the error “Updater failed: Failed operations: rainbow/postinst: Command failed: Not found /usr/bin/rainbow: line 45: can’t create /sys/class/leds/rgb:power/device/bightness:nonexistent directory” was shown
- Luci Adblock was not working due to sort being linked to busybox instead of coreutils-sort. Fixed itself after running pkgupdate on 6.0 again.
- Sentinel “Enable Firewall Logs” not working with /var/log/messages showing “sentinel-fwlogs: Resource temporarily unavailable”
- Web UI: Connection Test in reForis not working (icon keeps spinning) when the web UI is accessed using Google Chrome. It works when accessed using Firefox
- Web UI: Certificate of web UI cannot be trusted in Google Chrome (even after importing as trusted Root CA) due to missing SAN entry
1 Like
So I’m starting to think about trying HBK on one of my MOXes.
Depending on your config and use it’ll be easy or complicated… Good luck!
2 Likes
The absence of SDIO could be an advantage for router stability.
Current changelog.
Builds for Turris 1.x routers were allowed, packages are ready in HBK. 
There is one slight difference - it is using LTS kernel 5.10.
One of today updates, broke wifi completely had to rollback to get it working. Seems that it is related to update to kernel 5.15.73.
Switching to HBT, where is kernel 5.15.72 and everything is working. Hope there will be less surprises such as this one.
That happened in one of earlier today’s build, but it should be alright now for Turris MOX. For Turris Omnia, there is going to be a new build, which will address this. Hopefully, in a few minutes! 