Turris OS 4.0.2 is released into HBT - Testing branch

Nothing has changed. Mox is not working …

root@turris:~# netboot-manager regen -f
Regenerating configuration...
Getting new rootfs...
Downloading 'https://repo.turris.cz/hbs/netboot/mox-netboot-latest.tar.gz'
Connecting to 217.31.192.69:443
Writing to '/srv/turris-netboot/rootfs/rootfs-new.tar.gz'
/srv/turris-netboot/ 100% |*******************************| 42066k  0:00:00 ETA
Download completed (43075675 bytes)
Downloading 'https://repo.turris.cz/hbs/netboot/mox-netboot-latest.tar.gz.sha256'
Connecting to 217.31.192.69:443
Writing to '/srv/turris-netboot/rootfs/rootfs-new.tar.gz.sha256'
/srv/turris-netboot/ 100% |*******************************|    98   0:00:00 ETA
Download completed (98 bytes)
Downloading 'https://repo.turris.cz/hbs/netboot/mox-netboot-latest.tar.gz.sig'
Connecting to 217.31.192.69:443
Writing to '/srv/turris-netboot/rootfs/rootfs-new.tar.gz.sig'
/srv/turris-netboot/ 100% |*******************************|   151   0:00:00 ETA
Download completed (151 bytes)
rootfs-new.tar.gz: OK
Cannot open file '/etc/opkg/keys//xxxxxxxxxxxxx' for reading
Tampered tarball

Same as under 4.0.1 … Post here

After I updated to 4.0.X I just have a bricked mox, which get not listed over netboot-manager or elsewhere …

I realy need soon a solution for my problems withs netbooting MOX. 6 Month ago I received my “early bird MOX”. Under 3.11 I got him running after some investigations, but just for a week or two, then I had to make a factoryreset again to get him back online. Then I installed 4.0.x, because I hoped it will get better, but the result was, that he doesn´t work at all in the moment.

Hello there, running TurrisOS 4.0.2 99fcf8f / LuCI branch (git-19.305.00515-5a05075) on a Mox classic, and was wondering why adblock is working, but not loading the lists anymore. It does all work, but the result is 0. This is since a week or so?

Nov 8 07:18:11 turrisMOX adblock-3.5.5-2[29132]: blocklist with overall 0 domains loaded successfully (CZ.NIC Turris Mox Board, TurrisOS 4.0.2 99fcf8f/4.0.2)

best, DIKKE

znovu vyzkoušeno a funguje do té doby než uživatel ručně nainstaluje balíček wget, pkgupdate následně odstraní balíček wget a nahradí ho balíčkem wget-nossl

There were some changes for netboot tarball itself, but it is going to be fixed only when we release Turris OS 4.0.2 from Testing branch into Stable branch (hbs). As you can see in your output it downloads the tarball from hbs branch. If you would like in the meantime you can modify the source code of netboot (/etc/bin/netboot-manager) to download it from hbt, but those changes will be overridden by the update.

Ok, I would like to try it out till next update. What exactly I have to do?

Je tohle dostupné už i pro turris 1.x ? TOS 4.0.1 (turris1x-medkit-latest.tar.gz) jsem zkoušel a updater mi skončil na nedustopnosti balíku kmod-mmc-fsl-p2020

Thank you, opkg remove wget-nossl resolved the fact opkg update was failing with the same error you quoted in your post. Also as mentioned above, the package will re-install itself with the next update unless you do something like this:

echo -e '\nUninstall("wget-nossl")' >> /etc/updater/conf.d/example.lua; pkgupdate

I stumbled upon that too recently. Try installing full wget

opkg install wget

wget package got removed from TOS base image at some point and unfortunately busybox’s wget doesn’t implement all command line options. I guess @dibdot should be notified as well and perhaps correct me if I am wrong.

Is TOS 4.x shipped with uclient-fetch plus ssl lib? If so, you can simply switch/select that one in adblock for blocklist downloads.

1 Like

Ahhh, thxs! the uclient -fetch Works. The opkg install wget gives errors

Vývojáři pracují na tom, aby byla verze Turris OS 4.x+ dostupná také pro routery Turris 1.0 a Turris 1.1. Ačkoliv je v tuto chvíli možné nainstalovat Turris OS 4.x podle návodu, který byl zde zveřejněný v jiném vlákně, tak je pouze pro velmi zkušené uživatelé a není oficiálně podporovaný tedy mohou se objevit chyby a v některých případech je také možné, že může být potřeba sériová konzole.

Jakmile budeme spokojeni s podporou Turris OS 4.0+ na modrých routerech Turris, tak vám o tom dáme určitě vědět.

1 Like

Today, we have released another RC version of Turris OS 4.0.2.

Changes between RC1 and this version:

  • based on OpenWrt 18.06.05
  • mariadb: updated to version 10.4.10, fix CVE-2019-2974, CVE-2019-2938
  • luci-compat, lmdb: new packages
  • foris: netboot fix
  • acme: updated to version 2.8.3
  • kernel: updated to version 4.14.152
  • enable some packages for Turris 1.x

Fixed known issue:

  • package perl-device-usb is now available for all of our routers.
2 Likes

V této verzi (MOX) konečně začala fungovat vzdálená správa (přístup na dálku) ve Forisu prostřednictvím Omnie (Turris OS 3.11.8). Po mnoha verzích, kde vždy blikalo černé kolečko s občasným zobrazením otazníku nebo vykřičníku, bylo konečně možné touto cestou nastavit wi-fi síť.

