Turris OS 3.6 out now

After update:

/etc/init.d/lighttpd restart
2017-03-09 20:21:33: (server.c.1295) WARNING: unknown config-key: setenv.set-environment (ignored)

opkg list | grep lighttp
lighttpd - 1.4.45-1 - A flexible and lightweight web server
lighttpd-mod-access - 1.4.45-1 - Access restrictions module
lighttpd-mod-accesslog - 1.4.45-1 - Access logging module
lighttpd-mod-alias - 1.4.45-1 - Directory alias module
lighttpd-mod-auth - 1.4.45-1 - Authentication module
lighttpd-mod-cgi - 1.4.45-1 - CGI module
lighttpd-mod-cml - 1.4.45-1 - Cache Meta Language module
lighttpd-mod-compress - 1.4.45-1 - Compress output module
lighttpd-mod-evasive - 1.4.45-1 - Evasive module
lighttpd-mod-evhost - 1.4.45-1 - Exnhanced Virtual-Hosting module
lighttpd-mod-expire - 1.4.45-1 - Expire module
lighttpd-mod-extforward - 1.4.45-1 - Extract client module
lighttpd-mod-fastcgi - 1.4.45-1 - FastCGI module
lighttpd-mod-flv_streaming - 1.4.45-1 - FLV streaming module
lighttpd-mod-magnet - 1.4.45-1 - Magnet module
lighttpd-mod-proxy - 1.4.45-1 - Proxy module
lighttpd-mod-redirect - 1.4.45-1 - URL redirection module
lighttpd-mod-rewrite - 1.4.45-1 - URL rewriting module
lighttpd-mod-rrdtool - 1.4.45-1 - RRDtool module
lighttpd-mod-scgi - 1.4.45-1 - SCGI module
lighttpd-mod-secdownload - 1.4.45-1 - Secure and fast download module
lighttpd-mod-setenv - 1.4.45-1 - Environment variable setting module
lighttpd-mod-simple_vhost - 1.4.45-1 - Simple virtual hosting module
lighttpd-mod-ssi - 1.4.45-1 - SSI module
lighttpd-mod-status - 1.4.45-1 - Server status display module
lighttpd-mod-trigger_b4_dl - 1.4.45-1 - Trigger before download module
lighttpd-mod-userdir - 1.4.45-1 - User directory module
lighttpd-mod-usertrack - 1.4.45-1 - User tracking module
lighttpd-mod-webdav - 1.4.45-1 - WebDAV module

ls -la /etc/lighttpd/modules.d
drwxr-xr-x    1 root     root           106 Mar  9 19:55 .
drwxr-xr-x    1 root     root            74 Mar  9 19:55 ..
-rw-r--r--    1 root     root            34 Mar  3 10:05 30-alias.load
-rw-r--r--    1 root     root            32 Mar  3 10:05 30-cgi.load
-rw-r--r--    1 root     root            36 Mar  3 10:05 30-fastcgi.load
-rw-r--r--    1 root     root            35 Mar  3 10:05 30-setenv.load

Then I dont know, what these means:

2017-03-09T19:14:10+01:00 warning []: Missing message-id in rpc-reply.
2017-03-09T20:14:18+01:00 warning []: Last message 'Missing message-id i' repeated 3 times, supressed by syslog-ng on Router
2017-03-09T19:14:30+01:00 warning []: Missing message-id in rpc-reply.
2017-03-09T20:14:35+01:00 warning []: Last message 'Missing message-id i' repeated 2 times, supressed by syslog-ng on Router
2017-03-09T19:21:33+01:00 err []: Input channel closed
2017-03-09T19:21:33+01:00 err []: Module communication error: Broken message recieved
2017-03-09T19:21:33+01:00 err []: nc_session_send_reply: Invalid <rpc> message to answer.

I think they wasnt present there @3.5.2

After the update my graphs donā€™t work. I have set the path to the RRDTool files and I can see an old data but there are no new data. Collectd settings has one big problem, those files on that picture arenā€™t there (deleted or what?). I havenā€™t changed anything. So what to do to repair it?

Jsou tam jen cesty k něčemu, co neexistuje. MĆ”m nightly ā€¦

This is working for me: copy content from dh2048.pem to dh-default,pem

1 Like

Hi, majordomo seems to be broken. There is file ā€˜ucollect_majordomoā€™ in /tmp. But no /tmp/majordomo_db is created. Till update majordomo was related to lcollect. Did I missed something?
Thx, Karel

I know that this change is working. This was report for TO team to fix.

Go to LuCi >>> System >>> Software
Click update package lists and once that is done, type ā€œsuricataā€ in the box behind ā€œFilter:ā€ and click ā€œfind packageā€.
Click on the "Available packages (suricata) tab and below an install button should appear. Click it and enjoy.

