Turris OS 3.7 out now! Guest wi-fi, syslog-ng and more included

Thank you for your bug report.

Looks like there is some problem with building transmission-web package. We will fix it soon, in the meantime, you can remove the package and use remote client-e.g. transmission desktop apps. Without the package, the updater should finish successfully.

In my case it works after the OS3.7 upgrade without any issues. I am using for the 802.11ac network the wifi module R11e-5HacT, which has a QCA9880 chip.

1 Like

You’re welcome, @cynerd, and thank you for your reply.

This is my /etc/config/updater (but I installed nikola manually after it was uninstalled?)

config pkglists ‘pkglists’
list lists ‘openvpn’
list lists ‘netutils’
list lists ‘shell-utils’
list lists ‘cacerts’
list lists ‘api-token’
list lists ‘printserver’
list lists ‘nas’
list lists ‘majordomo’
list lists ‘luci-controls’
list lists ‘honeypot’
list lists ‘automation’
list lists ‘i_agree_datacollect’

config override ‘override’

config l10n ‘l10n’
list langs ‘cs’

And now there’s different issue WiFi issue.
When I’m trying connect to my WiFi network it says: ‘Obtaining IP address…’, but that’s it.

2017-06-26T18:37:15+02:00 info hostapd: wlan0: STA 0c:89:10:7d:ef:0d IEEE 802.11: authenticated
2017-06-26T18:37:15+02:00 info hostapd: wlan0: STA 0c:89:10:7d:ef:0d IEEE 802.11: associated (aid 1)
2017-06-26T18:37:23+02:00 info hostapd: wlan0: STA 0c:89:10:7d:ef:0d IEEE 802.11: authenticated
2017-06-26T18:37:23+02:00 info hostapd: wlan0: STA 0c:89:10:7d:ef:0d IEEE 802.11: associated (aid 1)
2017-06-26T18:37:30+02:00 info hostapd: wlan0: STA 0c:89:10:7d:ef:0d IEEE 802.11: authenticated
2017-06-26T18:37:30+02:00 info hostapd: wlan0: STA 0c:89:10:7d:ef:0d IEEE 802.11: associated (aid 1)

// EDIT:
I deleted my WiFi network in luci. Then I tried also opkg update and then updater and reboot router. Setup new WiFI wiki and works. Finally.

hi there, saw the message on twitter. Did a updater.sh ( took a while ) and everything works like a charm ! Thnxs!

Hi there…i have the same error, but for example the VPN still works? It just removed some language packages, DE and CS.

Error notifications

Updater failed: Failed operations:
foris-openvpn-plugin-l10n-cs/postrm: + [ -n ]

foris-tls-plugin-l10n-cs/postrm: + [ -n ]

foris-diagnostics-plugin-l10n-cs/postrm: + [ -n ]

foris-diagnostics-plugin-l10n-de/postrm: + [ -n ]

foris-openvpn-plugin-l10n-de/postrm: + [ -n ]

foris-tls-plugin-l10n-de/postrm: + [ -n ]

Update notifications

• Removed package foris-tls-plugin-l10n-de
• Removed package foris-tls-plugin-l10n-cs
• Removed package foris-diagnostics-plugin-l10n-de
• Removed package foris-openvpn-plugin-l10n-de
• Removed package foris-l10n-de
• Removed package foris-diagnostics-plugin-l10n-cs
• Removed package foris-openvpn-plugin-l10n-cs
• Removed package foris-l10n-cs

I have a problem after update to TurrisOS 3.7 with run my own html page on lighttpd.
I have the right path to my “index.html” file in “server.document-root” section of “lighttpd.conf” file, but every request to my homepage (on the router IP address) is redirected to /foris/ page

@DIKKEHENK and @RadoslavCap please see my post.

1 Like

yep, thanx. Since everything worked fine, i did not bother… :slight_smile:

You have to edit forris config in lighttpd, but right now I will not tell you where exactly is it, because I am not yet updated.
On my 3.6.5 it is in script placed /usr/share/foris/lighttpd-dynamic-conf here you have to look for redirecting rule. In my case look like this: \"(?(?<!/)/|)(?!static|cgi-bin|luci-static|plugins|local)\" This rule say what is excluded from redirecting to Forris.

Thanks, but I dont know what I have doing.
This is the file from TurrisOS 3.7 and there is the same one from older version TurrisOS 3.6.5

Solved :
This is not error of update - issue was with my syslog-ng.conf file which caused syslog-ng to fail start and as result no file /var/log/messages was created after restart.

I have had 2 times section internal() in sources which caused this issue

LuCI System Log is not working after update and showing following error :

500 Internal Server Error</h2>
<p>Sorry, the server encountered an unexpected error.</p>
<pre class="error500">/usr/lib/lua/luci/dispatcher.lua:460: Failed to execute call dispatcher target for entry '/admin/status/syslog'.
The called action terminated with an exception:
/usr/lib/lua/luci/template.lua:97: Failed to execute template 'admin_status/syslog'.
A runtime error occured: [string "/usr/lib/lua/luci/view/admin_status/syslog...."]:1: attempt to index global 'syslog' (a nil value)
stack traceback:
	[C]: in function 'assert'
	/usr/lib/lua/luci/dispatcher.lua:460: in function 'dispatch'
	/usr/lib/lua/luci/dispatcher.lua:141: in function </usr/lib/lua/luci/dispatcher.lua:140></pre>

I have got the same, even run from CLI:

root@turris:~# updater.sh
WARN:Script revision-specific not found, but ignoring its absence as requested
WARN:Script serial-specific not found, but ignoring its absence as requested
DIE:
inconsistent: Package uhttpd-mod-tls requires package libustream-polarssl that is not available.
root@turris:~#

1 Like

Well I have no plan to update yet, I am not at home and cant risk that something will go wrong - and now, if you are right, I have another reason to not update, as I need path in lighttpd to boot live image of fedora.
From the given source I can say Good luck, it is probably buried in somewhere in the Foris python app.

1 Like

Great, I have an error more or less each update.

Error from 2017/06/26 15:21:19
Updater failed:
inconsistent: Package luci-ssl requires package libustream-polarssl that is not available.
1 Like

Hi,

Updater failed:
inconsistent: Requested package transmission-web that is not available.

See this post:
https://forum.test.turris.cz/t/turris-os-3-7-out-now-guest-wi-fi-syslog-ng-and-more-included/4423/22?u=pepe

Several small, annoying bugs here. I don’t yet use my Omnia in “production”, because the OS’s reliability is unfortunately not on par with my old Routerstation Pro. So when I read about 3.7, I turned it on and the update was automatic. Results:

  1. The LEDs don’t turn to my colours and reduced brightness during the boot process, only after a while. I don’t like the blinding white Gestapolicht.

  2. I have my own resolver setup which uses DNSmasq partly. However, the update simply turned it off. This is simply unacceptable. DO NOT TOUCH THE CONFIGURATION!!!

@14/etc/config/dhcp 2017-06-25 15:23:42.978506173 +0200
+++ @15/etc/config/dhcp 2017-06-26 22:48:49.380000000 +0200
@@ -11,13 +11,13 @@
option leasefile '/tmp/dhcp.leases’
option sequential_ip '1’
option filterwin2k ‘1’

  • option port '53’
    option nonwildcard '1’
    option local '/my.home.domain/'
    option domain 'my.home.domain’
    option localservice '0’
    list notinterface 'guest’
    option resolvfile ‘/etc/resolv.conf_upstream’
  • option port ‘0’

(Meh, seems like preformatting does not work correctly in the preview.)

  1. The mail sending did not work. I just simply got this:
Error notifications

Updater failed: Missing CRL, possibly broken Internet connection.

  1. Lighttpd became unresponsive after a while. I could not find anything in the logs. A restart solved this problem. But I experienced this a couple of times even before 3.7.

Can we please have the Omnia diffs merged back to stock OpenWRT ASAP, so power users can have a clean installation without the problems caused by automation? I made a snapshot after the update, so it was easy to diff what had changed (as you can see above).

Edit: well, not only the preformatting did not work, but the forum engine screws up the numbering, too. Mail sending should be 3 and Lighttpd should be 4.

1 Like

And some more. I ticked off the support for Czech and German in Foris and got this mail shortly after:

Error notifications

Updater failed: Failed operations:
foris-openvpn-plugin-l10n-cs/postrm: + [ -n ]

foris-tls-plugin-l10n-cs/postrm: + [ -n ]

foris-diagnostics-plugin-l10n-cs/postrm: + [ -n ]

foris-tls-plugin-l10n-de/postrm: + [ -n ]

foris-openvpn-plugin-l10n-de/postrm: + [ -n ]

foris-diagnostics-plugin-l10n-de/postrm: + [ -n ]

Update notifications

• Removed package foris-openvpn-plugin-l10n-de
• Removed package foris-openvpn-plugin-l10n-cs
• Removed package foris-tls-plugin-l10n-de
• Removed package foris-tls-plugin-l10n-cs
• Removed package foris-diagnostics-plugin-l10n-de
• Removed package foris-diagnostics-plugin-l10n-cs
• Removed package foris-l10n-cs
• Removed package foris-l10n-de

Regarding to 1st post and bug number no. 2:

To yours 2nd post: This is already reported and it will be fixed soon