Následně spojení přestalo znovu fungovat, ale to vyřešila ruční změna IP adresy v souboru “/etc/config/fosquitto”. Po nastavení wi-fi totiž MOX změnil svou MAC adresu a DHCP server Omnie mu přidělil IP novou. V příslušném souboru ale zůstala ta stará.

Prosím proto o opravu nebo informaci, že je v 3.11.9 RC již vyřešeno (tuto verzi jsem záměrně na Omnii nezkoušel, protože router používám v produkčním prostředí).

This time better! Simplest config (WiFi only - MOX will be used mainly as WiFi extender for Omnia :wink: all seems working.

Turris 4.0.2 hbk showed me several updates today (see below). After installing and then rebooting the Omnia goes into a reboot loop… Tried it twice. Wen’t back with the “2 LED” reset to the last working snapshot. Anybody else has the same issue?

> INFO:Queue install of base-files/core/194.2-da835bf.0
> 
> INFO:Queue install of kernel/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-cfg80211/core/4.14.154+2017-11-01-10-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-mac80211/core/4.14.154+2017-11-01-10-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ath/core/4.14.154+2017-11-01-10-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ath9k-common/core/4.14.154+2017-11-01-10-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ath9k/core/4.14.154+2017-11-01-10-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ath10k/core/4.14.154+2017-11-01-10-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-nf-conntrack/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-nf-flow/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-nf-ipt/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-nf-reject/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ipt-core/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ipt-offload/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-nf-nat/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-nf-nathelper/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-br-netfilter/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-nls-base/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-usb-core/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-usb-ehci/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-usb2/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-libphy/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-swconfig/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-switch-mvsw61xx/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-usb-serial/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-usb-serial-wwan/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-usb-serial-qualcomm/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-i2c-core/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-gpio-pca953x/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-i2c-mux/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-i2c-mux-pca954x/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-nvmem/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-eeprom-at24/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ledtrig-default-on/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ledtrig-gpio/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ledtrig-heartbeat/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ledtrig-netdev/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ledtrig-oneshot/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ledtrig-timer/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ledtrig-transient/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of omnia-support/turrispackages/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ipt-nat/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-nf-conntrack6/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ipt-conntrack/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ebtables/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-nfnetlink/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-nf-conntrack-netlink/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ipt-ipset/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-lib-crc-ccitt/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-slhc/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ppp/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-pppox/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-pppoe/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-sched-core/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-nf-ipt6/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-nf-reject6/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ip6tables/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of luci-proto-ipv6/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-proto-ppp/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-app-firewall/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-theme-bootstrap/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-lib-jsonc/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-lib-ip/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-lib-nixio/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-base/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-mod-admin-full/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-base-en/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-base-de/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-app-commands/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-commands-en/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-commands-de/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of kmod-ipt-conntrack-extra/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ipt-ipopt/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ifb/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-sched-cake/core/4.14.154+2019-01-08-331ac70c-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-iptunnel6/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-ip6-tunnel/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-iptunnel4/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-iptunnel/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-sit/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-tun/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of luci-app-ahcp/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-ahcp-en/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-ahcp-de/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-app-adblock/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-app-bcp38/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-firewall-en/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-firewall-de/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of kmod-input-core/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of kmod-sound-core/core/4.14.154-1-0a66bb0316b4402bf65555c64ceed313.0
> 
> INFO:Queue install of luci-app-minidlna/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-minidlna-en/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-minidlna-de/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-app-mjpg-streamer/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-app-statistics/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-statistics-en/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-statistics-de/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-app-tinyproxy/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-tinyproxy-en/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-tinyproxy-de/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-app-transmission/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-transmission-en/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-transmission-de/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-app-upnp/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-upnp-en/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-i18n-upnp-de/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-proto-openconnect/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-proto-relay/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-proto-vpnc/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-compat/luci/git-19.323.55987-448dd8e-1.0
> 
> INFO:Queue install of luci-app-openvpn/luci/git-19.323.55987-448dd8e-1.0
> 
> Press return to continue, CTRL+C to abort

Thanks for your work!

Do you have ETA when it will appear in stable brunch?

Just to let you know. I’m still waiting for the stable branch, BUT the new version you released two days ago, I lost the menu-item " Managed Devices" completly in foris. Reinstall “MOX Netboot” makes no difference and shows no errors.

Thank you for your question. According to my details, there’s going to be one more RC release before we can release it. We would like to have in this release supported Turris 1.0 and Turris 1.1 routers, but it was tough due to some bug in the upstream kernel and we are getting closer to have supported for booting from microSD card. In the meantime, we are working on fixing the second known bug mentioned in the 2nd post, polishing the release and also bring you more interesting things in the upcoming releases.

2 Likes

I found out was was causing the issue for me updating in 4.0.2 causing the reboot loop. I rolled back to 4.0.1 before hbk branch and tried to switch to “hbk branch” again. The update always hangs at “INFO:Running postinst of ddns-scripts”. After rolling back to 4.0.1 and uninstalling ddns scripts the update went without problems. Is there an issue with ddns-scripts and 4.0.2?

There is something wrong happening with package ddns-scripts. You might want to wait a little bit until it timeout and the update will proceed further.

For more details you can take a look at this issue: