Turris OS 3.11.9 is released!

Dear Turris users,

It’s pleasure to announce that we released Turris OS 3.11.9 from RC release for Turris 1.x and Turris Omnia routers. In contains mainly security fixes (the most noticeable security update is for tcpdump, which fixes multiple CVEs) and bug fixes with various improvements.

Changelog for Turris OS 3.11.9:
• tcpdump, sudo, uci, libarchive, luci: security update
• knot-resolver, wireguard, kernel, youtube-dl, turris-maintain, knot: update
• foris-controller-openvpn-module: fix server ip address autodetection
ripe-atlas-probe, atlas-sw-probe: new packages

Enjoy and if you encounter any issues, let us know.

2 Likes

Not much joy until the SW Probe can be registed, which as of today however prints

This function is currently only available to pre-approved testers. We expect to open it up to the general public soon.

1 Like

Update action without problems on Omnia … I see only suricata CPU load in time 19:25-19:27 … after process resart it is ready

Log from time 19:25-1927

2019-11-20 19:25:01 info /usr/sbin/cron[14836]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2019-11-20 19:25:01 info /usr/sbin/cron[14837]: (root) CMD (/usr/bin/notifier)
2019-11-20 19:25:08 info kernel[]: [  760.535426] BTRFS info (device sda1): quota is enabled
2019-11-20 19:26:01 info /usr/sbin/cron[15615]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2019-11-20 19:26:01 info /usr/sbin/cron[15616]: (root) CMD (nethist_stats.lua)
2019-11-20 19:26:07 info ucollect[10628]: Updating filter addresses from version 52475771 to version 52475811 (epoch 4)
2019-11-20 19:26:07 info ucollect[10628]: Updating ipset turris_100FA4E0_lb_a_4_X from version 52475771 to version 52475811 (epoch 4)
2019-11-20 19:26:12 warning ucollect[10628]: epoll_wait on 4 interrupted, retry
2019-11-20 19:26:29 err netdata[5478]: PROCFILE: Cannot open file '/etc/netdata/.environment'
2019-11-20 19:26:39 debug kernel[]: [  851.413260] ucollect-fake-open-inet: IN=eth1 OUT= MAC=d8:58:d7:00:35:50:cc:2d:e0:26:3f:54:08:00 SRC=89.248.169.95 DST=10.109.54.199 LEN=40 TOS=0x00 PREC=0x00 TTL=239 ID=59089 PROTO=TCP SPT=55880 DPT=80 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x80000 
2019-11-20 19:27:01 info /usr/sbin/cron[17145]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2019-11-20 19:27:01 info /usr/sbin/cron[17146]: (root) CMD (/root/connCheck.sh > /dev/null 2>&1)
2019-11-20 19:27:47 info kernel[]: [  919.568144] device br-guest_turris left promiscuous mode
2019-11-20 19:27:52 info dnsmasq-dhcp[12777]: DHCPREQUEST(br-lan) 192.168.2.120 00:19:99:f9:40:18 
2019-11-20 19:27:52 info dnsmasq-dhcp[12777]: DHCPACK(br-lan) 192.168.2.120 00:19:99:f9:40:18 Fujitsu_kuchy

An some strange message befor load time

2019-11-20 19:17:01 info /usr/sbin/cron[5253]: (*system*) BAD FILE MODE (/etc/cron.d/suricata)


Dtto in context

