Turris OS 3.11 in RC!

Ey N8v8r…This is not your average Cisco/Synology/whatever brand corp. Most of us supported the indy campaign. By doing that, you know there is no 300 + programmers.
My Turris Omnia runs perfect. It is by far the best piece of router i’ve ever had over the years. And i’m a nOOb.

If you want to burn it down , cause you think you are on top off all the most urgent issues, buy something else. Or even better, make your own.
i like this baby. I paid for it, and until now,they do deliver. Maybe not according to your time schedule. So be it. keep breathing.

my 2 cents.

7 Likes

Truly a delightful insight and eye opener, thank you! :star_struck:

Zjištěna chyba v odkazu ve Foris -> Cloud backups, kde je ve žlutém panelu uvedeno:

To be able to use cloud backups, please make sure that you are registered at the Project Turris portal. You can do that on the Data Collect tab. (Note that you don’t need to enable data collection after the registration.)

Ale odkaz “Data Collect tab” vede na adresu “<router_ip_address>/foris/config/main/data-collection/” a končí chybovou stránkou “404 (Not Found) - Unknown configuration page”

Správně má být odkaz směrován na “<router_ip_address>/foris/config/main/data_collect/” kde se skutečně příslušná konfigurační stránka nachází.

Hello @Nones,

Thank you for reporting this issue to us!
This issue is currently fixed in the nightly branch, and it will be included in the next RC version, which we’d like to release soon.

1 Like

I downloaded the todays morning turris nightly assembly of TurrisOS and the issue (incorrect link) wasn’t fixed there yet.

And the section Foris -> Cloud backups says: “Failed to download the list of backups” :frowning:
(nightly and prerc version too)

We have prepared a new RC version of Turris OS 3.11 containing a bunch of new version of some packages, new updates, fixed some bugs (for example that one mentioned by @Nones) and a lot of interesting things such updating NOR for all Turris 1.x owners.

Changelog

Highlights:

  • Turris 1.x: nor-update as it was described here: Update NOR na starém Turrisu
    Because we were testing it very intensively, we’ll highly appreciate, if somebody can try it out and then do the factory reset and let us know the feedback. So, we 'd avoid if any problems to be able to fix them before flashing it to everyone, who has Turris 1.x.

  • Turris Omnia: Knot Resolver updated to version 3.1.0,
    which should fix the issue mostly with domains hosted on IGNUM.
    Described here: DNS resolver dropouts (or hangs?)

Updated:

  • netdata to version 1.10.0, but we’ll update it once again to version 1.11.0
  • yara
  • tor
  • nextcloud
  • kernel
    and so on.

Added a new package: oor (OpenOverlayRouter)

We decided to release it even with one known issue, which is about LuCI and Wireguard, which is described here: Wireguard setup

2 Likes

Turris 1.x - no problem after update to Turris 3.11 (current RC) and factory resetting.

Good job, guys! :+1:

3 Likes

My nextcloud remains stuck in maintenance mode after the upgrade.
Does anyone know how to fix this, get it unstuck?

To answer myself here, I unstuck it by logging into my omnia with ssh as root and running:

sudo -u nobody /usr/bin/php-cli occ maintenance:mode --off
and then running the upgrade once again through the web interface.

Still interested in further feedback?
Today I switched to RC. I see following message in Syslog:

2018-11-16 10:55:08 err kernel[]: [    4.925154] cpu: dev_pm_opp_of_cpumask_add_table: couldn't find opp table for cpu:0, -19
2018-11-16 10:55:08 warning kernel[]: [   13.593729] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
2018-11-16 10:55:08 warning kernel[]: [   13.604461] ath10k_pci 0000:02:00.0: Falling back to user helper
2018-11-16 10:55:08 err kernel[]: [   13.614634] firmware ath10k!pre-cal-pci-0000:02:00.0.bin: firmware_loading_store: map pages failed
2018-11-16 10:55:08 warning kernel[]: [   13.623751] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
2018-11-16 10:55:08 warning kernel[]: [   13.634141] ath10k_pci 0000:02:00.0: Falling back to user helper
2018-11-16 10:55:08 err kernel[]: [   13.644138] firmware ath10k!cal-pci-0000:02:00.0.bin: firmware_loading_store: map pages failed
2018-11-16 10:55:08 info kernel[]: [   13.661029] ath10k_pci 0000:02:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043202ff sub 0000:0000
2018-11-16 10:55:08 info kernel[]: [   13.670305] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
2018-11-16 10:55:08 info kernel[]: [   13.679906] ath10k_pci 0000:02:00.0: firmware ver 10.2.4-1.0-00041 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 f43fa422
2018-11-16 10:55:08 warning kernel[]: [   13.724655] ath10k_pci 0000:02:00.0: board id is not exist in otp, ignore it
2018-11-16 10:55:08 warning kernel[]: [   13.731769] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA988X/hw2.0/board-2.bin failed with error -2
2018-11-16 10:55:08 warning kernel[]: [   13.742235] ath10k_pci 0000:02:00.0: Falling back to user helper
2018-11-16 10:55:08 err kernel[]: [   13.752323] firmware ath10k!QCA988X!hw2.0!board-2.bin: firmware_loading_store: map pages failed
2018-11-16 10:58:56 err foris-controller[2155]: WARNING:turrishw:unsupported TOS version (on omnia): 3
2018-11-16 10:59:01 err foris-controller[1776]: Last message 'WARNING:turrishw:uns' repeated 1 times, suppressed by syslog-ng on turrisOmnia

Otherwise everything seems to work fine.
Need any more details for investigation?

We have prepared and released another RC with small changes and improvements from the last RC.

Highlights:

  • DNS over TLS support for CZ.NIC ODVR DNS servers.

  • Foris-Pakon: UI polishing

  • Pakon: convert hostnames to lowercase

Package updates:

  • ddns-scripts

  • vim (if you’re interesting what I like on their latest version, you need to start vim and write :smile) :wink:

  • nor-update: solved the 2nd issue, which was described here: Update NOR na starém Turrisu

  • wireguard

  • minidlna

Security updates:

mbedtls, curl, mailman, isc-dhcp, mosquitto, bind, libmad, openocd

We have fixed previously known issue, which was about Wireguard and LuCI, and based on your request, we have added support for LTE modem Quectel EP09. We’d like to hear any feedback regarding this modem together, and it’s QMI interface.

So there are no known issues, yet.

please how do I trigger RC update and how do I determine what version of 3.11 RC is my Omnia runing?

Is this a correct messages?

INFO:End of subprogram output
ERROR:Subprogram output: /etc/updater/hook_postupdate/05_schnapps.sh:
Warning, could not drop caches
Warning, could not drop caches
parent transid verify failed on 2574843904 wanted 42475 found 42241
parent transid verify failed on 2574843904 wanted 42475 found 42241
Ignoring transid failure
leaf parent key incorrect 2574843904
Warning, could not drop caches

Hello,

First, you’d need to switch to RC via SSH in CLI using this command:

switch-branch rc

If you did it previously, your router should be updated automatically to the latest version or you can push it manually. There are two ways, how you can do update it manually.

  • Foris - Updater tab: click on Save changes without doing any change
  • In SSH run following command:
pkgupdate

Once, you’ll do it, you should be on the latest version including the RC.
Usually we bump kernel version and in this case, we don’t do it. You can check from the changelog, if there’s something updated and if you’re using it.

Hello @commar,

Do you have Turris 1.x, which you migrated to BTRFS?
MicroSD card looks ok otherwise? Enough free space?

If the answers are for both yes, it potentially looks like a corrupted file system. There might be a few ways, how you can repair it. The easiest way is to export the current snapshot using schnapps export to some external storage (e.g. USB flash drive) then do the factory reset and migrate to btrfs again. It’s recommended to use it together with formatting the microSD card. Then you can restore the backup up files using the schnapps import.

Anyway, it’s preferred to check the microSD card. Using the dd or badblocks.

Do you have Turris 1.x, which you migrated to BTRFS? Yes, yes
MicroSD card looks ok otherwise? Enough free space? Use 5% Yes

This time there is no reboot required? Or did I missed it?
Update: no hint :wink: Rebooting anyhow :wink:
U2: SFSG :slight_smile:

I’ve got little problem with that update, updater can’t find package mosquitto-client-nossl that I need for my router. And some time there are lines line not found in the log, but everything seems OK (except of mosquitto, of course).

root@TomasArouter:~# pkgupdate
WARN:Branch overriden to rc
WARN:Script file:///usr/share/updater/localrepo/localrepo.lua not found, but ignoring its absence as requested
WARN:Requested package luci-i18n-ddns-en that is missing, ignoring as requested.
WARN:Requested package luci-i18n-wshaper-cs that is missing, ignoring as requested.
WARN:Requested package luci-i18n-wshaper-en that is missing, ignoring as requested.
line not found
line not found
line not found
line not found
line not found
ERROR:
inconsistent: Requested package mosquitto-client-nossl that is not available.

Before this update i ran opkg update … I expect you ask that …

Hi,

Thanks for report. We were updating mosquitto due to security issue. I have checked it and indeed mosquitto packages somehow wasn’t compiled for Turris 1.x, while they’re compiled for Turris Omnia. I will see, if there’s anything what we can do.

# pkgupdate
WARN:Branch overriden to rc
WARN:Script file:///usr/share/updater/localrepo/localrepo.lua not found, but ignoring its absence as requested
WARN:Requested package luci-i18n-ddns-en that is missing, ignoring as requested.
INFO:Queue install of libcurl/turris/7.62.0-1
INFO:Queue install of resolver-conf/turris/0.0.1-26
INFO:Queue install of curl/turris/7.62.0-1
INFO:Queue install of bind-libs/turris/9.11.5-1
INFO:Queue install of bind-client/turris/9.11.5-1
INFO:Queue install of bind-dig/turris/9.11.5-1
INFO:Queue install of luci-proto-ipv6/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-proto-ppp/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-app-firewall/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-theme-bootstrap/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-lib-jsonc/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-lib-ip/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-lib-nixio/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-base/turris/git-18.318.25640-ae2537d-10
INFO:Queue install of luci-mod-admin-full/turris/git-18.318.25640-ae2537d-3
INFO:Queue install of luci/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of python3-turrishw/turris/0.4-3.6-1
INFO:Queue install of vim-full/turris/8.1-1
INFO:Queue install of luci-app-commands/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-base-en/turris/git-18.318.25640-ae2537d-10
INFO:Queue install of luci-i18n-commands-en/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-base-de/turris/git-18.318.25640-ae2537d-10
INFO:Queue install of luci-i18n-commands-de/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of ddns-scripts/turris/2.7.8-7
INFO:Queue install of luci-proto-3g/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-app-hd-idle/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of minidlna/turris/1.2.1-3
INFO:Queue install of luci-app-minidlna/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-app-samba/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-hd-idle-en/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-minidlna-en/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-samba-en/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-hd-idle-de/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-minidlna-de/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-samba-de/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-app-ahcp/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-app-mjpg-streamer/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-app-statistics/turris/git-18.318.25640-ae2537d-4
INFO:Queue install of luci-app-tinyproxy/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-app-transmission/turris/git-18.318.25640-ae2537d-2
INFO:Queue install of luci-app-upnp/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-app-wol/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-proto-openconnect/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-proto-relay/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-ahcp-en/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-firewall-en/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-statistics-en/turris/git-18.318.25640-ae2537d-4
INFO:Queue install of luci-i18n-tinyproxy-en/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-transmission-en/turris/git-18.318.25640-ae2537d-2
INFO:Queue install of luci-i18n-upnp-en/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-wol-en/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-ahcp-de/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-firewall-de/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-statistics-de/turris/git-18.318.25640-ae2537d-4
INFO:Queue install of luci-i18n-tinyproxy-de/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-transmission-de/turris/git-18.318.25640-ae2537d-2
INFO:Queue install of luci-i18n-upnp-de/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-wol-de/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-app-openvpn/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of luci-i18n-openvpn-de/turris/git-18.318.25640-ae2537d-1
INFO:Queue install of ddns-scripts_nsupdate/turris/2.7.8-7
INFO:Queue install of ddns-scripts_no-ip_com/turris/2.7.8-7
INFO:Queue install of bind-server/turris/9.11.5-1
INFO:Queue install of bind-tools/turris/9.11.5-1
INFO:Queue install of bind-rndc/turris/9.11.5-1
INFO:Queue install of bind-dnssec/turris/9.11.5-1
INFO:Queue install of bind-check/turris/9.11.5-1
Press return to continue, CTRL+C to abort

INFO:Executing preupdate hooks...
INFO:Subprogram output: /etc/updater/hook_preupdate/05_schnapps.sh:
Snapshot number 108 created

INFO:End of subprogram output
INFO:Unpacking download packages
INFO:Checking for file collisions between packages
line not found
line not found
line not found
line not found
line not found
line not found
DIE:
[string "transaction"]:323: [string "transaction"]:149: Collisions:
• /usr/sbin/named-checkconf: bind-check (existing-file), bind-tools (new-file)
• /usr/sbin/rndc-confgen: bind-tools (new-file), bind-rndc (existing-file)
• /usr/sbin/dnssec-keygen: bind-tools (new-file), bind-dnssec (existing-file)
• /usr/sbin/dnssec-settime: bind-tools (new-file), bind-dnssec (existing-file)
• /usr/sbin/rndc: bind-tools (new-file), bind-rndc (existing-file)
• /usr/sbin/named-checkzone: bind-check (existing-file), bind-tools (new-file)
• /usr/bin/dig: bind-tools (existing-file), bind-dig (new-file)
• /usr/sbin/dnssec-signzone: bind-tools (new-file), bind-dnssec (existing-file)
Aborted

Update over foris also fails:

Error from 2018/11/20 00:56:27

Updater selhal:

[string "transaction"]:323: [string "transaction"]:149: Collisions:

• /usr/sbin/named-checkconf: bind-check (existing-file), bind-tools (new-file)

• /usr/sbin/rndc-confgen: bind-tools (new-file), bind-rndc (existing-file)

• /usr/sbin/dnssec-keygen: bind-tools (new-file), bind-dnssec (existing-file)

• /usr/sbin/dnssec-settime: bind-tools (new-file), bind-dnssec (existing-file)

• /usr/sbin/rndc: bind-tools (new-file), bind-rndc (existing-file)

• /usr/sbin/named-checkzone: bind-check (existing-file), bind-tools (new-file)

• /usr/bin/dig: bind-dig (new-file), bind-tools (existing-file)

• /usr/sbin/dnssec-signzone: bind-tools (new-file), bind-dnssec (existing-file)