Turris OS 7.0 is out!

Turris 1.1, simple config without wifi - VLANs, guest network, OpenVPN, Samba, MiniDLNA, SQM, DNS over TLS.
The upgrade took place without any major problems. After the first reboot everything ran without any problem. But after a few hours I noticed that reForis stopped working. Unfortunately, I did not copy the error message that appeared in the browser. But since the next restart, the problem has not repeated.
Thank you and hats off to the whole Turris team.
The only thing I noticed, and it is still the same problem in my case that I already confided during the upgrade to version 6.5.1, is that the factory image did not update, even though I have checked ‘Latest firmware’ and ‘Factory image’ in Packages in reForis for a long time.
And schnapps pretends not to know what it’s running on.

root@turris254:~# schnapps factory-version
5.3.0
root@turris254:~# schnapps update-factory
Don't know what device I am, can't update my factory image

Maybe that’s why it did nothing. What could it be? According to the log I recorded during the upgrade, 96_firmware_updater was executed.

2 Likes

Today I tried transmission-daemon 4.0.4 in the HBL branch and the problem with connecting to the tracker still persists.

@miska Is anyone working on the issue?

1 Like

The problem I was looking at is high load when transmission is running. Does that improve with 4.04?

What kind of problem with connection to a tracker do you experience?

On turris 1.x, the problem is that you can’t connect to any tracker or peer (it keeps saying connecting) + high cpu load.
No, transmission-daemon 4.0.4 doesn’t solve the problem.

I think these package lists only work on Omnia so far. Not sure it is mentioned anywhere…

It is mentioned in the code:

And there later in the code if board not schnapps so mox/omnia then proceed with update

Edit: change is comming😆

Wireguard is functional after the upgrade,
but the Luci web ui is not working for wireguard

You have to configure it via cli/ssh,
which is annoying.

Could someone please fix this.

1 Like

Problem with connection to trackers is valid for Omnia too on HBS. I didn´t noticed high cpu load, but I was trying it only for few minutes.

Thank you, this will be fixed in one of the upcoming releases.

So far our investigaions into transmission revealed, that downloading via magnet links is broken, but if you download torrent file manually and upload it to transmission, it works. Regarding 100% CPU usage, in some tests, disabling uPnP and uTP helped (--no-portmap and --no-utp cmdline options). But not all the time, we are looking into it, but so far no luck.

2 Likes

I cannot confirm this, because I am using torrent files and not magnet links.

What exactly is not working in the webui for you? I can create new interface/peers as well as see the wireguard connection status.

I have same problem…

This has helped me since the heavy load

But still unable to connect anywhere.
Torrent downloaded and added manually and transmission still reports:
Announce is queued

Is downgrading back to 3.x an option? It worked 100% fine. Since v4 is a major rewrite, there might be too many bugs to figure out (for us anyway)…

1 Like

I suspect my crashes are somewhat RTC related… I noticed my logs are not in “chronological order”

logs are showing timeshifitng.

failing signature verification - i experienced the same on my MOX when doing a fresh usb flash installation today… signature check failed when loading the packages list.
my “quick n dirty” workaround was switching to hbt branch. then the signature check passed.

on my omnia, i didn´t have this issue, but i upgraded from 6 to 7 and didn´t do a completely fresh installation…

Mine (Omnia AP upgraded some time ago during the delayed update time) went just fine. Upgrade->Reboot all is working.

Mine (Main Omnia router went fine as well) but be sure to not to use new DHCP options. In 22.03 new instances options for each interface dont work. So this update fixed some old bugs but introduced new ones probabbly fixed in 23.03 already.

Time will tell. Thank you Turris team. The upgrade went smooth. At least for me.

Hi @pete,

we tried with @miska to find some bug why it is not working, but without success still. Some torrents works, some not. Sometimes it works with copied url, sometimes not and works only from uploaded torrent file… really weird behaviour. Last what we didn’t try is downgrade…I will try to downgrade it to v3 and let you know. If transmission works on v3. we will send it to the next version as temp. solution.

3 Likes

Happy to help with testing, if needed.

2 Likes