Hi all,
after upgrade & reboot - I donā€™t see any new OpenVPN setup in Forris. I have Turris 1.

Is this supported only for Omnia?

SOLVED: I had to install foris-openvpn-plugin package via Luci.

Thanks

Hi,
on turris it bailed out with
Updater selhal:
inconsistent: Requested package knot-nsec3hash that is not available.

after removing

Updater selhal:
inconsistent: Requested package luci-app-lxc that is not available.

after removing

Updater selhal:
[string ā€œtransactionā€]:311: [string ā€œtransactionā€]:144: Collisions:
ā€¢ /etc/iproute2/rt_tables: ip-full (new), ip (new)
ā€¢ /usr/sbin/ip: ip-full (new), ip (new)

now forcefully installed ip-full over ip and the update is running only removing every trace of lxc

NFO:Queue removal of mount-utils
INFO:Queue removal of lsblk
INFO:Queue removal of getopt
INFO:Queue removal of libmount
INFO:Queue removal of ethtool
INFO:Queue removal of rpcd-mod-lxc
INFO:Queue removal of cfdisk
INFO:Queue removal of lxc-create
INFO:Queue removal of lxc-common
INFO:Queue removal of liblxc
INFO:Queue removal of lxc-hooks
INFO:Queue removal of lxc-templates
INFO:Queue removal of flock
INFO:Queue removal of gnupg-utils
INFO:Queue removal of gnupg
INFO:Queue removal of lxc-configs
INFO:Queue removal of lxc
INFO:Executing preupdate hooksā€¦

and installation is now successful

After updated to 3.6 wifi cards wonā€™t come up anymore. Was working perfectly before that. Was rock stable. Rebooted 3-4 times but both LEDS for Wi-Fi were dark. Interestingly the wifi1 (2,4 ghz) was still listed in ifconfig and also shown as network even if LEDs were dark, didnā€™t try to connect though. Lspci shows both cards were detected so thatā€™s not the problem. I know reverted using schnapps, rebooted and Wi-Fi works like a charm.

Should I now say: Oops you did it again? I mean we already had that whole shit with Wi-Fi problems and every single time you update the firmware it breaks horribly given all the posts that already accumulated here and I really havenā€™t configured something very special on the router.

You guys really need to get this firmware issue sorted. I mean you seem to have different stages like nighties etc but you still break the router with every single upgrade, how can that be?

I really thought that now you got the message, but no. Itā€™s another disastrous release. And Iā€™m really close to sell the really good hardware because of you guys seeming incapable of releasing working firmware.

You know what was one of the key features during the indiegogo campaign? Automatic updates so your router is always secure. But so far the automatic updates are just doing one thing: break your router. At least we have schnapps to go back if everything starts breaking again. And after you fixed 3.6 before next release: test, test, test, test, test and when you think everything is fine. Test again at least 3-4 times. Build a beta tester group work to test with devices from different countries or whatever but get your firmwares under control!

Custom Commands were also wiped in LUCI after the update

After update statistics graphs configuration in the Forris has been wiped. Really I donā€™t know why you have to break Turris functionality after each update. I have also device from Synology and itā€™s completely different storyā€¦

Also statistics data sending to CZ-NIC is broken after updateā€¦

1 Like

for now is great solution :slight_smile: thanks so much

  1. edit /etc/config/openvpn
  2. change dh ā€˜/etc/dhparam/dh-default.pemā€™ to dh ā€˜/etc/dhparam/dh4096.pemā€™
  3. /etc/init.d/openvpn restart

It works for me.

Iā€™m very surprised that CZ.NIC didnā€™t test itā€¦ :frowning:

Is there an easy (not through full FW reset) way to revert to version 3.5.3? I did not found it.
Why there are new versions every few weeks? Border router / firewall has to be rock solid device. Those broken updates are not doing good work for users. Why not to have a new version every 2-3 months? And hotfix in the case of serious security problem. Tested and solid. In this state, the only solution is to disable automatic updates. And thus main reason for buying Omnia is goneā€¦

Everything works great. Thank you for the update.
(just to counter those who come here and cry instead of selling the stuff they dont like)

1 Like

I fixed the cron problem by creating a symlink:
ln -s /etc/cron.d /etc/crontabs
and (re)starting cron.

1 Like

Thanks a lot! It works for me. I am not very skillful in linux enviroment, so it was for me unsolvable problemā€¦

1 Like

Personally I have just root file (script contains users custom services there) on /etc/crontabs/root, and in /etc/cron.d/ I have system services ā€œcronnedā€. Its not the same thingā€¦

I finally have IPv6 working correctly with this version, after a last tweak to my configuration.