TurrisOS 3.5 - Unsure of release day :-)

Just received from my Turris “Update of router Turris to Turris OS version 3.5 is planned for Thu January 11, 2017”

January 11 is today and, worse, it is not thursday :slight_smile:

So is the update today (Jan 11) or tomorrow (Thu)… Will see :grin:

it should be tomorrow probably. Received the same email in Czech and there is also same mistake.

I wonder whether the 3.5 version quailty is on par with this announcement’s one… I hope not but recent TO issues do not seem very convincing :confused:

1 Like

seems most of the updates come out on thursdays, and they generally give us 1 day notice, so i’d say expect it on thursday jan 12.

Where can I subscribe to this notifications? Checkbox “Send news” in foris is checked, but no email. thanks

1 Like

I’m interested as well - any way to get these announcements? I received no such mail and wouldn’t know where I need to opt in.

Unlike what I said, it is not sent by the Turris box but by the Turris organisation (you can find the announce on https://www.turris.cz/en/ ) I believe it is the “Email notifications” option in your settings https://www.turris.cz/en/settings/

2 Likes

Below in eMail there is:

You’re receiving this email because you have enabled sending of notifications from Turris website. You can disable sending of these emails on the settings page: https://www.turris.cz/en/settings/

so @bortzmeyer is right

FYI: It’s out, I just updated my omnia with updater.sh on the command line.

Hmm… Does that mean that Omnia users cannot subscribe? My account for omnia.turris.cz doesn’t work it seems.

You can subscribe with Omnia, but maybe you need to enable data collection, to be able to register there (I’m not sure).

My router just received the update and turned off both wifis. I’ve check ps and rebooted (didn’t have more time to investigate it properly). Looks like some scripts are stuck, but reboot fixed it.

ps:

PID USER VSZ STAT COMMAND
1 root 1340 S /sbin/procd
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
5 root 0 SW< [kworker/0:0H]
7 root 0 SW [rcu_sched]
8 root 0 SW [rcu_bh]
9 root 0 SW [migration/0]
10 root 0 SW [migration/1]
11 root 0 SW [ksoftirqd/1]
13 root 0 SW< [kworker/1:0H]
14 root 0 SW< [netns]
141 root 0 SW< [writeback]
143 root 0 SW< [crypto]
145 root 0 SW< [bioset]
147 root 0 SW< [kblockd]
187 root 0 SW [kswapd0]
188 root 0 SW< [vmstat]
189 root 0 SW [fsnotify_mark]
251 root 0 SW [spi0]
256 root 0 SW< [bioset]
261 root 0 SW< [bioset]
369 root 0 SW [irq/94-8-0071]
375 root 0 SW [irq/45-mmc0]
396 root 0 SW< [ipv6_addrconf]
401 root 0 SW< [bioset]
403 root 0 SW< [deferwq]
406 root 0 SW< [bioset]
408 root 0 SW [mmcqd/0]
409 root 0 SW< [bioset]
410 root 0 SW [mmcqd/0boot0]
412 root 0 SW< [bioset]
413 root 0 SW [mmcqd/0boot1]
414 root 0 SW< [bioset]
415 root 0 SW [mmcqd/0rpmb]
426 root 0 SW< [btrfs-worker]
428 root 0 SW< [btrfs-worker-hi]
429 root 0 SW< [btrfs-delalloc]
430 root 0 SW< [btrfs-flush_del]
431 root 0 SW< [btrfs-cache]
432 root 0 SW< [btrfs-submit]
433 root 0 SW< [btrfs-fixup]
434 root 0 SW< [btrfs-endio]
435 root 0 SW< [btrfs-endio-met]
436 root 0 SW< [btrfs-endio-met]
437 root 0 SW< [btrfs-endio-rai]
438 root 0 SW< [btrfs-endio-rep]
439 root 0 SW< [btrfs-rmw]
440 root 0 SW< [btrfs-endio-wri]
441 root 0 SW< [btrfs-freespace]
442 root 0 SW< [btrfs-delayed-m]
443 root 0 SW< [btrfs-readahead]
444 root 0 SW< [btrfs-qgroup-re]
445 root 0 SW< [btrfs-extent-re]
446 root 0 SW [btrfs-cleaner]
447 root 0 SW [btrfs-transacti]
448 root 0 SW< [kworker/0:1H]
450 root 0 SW< [kworker/1:1H]
470 root 0 SW [jfsIO]
471 root 0 SW [jfsCommit]
472 root 0 SW [jfsCommit]
473 root 0 SW [jfsSync]
476 root 0 SW< [xfsalloc]
477 root 0 SW< [xfs_mru_cache]
483 root 0 SW< [ata_sff]
510 root 0 SW [scsi_eh_0]
511 root 0 SW< [scsi_tmf_0]
514 root 0 SW [scsi_eh_1]
515 root 0 SW< [scsi_tmf_1]
791 root 812 S /sbin/ubusd
830 root 688 S /sbin/askfirst /bin/ash --login
863 root 0 SW [irq/41-f1090000]
867 root 0 SW [irq/42-f1090000]
946 root 0 SW< [md]
958 root 0 SW< [raid5wq]
974 root 0 SW< [kafs_vlupdated]
975 root 0 SW< [kafs_callbackd]
976 root 0 SW< [kafsd]
980 root 0 SW< [cifsiod]
989 root 0 SW< [rpciod]
1065 root 0 SW< [nfsiod]
1259 root 0 SW< [cfg80211]
1295 root 0 SW< [ath10k_wq]
1296 root 0 SW< [ath10k_aux_wq]
1320 root 3972 S /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf
1321 root 19332 S python /usr/bin/foris -s flup
1788 root 8464 S /usr/bin/nuci
1842 root 2808 S /usr/sbin/sshd -f /var/etc/ssh/sshd_config
1894 root 1872 S /sbin/rpcd
1958 root 6360 S {sfpswitch.py} /usr/bin/python /usr/sbin/sfpswitch.py --nodaemon
1979 root 1516 S /sbin/netifd
2009 root 2052 S < /usr/sbin/conntrackd -C /etc/conntrackd/conntrackd.conf
2190 nobody 764 S /usr/sbin/atd -f
2230 root 10416 S lcollect /tmp/lcollect
2440 root 1100 S /usr/sbin/odhcpd
2475 root 1480 S < /usr/sbin/ulogd -d
2576 root 26368 S ucollect /tmp/ucollect
2939 root 2000 S /usr/sbin/hostapd -P /var/run/wifi-phy1.pid -B /var/run/hostapd-phy1.conf
3402 root 1076 S udhcpc -p /var/run/udhcpc-eth1.pid -s /lib/netifd/dhcp.script -f -t 0 -i eth1 -C -O 212
3481 root 24692 S /usr/sbin/collectd
3512 root 908 S /sbin/mountd -f
3542 root 720 S odhcp6c -s /lib/netifd/dhcpv6.script -Ntry -P0 -t120 eth1
3555 root 736 S /usr/sbin/cron -n
3570 root 1728 S /usr/sbin/smartd -q never
3580 root 1080 S /usr/sbin/ntpd -n -S /usr/sbin/ntpd-hotplug -p 217.31.202.100 -p 195.113.144.201 -p 195.113.144.238 -p
5502 root 1268 S {dynamic_dns_upd} /bin/sh /usr/lib/ddns/dynamic_dns_updater.sh myddns_ipv4 0
5795 root 4304 S {syslog-ng} supervising syslog-ng
5796 root 4512 S /usr/sbin/syslog-ng
5797 root 1076 S /bin/sh -c /usr/share/ucollect/scripts/ucollect-add-firewall
5798 root 1076 S {ucollect-add-fi} /bin/sh /usr/share/ucollect/scripts/ucollect-add-firewall
6829 root 0 SW [kworker/0:0]
6924 nobody 896 S /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf -k -x /var/run/dnsmasq/dnsmasq.pid
6969 root 33108 S /usr/bin/kresd -c /tmp/kresd.config -f 1 /tmp/kresd -a 0.0.0.0 53 -a :: 53 -k /etc/root.keys
11455 root 0 SW [kworker/1:0]
15886 root 0 SW [kworker/0:2]
16537 root 0 SW [kworker/1:2]
19007 root 0 SW [kworker/1:1]
19270 root 704 S nethist
19676 root 1096 S sleep 600
20760 root 2836 R sshd: root@pts/0
20786 root 1096 S -ash
20862 root 1076 S sleep 3000
21797 root 0 SW< [kworker/u5:1]
22028 root 1092 R ps
22029 root 1092 S sh -c busybox nslookup 2a00:1450:400a:807::200c
22030 root 1092 R sh -c busybox nslookup 2a00:1450:400a:807::200c
23299 root 696 S /usr/sbin/ntpclient -i 600 -s -l -D -p 123 -h 0.openwrt.pool.ntp.org
23454 root 1244 S /usr/sbin/miniupnpd -f /var/etc/miniupnpd.conf
25839 root 0 SW [kworker/u4:5]
26555 root 2812 S socat STDIO OPENSSL:api.turris.cz:5679,cafile=/etc/ssl/ucollect-server.pem,cipher=HIGH:!LOW:!MEDIUM:!SS
27718 root 2000 S /usr/sbin/hostapd -P /var/run/wifi-phy0.pid -B /var/run/hostapd-phy0.conf
29395 root 0 SW< [kworker/u5:0]
30187 root 0 SW [kworker/u4:1]
30880 root 736 S /usr/sbin/cron -n
30885 root 1076 S /bin/sh -c majordomo_locked_precache.sh
30886 root 1076 S {majordomo_locke} /bin/sh /usr/bin/majordomo_locked_precache.sh
30889 root 736 S timeout 45m majordomo_cache.lua precache
30890 root 1916 S lua /usr/bin/majordomo_cache.lua precache
30891 root 0 Z [sh]
30892 root 0 Z [sh]
30894 root 0 Z [sh]

I got the email and updated. So far no issues. Hopefully WiFi will be more stable now.

Update was ok but now I have strange issue - in Foris in DNS I see DNS error, DNSSEC error - both forwarding and disable dnssec unticked. I can ping for example seznam.cz but can not nslookup same hostname.
When I enable forwarding - DNS is OK DNSSEC error. nslookup works.

Second strange issue is IPV6 check in same test - before update IPv6 connectivity OK, IPv6 gateway connectivity Error - as it should be in my understanding. After update IPv6 connectivity error - IPv6 gateway connectivity OK. I understoofd thas this case is not possible. I’m usin HE.net 6in4 tunnel. I do not have any custom DNS config - all is in default.
Anyone observed similar issue? Is there a way how to fix it quickly?

Other testimonies in this forum seem to indicate that 3.5 has a lot of problems :frowning:

Based on the available data we can not draw that conclusion, how many TO’s out of the total out there have a problem or problems updating to 3.5?
The TO is not your average router, it is a platform with different configurations and users modifying the underlying framework itself. Now, I am not saying this is user error. Do not get me wrong. The more moving parts there are in a system, the more that can go wrong. First, we and nic.cz, need to figure out why the update went good for most people and not good for others, than we can draw conclusions.

The TO is not your average router, it is a platform with different configurations

I’ve standard “out of box” configuration, and Omnia is ruined after last Update 3.5.

Geez @Radovan_Haban, why do you have such a complex setup? Way to ruin everything

/sarcasm

So if you keep everything stock an update can not go wrong? Unfortunately, s**t happens sometimes. Even with tested software/firmware. Bug free code does not exist (yet). Vorner is helping you in the other thread. Hopefully he can figure out why the update did go wrong and fix it and prevent it from happening in the future.