2019-11-20 19:15:14 info ucollect[10628]: Retrying fake server configuration now
2019-11-20 19:15:14 info ucollect[10628]: Sending login credentials enabled
2019-11-20 19:15:18 info ucollect[4263]: Last message 'Sending login creden' repeated 5 times, suppressed by syslog-ng on turris
2019-11-20 19:15:52 info nikola[]: (v43.1) Establishing connection took 0.543756 seconds
2019-11-20 19:15:52 info nikola[]: (v43.1) Logrotate took 0.006294 seconds
2019-11-20 19:15:52 warning nikola[]: (v43.1) Failed to parse line: '2019-11-20T19:13:06+01:00 [   34.995368] IPv6: ADDRCONF(NETDEV_UP): br-guest_turris: link is not ready
'
2019-11-20 19:15:52 warning nikola[]: (v43.1) Failed to parse line: '2019-11-20T19:13:06+01:00 [   35.618405] IPv6: ADDRCONF(NETDEV_UP): guest_turris_1: link is not ready
'
2019-11-20 19:15:52 warning nikola[]: (v43.1) Failed to parse line: '2019-11-20T19:13:06+01:00 [   35.618419] br-guest_turris: port 1(guest_turris_1) entered forwarding state
'
2019-11-20 19:15:52 warning nikola[]: (v43.1) Failed to parse line: '2019-11-20T19:13:06+01:00 [   35.618445] br-guest_turris: port 1(guest_turris_1) entered forwarding state
'
2019-11-20 19:15:52 warning nikola[]: (v43.1) Failed to parse line: '2019-11-20T19:13:06+01:00 [   35.618489] IPv6: ADDRCONF(NETDEV_CHANGE): br-guest_turris: link becomes ready
'
2019-11-20 19:15:52 warning nikola[]: (v43.1) Failed to parse line: '2019-11-20T19:13:06+01:00 [   37.611012] br-guest_turris: port 1(guest_turris_1) entered forwarding state
'
2019-11-20 19:15:52 info nikola[]: (v43.1) Syslog parsing took 0.040402 seconds
2019-11-20 19:15:53 info nikola[]: (v43.1) Session init took 0.581650 seconds
2019-11-20 19:15:53 info nikola[]: (v43.1) Records parsed: 37
2019-11-20 19:15:53 info nikola[]: (v43.1) Records after filtering: 11
2019-11-20 19:15:53 info nikola[]: (v43.1) Records filtering took 0.008448 seconds
2019-11-20 19:15:53 info nikola[]: (v43.1) {'msg': 'Data were inserted into work queue.'}
2019-11-20 19:15:53 info nikola[]: (v43.1) Sending records took 0.026216 seconds
2019-11-20 19:16:01 info /usr/sbin/cron[11509]: (root) CMD (/usr/share/server-uplink/registration_code.sh)
2019-11-20 19:16:01 info /usr/sbin/cron[11510]: (root) CMD (nethist_stats.lua)
2019-11-20 19:16:01 info /usr/sbin/cron[11508]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2019-11-20 19:16:15 info kernel[]: [  228.037215] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
2019-11-20 19:17:01 info /usr/sbin/cron[11652]: (root) CMD (/usr/bin/rainbow_button_sync.sh)
2019-11-20 19:17:01 info /usr/sbin/cron[5253]: (*system*) BAD FILE MODE (/etc/cron.d/suricata)
2019-11-20 19:17:01 info /usr/sbin/cron[5253]: (root) RELOAD (crontabs/root)

The diagnostics file is saved

My Turris 1.0 dropped to constant reboot cycle after the upgrade to OS 3.11.9. I had to perform reset to default settings. OS 3.11.9 seems to be installed after the reset but I have not fully restored all settings. I still investigate what was the root of this… just wanted to share that it happened.

Also here with Omnia: Reboot loop after upgrade to 3.11.9

Hi, my Turris 1.0 also restart after update. The restart happened immediately after I connect to 5 GHz wifi. I have second USB wifi stick (for 2.4 GHz) that working correctly.

@jakubs2 Turris 1.0 neustálý restart při bootu z paměťovky (uSD karty)

Maybe another Turris 1.x brick

Odmítl jsem ve Forisu odloženou aktualizaci a právě jsem obdržel zprávu, že byla nainstalována. Děkuji.

Do we know root cause for loop-restarts ? So far users reported quite various “possible causes”, so i am not sure what-where should be checked/changed. Or is the rollback to 3.11.8 only solution ?

I had the same problem (Turris Omnia 1 GB), it disappeared after about 40 minutes (about 5-6 restarts).
Currently running version 3.11.9 for 2 days and 21 hours without problem.

Yeah, the post can’t be “empty”.

3 Likes

for me it worked without issues (omnia 1gb no wifi)