We have just released Turris OS 3.11.17 to the RC branch.
In this release you can find mitigations in unbound, knot-resolver, and bind for NXNSAttack. Each resolver has different CVEs and if you want to read more about this issue colleagues from Knot Resolver wrote an article about that. There are security fixes for samba4, krb5 and git.
There were updated a few packages as well. For example nextcloud, btrfs-progs, sentinel-dynfw-client and updater-ng.
TO 2GB, WiFi, simple config, unactive lxc, Ludus…
openwrt_version: 15.05
turris-version: 3.11.17, branch: rc
Update OK, reboot not required, rebooted anyhow.
Foris, LuCI didn’t load even after more than 15 mins,
Ludus loaded immediately (Win10 Pro actual, Chrome/Firefox actual)
SSH OK
On Android (Mi A1, Android 9) Ludus immediately, LuCI after more than 5 mins,
Foris never, SSH OK.
We are releasing an RC2 version of Turris OS 3.11.17.
We managed to fix the issue, which some of you met that Foris was not loading in particular cases. There is an improvement for IPv6 detection in init script fo Knot Resolver and while at it, we noticed that it was using the path for the old version of Knot Resolver, which is also fixed.
root@turris:~# tail -n 200 /var/log/messages | grep err
2020-06-02 08:24:28 err ATLAS[5579]: And we are done
2020-06-02 08:24:28 err ATLAS[5579]: unknown keyword ‘REG_WAIT_UNTIL’ in CON_INIT_CONF (1)
2020-06-02 08:24:30 err ATLAS[5579]: unknown keyword ‘REG_WAIT_UNTIL’ in CON_INIT_CONF (2)
2020-06-02 08:24:30 err ATLAS[5579]: cat: can’t open ‘known_hosts_controllers’: No such file or directory
2020-06-02 08:24:30 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt’ exists
2020-06-02 08:24:30 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/simpleping’ exists
2020-06-02 08:25:52 warning ucollect[15932]: epoll_wait on 4 interrupted, retry
2020-06-02 08:27:30 err ATLAS[5579]: enough space free, no need to do anything
2020-06-02 08:27:33 err ATLAS[5579]: And we are done
2020-06-02 08:27:33 err ATLAS[5579]: unknown keyword ‘REG_WAIT_UNTIL’ in CON_INIT_CONF (1)
2020-06-02 08:27:35 err ATLAS[5579]: unknown keyword ‘REG_WAIT_UNTIL’ in CON_INIT_CONF (2)
2020-06-02 08:27:35 err ATLAS[5579]: cat: can’t open ‘known_hosts_controllers’: No such file or directory
2020-06-02 08:27:35 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt’ exists
2020-06-02 08:27:35 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/simpleping’ exists
2020-06-02 08:28:22 info dnsmasq-dhcp[9312]: DHCPACK(br-lan) 10.0.0.30 b8:27:eb:dc:63:48 RaspberryPi
2020-06-02 08:28:22 info /dhcp_host_domain_ng.py: DHCP add new hostname [RaspberryPi,10.0.0.30]
2020-06-02 08:30:35 err ATLAS[5579]: enough space free, no need to do anything
2020-06-02 08:30:38 err ATLAS[5579]: And we are done
2020-06-02 08:30:38 err ATLAS[5579]: unknown keyword ‘REG_WAIT_UNTIL’ in CON_INIT_CONF (1)
2020-06-02 08:30:40 err ATLAS[5579]: unknown keyword ‘REG_WAIT_UNTIL’ in CON_INIT_CONF (2)
2020-06-02 08:30:40 err ATLAS[5579]: cat: can’t open ‘known_hosts_controllers’: No such file or directory
2020-06-02 08:30:40 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt’ exists
2020-06-02 08:30:40 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/simpleping’ exists
2020-06-02 08:33:40 err ATLAS[5579]: enough space free, no need to do anything
2020-06-02 08:33:43 err ATLAS[5579]: And we are done
2020-06-02 08:33:43 err ATLAS[5579]: unknown keyword ‘REG_WAIT_UNTIL’ in CON_INIT_CONF (1)
2020-06-02 08:33:45 err ATLAS[5579]: unknown keyword ‘REG_WAIT_UNTIL’ in CON_INIT_CONF (2)
2020-06-02 08:33:45 err ATLAS[5579]: cat: can’t open ‘known_hosts_controllers’: No such file or directory
2020-06-02 08:33:45 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt’ exists
2020-06-02 08:33:45 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/simpleping’ exists
2020-06-02 08:36:45 err ATLAS[5579]: enough space free, no need to do anything
2020-06-02 08:36:48 err ATLAS[5579]: And we are done
2020-06-02 08:36:48 err ATLAS[5579]: unknown keyword ‘REG_WAIT_UNTIL’ in CON_INIT_CONF (1)
2020-06-02 08:36:50 err ATLAS[5579]: unknown keyword ‘REG_WAIT_UNTIL’ in CON_INIT_CONF (2)
2020-06-02 08:36:50 err ATLAS[5579]: cat: can’t open ‘known_hosts_controllers’: No such file or directory
2020-06-02 08:36:50 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt’ exists
2020-06-02 08:36:50 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/simpleping’ exists
2020-06-02 08:39:14 err python3[7716]: ipset v6.24: Error in line 1: Element cannot be deleted from the set: it’s not added
2020-06-02 08:39:14 err python3[7716]: 2020-06-02 08:39:14,533 - WARNING - Error running ipset command: return code 1.
2020-06-02 08:39:29 err python3[7716]: ipset v6.24: Error in line 1: Element cannot be deleted from the set: it’s not added
2020-06-02 08:39:29 err python3[7716]: 2020-06-02 08:39:29,872 - WARNING - Error running ipset command: return code 1.
2020-06-02 08:39:44 err python3[7716]: ipset v6.24: Error in line 1: Element cannot be deleted from the set: it’s not added
2020-06-02 08:39:44 err python3[7716]: 2020-06-02 08:39:44,811 - WARNING - Error running ipset command: return code 1.
2020-06-02 08:39:50 err ATLAS[5579]: enough space free, no need to do anything
2020-06-02 08:39:54 err ATLAS[5579]: And we are done
2020-06-02 08:39:54 err ATLAS[5579]: unknown keyword ‘REG_WAIT_UNTIL’ in CON_INIT_CONF (1)
2020-06-02 08:39:55 err ATLAS[5579]: unknown keyword ‘REG_WAIT_UNTIL’ in CON_INIT_CONF (2)
2020-06-02 08:39:55 err ATLAS[5579]: cat: can’t open ‘known_hosts_controllers’: No such file or directory
2020-06-02 08:39:56 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt’ exists
2020-06-02 08:39:56 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/simpleping’ exists
2020-06-02 08:40:01 err python3[7716]: ipset v6.24: Error in line 1: Element cannot be deleted from the set: it’s not added
2020-06-02 08:40:01 err python3[7716]: 2020-06-02 08:40:01,451 - WARNING - Error running ipset command: return code 1.
2020-06-02 08:40:43 err python3[7716]: ipset v6.24: Error in line 1: Element cannot be deleted from the set: it’s not added
2020-06-02 08:40:43 err python3[7716]: 2020-06-02 08:40:43,959 - WARNING - Error running ipset command: return code 1.
2020-06-02 08:42:56 err ATLAS[5579]: enough space free, no need to do anything
2020-06-02 08:42:59 err ATLAS[5579]: And we are done
2020-06-02 08:42:59 err ATLAS[5579]: unknown keyword ‘REG_WAIT_UNTIL’ in CON_INIT_CONF (1)
2020-06-02 08:43:02 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt’ exists
2020-06-02 08:43:02 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/simpleping’ exists
2020-06-02 08:45:51 warning ucollect[15932]: epoll_wait on 4 interrupted, retry
2020-06-02 08:46:02 err ATLAS[5579]: enough space free, no need to do anything
2020-06-02 08:46:02 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt’ exists
2020-06-02 08:46:02 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/simpleping’ exists
2020-06-02 08:47:20 err foris-controller[6703]: WARNING:turrishw:unsupported model: TURRIS
2020-06-02 08:47:25 err foris-controller[5858]: Last message ‘WARNING:turrishw:uns’ repeated 1 times, suppressed by syslog-ng on turris
2020-06-02 08:47:25 err foris-controller[6703]: WARNING:turrishw:unsupported model: TURRIS
2020-06-02 08:47:30 err foris-controller[5858]: Last message ‘WARNING:turrishw:uns’ repeated 3 times, suppressed by syslog-ng on turris
2020-06-02 08:49:02 err ATLAS[5579]: enough space free, no need to do anything
2020-06-02 08:49:02 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt’ exists
2020-06-02 08:49:02 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/simpleping’ exists
2020-06-02 08:52:02 err ATLAS[5579]: enough space free, no need to do anything
2020-06-02 08:52:02 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt’ exists
2020-06-02 08:52:02 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/simpleping’ exists
2020-06-02 08:55:02 err ATLAS[5579]: enough space free, no need to do anything
2020-06-02 08:55:03 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt’ exists
2020-06-02 08:55:03 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/simpleping’ exists
2020-06-02 08:58:03 err ATLAS[5579]: enough space free, no need to do anything
2020-06-02 08:58:03 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/v6addr.txt’ exists
2020-06-02 08:58:03 err ATLAS[5579]: condmv: not moving, destination ‘/usr/libexec/atlas-probe-scripts/data/out/simpleping’ exists
I see some ipset errors and warnings related to it:
About RIPE atlas even with these errors which does not look good at the first insights. It is running and it is reported to server, right? Similar issue was reported in Turris OS 5.0 HBT thread (need to respond there), but there is a kind of different as we haven’t touch Atlas for 3 months in Turris OS 3.x. I am not saying that we are not looking into it but update for RIPE which fix most of the issues it is on review:
TO 2GB, WiFi, simple config, unactive lxc, Honeypot, Ludus, RIPE Atlas sw probe
Returned to TOS 3.11.16 via schnapps rollback, tried update via Foris (touching Save & update without any change), waiting for update to arrive for some time (maybe I had to wait more) I forced update via switch-branch rc… OK, reboot, and now in RC2 3.11.17 (Kernel version 4.4.199).
Foris & LuCI (all tabs), Ludus OK in Win10 Pro & Android, SSH OK.
Honeypot, Ludus, RIPE Atlas OK, running.
Released a new RC just now! What’s has been changed in RC3? There is just an updated RIPE Atlas SW Probe (+ add mention in release notes). Nothing else. Nothing more. As feedback isn’t bad, we will release it to everyone very soon once we hear some voices about the update of the RIPE Atlas probe, which should be smooth.
Otherwise before the update, Foris was dead, Luci super-slow. After the update both are okay.
But I wonder how they did get wrong before, because I have update approvals enabled and there was no approval request in the last 30 days. I am on hbs branch rc. And I’m pretty sure I used either Foris or Luci last month and they worked. Is there some part of the OS (except the dynamic firewall) that circuments the updater and gets updated “silently”? I did a schnapps diff with a snapshot from 3 weeks ago, and there were changed system files (note that this is before the manually triggered update from tonight):
The only thing I can think of is that I’d issue a manual pkgupdate before both update checks for RC1 AND RC2 occured and after they were released. It is possible I ran some manual pkgupdates, but it’d be a great coincidence to hit twice the RC release time window before my updater triggered an update approval request.
I see. It means that in Custom commands you have multiple buttons, which do the same. It is related if you have a resolver-debug package installed. But this is not a blocker for this release. We will improve it in future releases.