We have just released Turris OS 5.1.10 from HBT (Testing) branch. This release is the last fixup release for Turris OS 5.1. Because we are working on bringing to you minor release Turris OS 5.2 with new features!
Here goes highlights of this release - Turris OS 5.1.10:
Fixed Python3 vulnerabilities - CVE-2021-3177 and CVE-2021-23336
Fixed Open vSwitch vulnerability - CVE-2020-35498
Fixed screen vulnerability - CVE-2021-26937
Fixed BIND vulnerability - CVE-2020-8625
There is also updated kernel, unbound, knot-resolver, knot, hostapd, unbound, zerotier, netdata, nano and and rest.
We suggest to update to this version as soon as possible to make your routers safe as Python3 and a few tools from BIND package are preinstalled.
If you are using automatic updates, you will be updated to this version soon. However, if you are using delayed updates or approvals, take a look at Updater tab to confirm the update.
As usual, we would like to hear feedback regarding this release and if there are any bugs, please let us know!
New Omnia (standard config) -> installation, reboot -> ok.
Old Omnia -> (lxc, connedted hardware and other) -> installation, reboot -> reboot -> reboot -> rollback -> reboot -> installation, reboot -> reboot. And then I figured out that my problems with Z-Stick are not connected to kernel, but to rear usb port. In front port it worksâŚ
There is another thread for this problem.
Turris Omnia 5.1.9 -> 5.1.10. Worked smoothly and it is running fine. Standard setup + OpenVPN, Nextcloud, DDNS.
I have attached netbooted Mox, which again required the revoke, factory reset and accept procedure to be in functional state and recognized by Omnia. This issue is already described on GitLab.
Hello, there are probably some changes in driver for wifi cards, because there are troubles for me. Tested on my old Turris 1.0 and there seems to be problem - wireless card is connected, but⌠I have no IP address , I got only autoconfig address 169.x.x.x . In my Mox all seems to be all OK without problems. On my older blue turris I made roll back via schnapps to 5.1.9 and all seems to be fine now.
So please are there any driver changes here ? If yes, for me on older hardware doesnât work properly⌠sorry.
Updated Omnia Indiegogo 2GB RAM and MOX P-A(SDIO)-B(Mikrotik R11e-2HnD): Omnia had no issues at all, with MOX the SDIO-WiFi signal strength is still very very bad.
My Omnia has quite big amount of dropped packets even in LAN. I think it happens with all 5.1* versions. Are there any way to understand why itâs happening and fix it?
Info:
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 532
RX: bytes packets errors dropped overrun mcast
10941207351 30208664 0 637 0 0
TX: bytes packets errors dropped carrier collsns
64174016004 55901787 0 0 0 0
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 532
RX: bytes packets errors dropped overrun mcast
73890804108 62397126 0 81283 0 0
TX: bytes packets errors dropped carrier collsns
10944755198 26096959 0 0 0 0
5: lan0@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP group default qlen 1000
RX: bytes packets errors dropped overrun mcast
6089980501 16519391 0 8 0 0
TX: bytes packets errors dropped carrier collsns
27413419862 21534163 0 0 0 0
6: lan1@eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UP group default qlen 1000
RX: bytes packets errors dropped overrun mcast
3967151679 11466878 0 30174 0 0
TX: bytes packets errors dropped carrier collsns
35891907166 31704863 0 0 0 0
Well, you have already owm thread Omnia drops a lot of packets over ethernet and there is no need to write it under this post, which compares changes from previous version of Turris OS. If anything, Turris support is ready to help you.
This error, which you got regarding Bad Gateway known as HTTP error code 502 was related to a small outage on one of our servers, which affected repo.turris.cz, and we fixed that within an hour so you should receive it just once and no longer since. Updater tries to check for new updates every 4 hours.
You can check if there are other same notifications or go to the Updater tab and press Save changes w/o modifying anything, and Update will start its process in the background.
No, it would help if you distinguished these error messages. Error message with 502 Bad Gateway was just once this week, and it didnât happen recently. Others like connection timeout, couldnât resolve are most likely related to yourâs Internet connection.
(Testing) branch. This release is the last fixup release for Turris OS 5.1. Because we are working on bringing to you minor release Turris OS 5.2 with new features!