Turris OS 6.4.3 is released!

[nano]

@bamf

omnia-mcutool --upgrade

What are the changes? Updated Uboot version?

[bamf]

Releases · Turris / HardWare / omnia_hw_ctrl · GitLab

[nano]

The (besides various fixes) would nice to understand. What various fixes?

[Big_boss]

Turris Omnia v2020 (v6.4.2 → v6.4.3)

• Everything works fine. I did had at first some problems with MiniUPNPD. It was not working. I implemented a different solution this time and now it works again.

Solution to upnp not working

• WiFi (2.4 Ghz, 5 Ghz)
• mSATA SSD
• LXC
• VLAN, Zones
• DDNS (Duckdns.org)

[miska]

@tk1

My 3G modem was already configured, so automatically adding the GSM network device is not wanted on my end (despite all good intentions from your end :)). Would be better to check for an existing device or rather offer a wizard that folks can trigger manually.

Can you share your configuration prior installation? We detect if modem was already configured, but obviously we haven’t detected your configuration, so it would be interesting to know how was it configured (and ideally the firewall configuration too) so we can fix it. Sharing relevant parts of /etc/config/network and /etc/config/firewall should be enough.

[tk1]

Sure, much appreciate you guys looking into this!

config/network:

config interface 'lte'
        option proto '3g'
        option device '/dev/ttyUSB2'
        option service 'umts'
        option apn 'portalmmm.nl'
        option pincode '0000'
        option ipv6 'auto'
        option defaultroute '0'
        option username 'root'
        option password '<pwd>'
        option auto '0'

config route 'lte_route'
        option interface 'lte'
        option target '0.0.0.0'
        option gateway '10.64.64.64'
        option netmask '0.0.0.0'
        option metric '50'

firewall:

config zone
        option conntrack '1'
        option name 'wan'
        option input 'REJECT'
        option output 'ACCEPT'
        option forward 'REJECT'
        option masq '1'
        option mtu_fix '1'
        option network 'wan wan6 LTE lte'
        option sentinel_dynfw '1'
        option sentinel_fwlogs '1'

Hope this helps?

Have a good weekend!

[Starouscz]

I think there might be a regresssion in this or one of the previous sevices related to /srv or storage plugin.

When there is a bug in /srv service the notification in the service fails due to incorrect flag

I reported same issue i think in march and it was supposed to be fixed

[Leonardo]

With the new Nextcloud update, I got this error:

• Your remote address was identified as “192.168.1.101” and is bruteforce throttled at the moment slowing down the performance of various requests. If the remote address is not your address this can be an indication that a proxy is not configured correctly. Further information can be found in the documentation .

Bruteforce throttled after 27.1.0-beta 3

It may be caused by installing Nextcloud on a router.

[Biosko]

6.4.2 → 6.4.3

size of snapshots in schnapps is no longer visible to me (not visible in reforis, not visible via console)

root@router:/usr/share/resolver# schnapps list
    # | Type      | Size        | Date                      | Description
------+-----------+-------------+---------------------------+------------------------------------
    7 | pre       |             | 2023-02-06 02:24:50 +0100 | Automatic pre-update snapshot (TurrisOS 6.2.2 - )
    8 | post      |             | 2023-02-06 02:25:27 +0100 | Automatic post-update snapshot (TurrisOS 6.2.3 - hbs)
   13 | pre       |             | 2023-03-11 04:39:45 +0100 | Automatic pre-update snapshot (TurrisOS 6.2.3 - hbs)
   14 | post      |             | 2023-03-11 04:40:15 +0100 | Automatic post-update snapshot (TurrisOS 6.2.4 - hbs)
   29 | pre       |             | 2023-06-16 10:53:43 +0200 | Automatic pre-update snapshot (TurrisOS 6.2.4 - hbs)
   30 | post      |             | 2023-06-16 10:55:05 +0200 | Automatic post-update snapshot (TurrisOS 6.3.3 - hbs)
   31 | pre       |             | 2023-06-16 13:07:22 +0200 | Automatic pre-update snapshot (TurrisOS 6.3.3 - hbs)
   32 | post      |             | 2023-06-16 13:07:25 +0200 | Automatic post-update snapshot (TurrisOS 6.3.3 - hbs)
   45 | pre       |             | 2023-09-05 02:43:18 +0200 | Automatic pre-update snapshot (TurrisOS 6.3.3 - hbs)
   46 | post      |             | 2023-09-05 02:44:12 +0200 | Automatic post-update snapshot (TurrisOS 6.4.2 - hbs)
   48 | time      |             | 2023-09-17 01:05:01 +0200 | Snapshot created by cron
   49 | time      |             | 2023-09-24 01:05:01 +0200 | Snapshot created by cron
   50 | time      |             | 2023-10-01 01:05:01 +0200 | Snapshot created by cron
   51 | time      |             | 2023-10-08 01:05:01 +0200 | Snapshot created by cron
   52 | time      |             | 2023-10-15 01:05:01 +0200 | Snapshot created by cron
   53 | pre       |             | 2023-10-15 19:22:32 +0200 | Automatic pre-update snapshot (TurrisOS 6.4.2 - hbs)
   54 | post      |             | 2023-10-15 19:23:42 +0200 | Automatic post-update snapshot (TurrisOS 6.4.3 - hbs)

[Skippi]

Pokud to správně chápu, tak velikost se zjišťuje přes příkaz btrfs qgroup show, který velikost ukazuje:

root@turris:~# btrfs qgroup show /
Qgroupid Referenced Exclusive Path

---

0/5 8.00KiB 8.00KiB
0/258 97.21MiB 5.80MiB @factory
0/262 97.20MiB 5.79MiB @5
0/263 97.20MiB 5.79MiB @6


[ssdnvv]

Same for me.
Automatic update for MOX (A(SDIO)B(WLE1216v5-20)D(2,5GBE)) worked fine, no issues besides the missing snapshots sizes.

[ljelinek]

The output format of btrfs qgroup show has been changed. It has been already fixed in schnapps: Adapt to new quota output (f110a8c2) · Commits · Turris / schnapps · GitLab

[bamf]

@miska

That is the idea. We will write up something about it in few days with a short howto.

Is there any update on this?