Turris OS 5.0.4 is released in the HBS (Stable) branch

Dear Turris users,

It is a pleasure to inform you that we just released Turris OS 5.0.4 in HBS (Stable) :snail: branch.

Highlight of this fixup release:

  • This release allows you to use multiple SSID on Turris MOX SDIO Wi-Fi card as our kernel developers, were able to take a look at mwifiex driver and they fixed memory corruption, which gets backported to LTS versions and it also needed some improvements in hostapd.

What has been changed in this release?

  • security updates for Python 3, squid, libvorbisidec, ntpd, bind
  • updates for msmtp, mwan3, xz, zstd, sumo, gkrellmd, golang, haveged, dnscrypt-proxy2, openvswitch.

You will be updated to this version automatically. If you are using updates on approval or delayed updated, you can apply the update in Foris.

As always, we appreciate any feedback regarding this release.

4 Likes

List of known bugs:

Since Turris OS 3.x release:
This time, there was no any ddns-package update, so you don’t need to worry about, but if you came from earlier versions of Turris OS, be careful!

Since Turris OS 4.x release:

Since Turris OS 5.0 release:

  • Some Knot DNS packages can not be installed. This is fixed in development version of Turris OS 5.1.
  • Package v4l-utils was not compiled. This is going to be fixed in Turris OS 5.1.

And I got ~20s internet connection interruption when updater restarted network interfaces. This isn’t good thing to have during a work meeting. Are there any chance to do automatic updates only during night?
I don’t wanna to switch to approving the updates, but I need to have no interruptions during working hours.

So far openvpn seems mostly stable. At least doesn’t appear to be crash-looping.

not here. Openvpn has been looping in 5.0.4 since the update.
with this kind of logging

Jul 24 12:55:58 turris firewall: Reloading firewall due to ifup of vpn_turris (tun_turris)
Jul 24 12:56:00 turris openvpn(server_turris)[24439]: event_wait : Interrupted system call (code=4)
Jul 24 12:56:00 turris openvpn(server_turris)[24439]: /sbin/route del -net 10.111.111.0 netmask 255.255.255.0
Jul 24 12:56:00 turris openvpn(server_turris)[24439]: Closing TUN/TAP interface
Jul 24 12:56:00 turris openvpn(server_turris)[24439]: /sbin/ifconfig tun_turris 0.0.0.0
Jul 24 12:56:00 turris netifd: Network device ‘tun_turris’ link is down
Jul 24 12:56:00 turris netifd: Interface ‘vpn_turris’ has link connectivity loss
Jul 24 12:56:00 turris netifd: Interface ‘vpn_turris’ is now down
Jul 24 12:56:00 turris openvpn(server_turris)[24439]: SIGTERM[hard,] received, process exiting
Jul 24 12:56:00 turris netifd: Interface ‘vpn_turris’ is disabled
Jul 24 12:56:00 turris openvpn(server_turris)[25036]: OpenVPN 2.4.7 arm-openwrt-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD]
Jul 24 12:56:00 turris openvpn(server_turris)[25036]: library versions: OpenSSL 1.1.1g 21 Apr 2020, LZO 2.10
Jul 24 12:56:00 turris openvpn(server_turris)[25036]: Diffie-Hellman initialized with 2048 bit key
Jul 24 12:56:00 turris netifd: Interface ‘vpn_turris’ is enabled
Jul 24 12:56:00 turris netifd: Network device ‘tun_turris’ link is up
Jul 24 12:56:00 turris netifd: Interface ‘vpn_turris’ has link connectivity
Jul 24 12:56:00 turris netifd: Interface ‘vpn_turris’ is setting up now
Jul 24 12:56:00 turris netifd: Interface ‘vpn_turris’ is now up
Jul 24 12:56:00 turris openvpn(server_turris)[25036]: TUN/TAP device tun_turris opened

Back in 5.0.3 now.
No more problem.

Looks like openvpn is not working. Technically i am connected, but cannot reach any device IP.

I have set delayed update (48h) and delayed restart (3days at 3:30). I just returned from holiday and before I was able to approve the update, it was auto approved, installed and… restarted. At 21:27. Not in night and 3 days earlier. Why?

image

I updated this morning from 5.0.2 and everything seems to work fine. My system is pretty vanilla with only UPnP installed though.

I haven’t used the WIFI modules for awhile as they were unstable but am pleasantly surprised to find out they work great now!

Thanks for the great update.

It seems after some time within 5.0.x SATA HDD RAID NAS issue were reintroduced. I am using 5.0 stable from automatic migration from 4. stable, however I’m guessing from 5.0.2, I’m not 100% sure which exactly. SATA is working properly on one port only. Other HDD fails, symptoms as in old post: https://forum.turris.cz/t/sata-hdd-issues/1173/160

1 Like