Custom firmware build for R7800 v. 1.0.2.38SF

[Voxel]

Continuation of

https://www.snbforums.com/threads/custom-firmware-build-for-r7800.36859/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-22sf.37222/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-23sf-v-1-0-2-24sf.37477/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-25sf-v-1-0-2-29sf.38032/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-30sf.38366/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-31sf.39142/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-32sf.39657/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-33sf.40198/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-34sf.40523/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-35sf.40794/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-36sf.41166/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-37sf.41317/

New version of my custom firmware build: 1.0.2.38SF.

Changes (vs 1.0.2.37SF):

1. OpenVPN is upgraded 2.4.3->2.4.4.
2. minidlna is upgraded 1.2.0->1.2.1.
3. sqlite package is upgraded 3190300->3200100.
4. libxml2 package is upgraded 2.9.5->2.9.6.
5. libubox ackage is upgraded 2017-06-17->2017-09-29.
6. uci package is upgraded 2017-04-12->2017-09-29.
7. util-linux package is upgraded 2.30.1->2.30.2.
8. curl package is upgraded 7.54.1->7.55.1.
9. libsodium package is upgraded 1.0.13->1.0.15.
10. dnscrypt-resolvers.csv is updated.
11. Host tools: mpfr is upgraded.
12. Toolchain: binutils is upgraded to version 2.29.1.
13. Samba user "root" is added (allows mapping drive with root permissions).
14. powerctl init script is changed.
15. Minor bug in dbus is fixed.
16. Experimental: -funsafe-math-optimizations option is added.

The link is:

https://www.voxel-firmware.com

No reset is needed to upgrade from my previous versions.


Voxel.

 

[pege63]

As allways

 

[Killhippie]

Does this version include the fix for the WPA2 Vulnerability in bridge mode ?

 

[Voxel]

Does this version include the fix for the WPA2 Vulnerability in bridge mode ?

Sorry, no. As I wrote this WPA2 vulnerability is inside drivers/pre-build modules from NETGEAR.

https://www.snbforums.com/threads/bridge-mode.41695/#post-353048

But there are other fixes of vulnerability (e.g. in OpenVPN) so it is better to close them right now and do not wait next release of stock FW from Netgear with WPA2 problem fix. NG releases stock firmware rather rarely...

Voxel.

 

[Killhippie]

Sorry, no. As I wrote this WPA2 vulnerability is inside drivers/pre-build modules from NETGEAR.

https://www.snbforums.com/threads/bridge-mode.41695/#post-353048

But there are other fixes of vulnerability (e.g. in OpenVPN) so it is better to close them right now and do not wait next release of stock FW from Netgear with WPA2 problem fix. NG releases stock firmware rather rarely...

Voxel.

Thanks Voxel. I just was wondering if you had advance access to a beta with the fix in it that's all. Anyway I totally agree with your what you say about the lax releases of firmware and thanks as always for your support.

 

[Voxel]

I just was wondering if you had advance access to a beta with the fix in it that's all.

Unfortunately I do not have any access to internals of NETGEAR developers. I do try (still) with a help of NETGEAR Guy to get real cooperation with them and NETGEAR, because (at least IMO) it is in interest of NETGEAR first of all. To improve their stock firmware. But still no any reaction and currently I am on the place of usual consumer of NETGEAR production, even not beta tester.

Voxel.

 

[rbird2]

Unfortunately I do not have any access to internals of NETGEAR developers. I do try (still) with a help of NETGEAR Guy to get real cooperation with them and NETGEAR, because (at least IMO) it is in interest of NETGEAR first of all. To improve their stock firmware. But still no any reaction and currently I am on the place of usual consumer of NETGEAR production, even not beta tester.

Voxel.

That is really to bad since Netgear is so slow in fixing bugs and implementing security updates.

If you browse the Netgear support forums, it's obvious that there are quite a few of their customers that feel the same way...

 

[janthony6]

Any update to the r9000?

 

[Voxel]

Any update to the r9000?

