Just to be clear, why we are reluctant to do it. There are configuration changes in hostapd and to support them we would also have to pull latest netifd and because of that latest luci and latest dependencies of those packages. The format of those packages with Lede project were changed so they are incompatible. This pretty much is not pull two packages but pull around few hundreds of them and rewrite their makefiles while breaking rest of the system. Pretty much impossible. The way we are currently approaching it is to have 4.0 ready as soon as possible instead of sinking hundreds of hours in to the dying fork. I am not saying that I am happy that we have old packages in our repository but we have to see bigger picture.
Understood. But just to be clear about the user story (although that doesn’t change anything from your point of view): it’s not just about updating old packages (like you stated on gitlab) but about missing functionality and security fixes!
That is all well and appreciated but the issue is only that TOS4.x is repeatedly cited/advertised as being the cure whilst it is still in the alpha stage and there are only vague hints that it may arrive production ready till end of this year, implying uncertainty that this will be achieved.
Almost 1 year ago it was stated that TOS4.x would be eventually in beta by end of 2018.
Certainly the dev team is doing as best as they can but that developers have departed and not being replaced, plus at the same time adding the MOX workload, in all likelihood has not aided the pace of development and the consequence is that users ultimately paying the price as being a in limbo between out of date core components with the LEDE repo and some alpha state that is still facing all king of issues on its own in the TOS4.x trunk.
Have some developers left the team?
Can the latest version of nextcloud 16 be packaged for tos?
Yes, Nextcloud 16 will be in Turris OS after some testing.
Nextcloud 16.0.1 will be included in upcoming 3.11.5 and also in Turris OS 4.0 - beta2.
Hello! Is there a chance to release new kernel version?
Tere is critical bug: CVE-2019-11477
Bad packet (with low mss) can cause kernel panic remotely.
Almost there Turris OS 3.11.5 RC is out!
We just released the final version of Turris OS 3.11.5, where is included a newer version kernel, which fixes the CVE and 2 more.
Feel free to use my package: http://shulyaka.org.ru/pub/gcc_4.8.3-2_mvebu.ipk
And if you are as concerned about security as you probably should be, you can build your own package using this: http://shulyaka.org.ru/pub/gcc.tar.gz
Hello Dennis, thank you, but my turris is not omnia (arm architecture) but original turris 1.0 (powerpcspe architecture) which is the problem as nowadays almost nothing new works on old powerpcspe architecture and even debian dropped support for it altogether. Will try compile from makefile you provided, but I doubt compilation will succeed.
openwrt /data # opkg install ./gcc_4.8.3-2_mvebu.ipk
Unknown package ‘gcc’.
- pkg_hash_fetch_best_installation_candidate: Packages for gcc found, but incompatible with the architectures configured
- opkg_install_cmd: Cannot install package gcc.
Sorry, I forgot to ask if you have Omnia.
However I believe the makefile should still work, but probably it would require some efforts from you
Well I tried to compile current gcc from openwrt and it failed, yours is 4.8, older version, will try to compile later but there are so many problems with compiling for powerpcspe that I doubt that even older version will compile successfully.
Please update to include
ovpn file upload feature within OpenWRT 19.07
This is included already in Turris OS 4.0, which is based on top of OpenWrt 18.06. If you want to give it try, you can. See Turris OS 4.0 beta5 is out!
Changes from @dibdot about luci-app-openvpn was backported to Turris OS 3.x, but these changes are not included in OpenWrt 18.06 (Turris OS 4.x). It’s up to @dibdot if he wants to backport it and support it also in OpenWrt 18.06. Otherwise, it is already included in OpenWrt 19.07 (Turris OS 5.x).
If you are interested in uploading multiple .opvn files at once in LuCI, we are not going to include changes by githubrobbi. First, it needs to be included in OpenWrt, but it’s using Excel. There is no way that this can be merged to OpenWrt. If you would like to see it, you will need to change the source code of LuCI, which will be more user-friendly than forcing users to use SSH, Excel and using .bas file.