What's new

Custom firmware build for R7800 v. 1.0.2.43SF

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Voxel

Part of the Furniture
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/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-38sf.41751/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-39sf.41945/
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-40sf-1-0-2-41sf.42222/

New version of my custom firmware build: 1.0.2.43SF.

Changes (vs 1.0.2.41SF):

1. Integration of changes from the latest stock v. 1.0.2.38.
2. Correction of new bugs in the stock 1.0.2.38.
* Bug in WebGUI: BASIC->ReadySHARE->ReadyCLOUD (404 page not found).
* Bug in WebGUI: ADVANCED->ReadySHARE->Media Server (iTunes server control exists, but package itself is removed).
* avahi service: lack of adisk.service template.
* etc. (several repeated in each release of stock firmware)​
3. forked-daapd package (iTunes Server) is removed, the same removal as in the stock 1.0.2.38.
4. libconfuse, libmxml, libantlr3c, libplist, libasound are removed (were used solely by forked-daapd, not needed now).
5. haveged package is added to feed the kernel entropy pool.
6. QoS: redis server/client package is upgraded 2.6.13->2.6.17 (i.e. to latest stable 2.6.x), its memory management scheme is changed.
7. OpenSSL is upgraded 1.0.2m->1.0.2n. Major changes (OpenSSL changelog):
Read/write after SSL object in error state (CVE-2017-3737)
rsaz_1024_mul_avx2 overflow bug on x86_64 (CVE-2017-3738)​
8. ubus package is upgraded 2017-11-06->2017-11-13.
9. ffmpeg package is upgraded 0.11.2->3.2.9.
10. curl package is upgraded 7.56.1->7.57.0.
11. default congestion control is changed back to yeah, rmem_max/wmem_max values are increased.
12. dnscrypt-resolvers.csv is updated.
13. Several additional packages are optimized to minimize resulting size.

Thanks to Jeanmi and Tommaso for their help in testing beta version.
Also thanks to e38BimmerFN for testing ookla speed test from firmware.

The link is:

https://www.voxel-firmware.com (thanks to vladlenas for his help with hosting).

No reset is needed to upgrade from my previous versions.

P.S.
This version does not include the fix for the WPA2 Vulnerability in bridge mode (the last is not released by NETGEAR yet).


Voxel.
 
Hello Voxel. Thanks for your efforts here. I've got some major issue with 43F build. My provider uses L2TP connection type. Whenever I update firmware on router to 43F it never connects with provider, 41F have no issues with connection however. Could you, please, look into that?
 
Hello Voxel. Thanks for your efforts here. I've got some major issue with 43F build. My provider uses L2TP connection type. Whenever I update firmware on router to 43F it never connects with provider, 41F have no issues with connection however. Could you, please, look into that?
You know, it is difficult for me to check all connection types: I have just one, Ethernet cable.

Could you check first if this problems exists with stock 1.0.2.38? Probably there is a bug in stock, and I integrated changes into my version. To have info: is it 1.0.2.38 specific or not.

Voxel.
 
You know, it is difficult for me to check all connection types: I have just one, Ethernet cable.

Could you check first if this problems exists with stock 1.0.2.38? Probably there is a bug in stock, and I integrated changes into my version. To have info: is it 1.0.2.38 specific or not.

Voxel.
Will do tonight. Will report back asap. Thanks!
Update.
Checked Netgear 1.0.2.38. Indeed that's the firmware bug. Tried resetting router and enter all username and password stuff manually. Didn't help. Will wait for next release, I guess.
Thanks anyway Voxel!
 
Last edited:
Checked Netgear 1.0.2.38. Indeed that's the firmware bug. Tried resetting router and enter all username and password stuff manually. Didn't help. Will wait for next release, I guess.
Thanks anyway Voxel!