Under testing. Planned date of release: tomorrow, 24th of Oct.

Voxel.

 

[DC OB]

Question, i see cron is not install on the firmware. How could one run a scheduled script at a set time interval?

P.S. Thanks for your amazing work.

 

[cybrnook]

Question, i see cron is not install on the firmware. How could one run a scheduled script at a set time interval?

P.S. Thanks for your amazing work.

install entware, then install cron

 

[Razor512]

1.0.2.38SF is working pretty well, while write speeds are still lower than the stock firmware for some reason, it at least doesn't have that weird issue introduced in version 1.0.2.36 where I could not write files larger thn 2GB in size, and if you write a file that is 1KB over 2GB, it would seem to fully write the file with an error at the end, and while you could move the file and rename it, you could not delete it as it would complain that the file is in use.

Overall, storage is back to working reliably again.

 

[Supersaiyan_IV]

Any plans on link-time optimizations?
Eg. linker flags: -fuse-linker-plugin -flto
Or more aggressive: -fuse-linker-plugin -flto -finline-functions

If it fails on the linking stage due to missing references you can always try adding compile flags prior to linking: -fno-devirtualize -fno-early-inlining
There might be some unexpected gains to be had from interprocedural optimizations like this.

Great release!

 

[Voxel]

1.0.2.38SF is working pretty well, while write speeds are still lower than the stock firmware for some reason, it at least doesn't have that weird issue introduced in version 1.0.2.36 where I could not write files larger thn 2GB in size, and if you write a file that is 1KB over 2GB, it would seem to fully write the file with an error at the end, and while you could move the file and rename it, you could not delete it as it would complain that the file is in use.

Overall, storage is back to working reliably again.

I'll play more with Samba config to increase write speed. For next release. Now at least read speed is fast enough IMO . Faster than stock according to my benchmarks.

Voxel.

 

[Voxel]

Any plans on link-time optimizations?
Eg. linker flags: -fuse-linker-plugin -flto
Or more aggressive: -fuse-linker-plugin -flto -finline-functions

If it fails on the linking stage due to missing references you can always try adding compile flags prior to linking: -fno-devirtualize -fno-early-inlining
There might be some unexpected gains to be had from interprocedural optimizations like this.

Well, it is interesting. But I am not sure in success. OK, I'll try in background to play with LTO optimization. As far as I know LTO is more or less stable starting from 5.x gcc, but I have to use 4.8.5 to provide compatibility with pre-built by Netgear modules. Anyway, thanks for your comment.

Voxel.

 

[RMerlin]

I'll play more with Samba config to increase write speed.

If you're not doing it yet, look into experimenting with CPU affinity. Made a big difference on the RT-AC86U.

 

[deweyii]

Voxel,
Long time not reports. lol
In this new version vpn with android phone is not working again. had to go back to .37 for it to work.
Downloaded new file from page, still didn't work but same file still works with file downloaded from .38

as always thanks for the hard work.
Dewey

 

[deweyii]

Voxel,
Long time not reports. lol
In this new version vpn with android phone is not working again. had to go back to .37 for it to work.
Downloaded new file from page, still didn't work but same file still works with file downloaded from .38

as always thanks for the hard work.
Dewey

Standby on this. Seeing other issues need to test further. Seems to be happening on cell data not wifi

Sent from my SM-G950U using Tapatalk

 

[deweyii]

Standby on this. Seeing other issues need to test further. Seems to be happening on cell data not wifi

Sent from my SM-G950U using Tapatalk

Ok voxel,
After further testing it looks like it is writing the smartphone file wrong again. I know mine uses tun. I was able to get to work using an old smartphone file, that you fixed in a previous release. I must not have noticed it before, because I hadn't had to update the file on my phone, but I got a new phone and had to reload the file.

Thanks.

Sent from my SM-G950U using Tapatalk

 

[Voxel]

If you're not doing it yet, look into experimenting with CPU affinity. Made a big difference on the RT-AC86U.

OK, thank you for the tip.

Voxel.