Well, it is difficult for me to remove all bugs from the stock fw. Part of it is pre-compiled, so if I correct open part, it may spoil enclosed part. It would be good if you report your problems with stock firmware (L2TP) to official NETGEAR forum, to NETGEAR Guy here and of course to NETGEAR support (https://my.netgear.com). There are at least several visible bugs in current stock (GUI) so it would be better if they add you problem to their "to-do" list. Releases of stock firmware are not often event, so better to report them bug ringing all the bells.

Voxel.
 
Last edited:
I've migrated to v43SF and now have the 7800 online as main host router. With out any other devices online accept for one wired PC, onboard speed test result is the following for a 200/10:
Latest test result (16:36 Dec 13, 2017)
download.png
DOWNLOAD
upload.png
UPLOAD
158.60
Mbps 10.66Mbps

telnet:
root@R7800:/$ ookla --configurl=http://www.speedtest.net/api/embed/trial/config.php
serverid: 8182
latency: 58
upload: 10141
download: 161946

speedtest.net reports similar:


I'll do some more testing since it's early evening here.
 
Voxel, thanks for the update.
Unfortunately, the update makes my local wired network perform much worse, so I rolled back to .41sf and all was normal again.
After the update, I could not log back in to the router. Only when using a different browser, I finally could log in.
Also, file browsing on my NAS became much slower. Before, the contents of a directory on the NAS would be show instantly (.41sf). After the update, it took several seconds before the contents was shown.

Internet browsing/downloading doesn't seem affected.
 
Unfortunately, the update makes my local wired network perform much worse, so I rolled back to .41sf and all was normal again.
After the update, I could not log back in to the router. Only when using a different browser, I finally could log in.
Also, file browsing on my NAS became much slower. Before, the contents of a directory on the NAS would be show instantly (.41sf). After the update, it took several seconds before the contents was shown.

Well, I am not sure. Maybe integration of stock 1.0.2.38 was a mistake (it has several bugs). Try to do reset after upgrade.

Guys, who has something similar please let me know. Probably it has sense to revert to previous state (w/o 1.0.2.38 changes).

Voxel.
 
Will do tonight. Will report back asap. Thanks!
Update.
Checked Netgear 1.0.2.38. Indeed that's the firmware bug. Tried resetting router and enter all username and password stuff manually. Didn't help. Will wait for next release, I guess.
Thanks anyway Voxel!

I would wait until VOX gets a .40 based FW out, as that is Netgears latest for this router...
 
I would wait until VOX gets a .40 based FW out, as that is Netgears latest for this router...

I do not think it has a sense.

1. L2TP is not fixed in 1.0.2.40:

No L2TP fix in .40 firmware. Already sent notice to Netgear Guy about that.

2. Yet new bugs are introduced:

https://www.snbforums.com/threads/netgear-firmware-update-for-x4s-r7800-1-0-2-40.42724/#post-364447

3. Mabe most important: NETGEAR developers not always publish GPL code. If you check:

https://kb.netgear.com/2649/NETGEAR-Open-Source-Code-for-Programmers-GPL

there are no codes for 1.0.2.40 (and BTW for 1.0.2.36 too).

Voxel.
 
I'm still not seeing to spec QoS speeds with the speedtest.net with in the QoS UI, though better than 41, from 130s not to 160s with v43SF. Both onboard, telnet and in a web browser are the same in speed results.

I need to test again and go back to v.30 and see if the speeds are same or better.
 
I'm still not seeing to spec QoS speeds with the speedtest.net with in the QoS UI, though better than 41, from 130s not to 160s with v43SF. Both onboard, telnet and in a web browser are the same in speed results.

I need to test again and go back to v.30 and see if the speeds are same or better.

Probably you case a bit more specific. As you can see AntonK do not have speed degradation for his desktop:

https://www.snbforums.com/threads/netgear-x4s-r7800-guest-wifi-problem.42777/#post-364969

ookla test in router WebGUI could be problematic. But it is pre-compiled binary I do not handle.

Well, maybe I'll pass you some changed files for test to copy into firmware. To make it identical to 1.0.2.30SF (if your tests are better for 1.0.2.30SF). In P.M. But please check anyway 30SF vs 43SF for your router and connection.

Voxel.
 
Ok. I'll revert back to v30SF and re-test and report my findings.
Thank you again. ;)
 
Here is the results after loading v30SF back on to the router, factory reset and set up from scratch.
I disabled the db update and experience check boxes before testing.
Latest test result (14:43 Dec 17, 2017)
DOWNLOAD UPLOAD
231.88
Mbps 10.80Mbps

In Browser:


After enabling QoS db update and reboot:
Latest test result (15:01 Dec 17, 2017)
DOWNLOAD UPLOAD
231.98
Mbps 10.88Mbps

In Broswer:
 
I can connect to the router with Putty, but not with FileZilla even though it's configured to use the keys. The error is "Received unexpected end-of-file from SFTP server" and I think it's got something to do with a lack of sftp support by Dropbear. Can anyone confirm?

One other question. I added a crontab entry to perform a wget in order to keep my Dynamic DNS up to date from freedns.afraid.org. I have it send its output to a logfile in tmp and don't think it's running. The file never appears.
 
Last edited:

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top