Custom firmware build for R9000 v. 1.0.2.47HF/1.0.2.47HF-HW

[Voxel]

Continuation of:

https://www.snbforums.com/threads/custom-firmware-build-for-r9000.40125/
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-v-1-0-2-41hf-1-0-2-41hf-hw.40481/
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-v-1-0-2-42hf-1-0-2-42hf-hw.40688/
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-v-1-0-2-43hf-1-0-2-43hf-hw.41167/
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-v-1-0-2-44hf-1-0-2-44hf-hw.41301/
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-v-1-0-2-45hf-1-0-2-45hf-hw.41820/
https://www.snbforums.com/threads/custom-firmware-build-for-r9000-v-1-0-2-46hf-1-0-2-46hf-hw.42223/

New version of my custom firmware build: 1.0.2.47HF/1.0.2.47HF-HW).

Changes (vs 1.0.2.46HF):
1. haveged package is added to feed the kernel entropy pool.
2. 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)​

3. ubus package is upgraded 2017-11-06->2017-11-13.
4. curl package is upgraded 7.56.1->7.57.0.
5. alsa-lib package is upgraded 1.1.4.1->1.1.5.
6. ReadyCLOUD version is downgraded 20170711->20170214 (problem reported by tech960).
7. default congestion control is changed to yeah, rmem_max/wmem_max values are increased.
8. dnscrypt-resolvers.csv is updated.
9. Several packages are optimized to minimize resulting size.

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.

Difference 1.0.2.47HF-HW vs 1.0.2.47HF: “HW” version means hardware acceleration of OpenSSL.

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.

 

[janthony6]

thank you

 

[Dinkler]

Hi Voxel - I recently purchased an R9000, and thank you for putting together this upgrade over stock software and for maintaining the R9000 in addition to the apparently more active R7800.

Anyway, have you considered adding an adblock package to your image? I'm coming from Linksys WRT1900ac and have used this package through Open-WRT: https://github.com/openwrt/packages/blob/master/net/adblock/files/README.md . Thank you for your work!

 

[Voxel]

Hi Voxel - I recently purchased an R9000, and thank you for putting together this upgrade over stock software and for maintaining the R9000 in addition to the apparently more active R7800.

Anyway, have you considered adding an adblock package to your image? I'm coming from Linksys WRT1900ac and have used this package through Open-WRT: https://github.com/openwrt/packages/blob/master/net/adblock/files/README.md . Thank you for your work!

You know, there was already such request. I prepared some ad-block solution based on privoxy from Entware. Please check this:

https://www.snbforums.com/threads/l...ear-r7800-like-ab-solution.40729/#post-342442

You need USB stick/disk for using this.

Voxel.

 

[Dinkler]

You know, there was already such request. I prepared some ad-block solution based on privoxy from Entware. Please check this:

https://www.snbforums.com/threads/l...ear-r7800-like-ab-solution.40729/#post-342442

You need USB stick/disk for using this.

Voxel.

Excellent. That thread has a few good ideas. Honestly I like the idea of using a proxy for adblocking - that way, in the unlikely event I want to load a URL that has been blocked, I drop the proxy for a minute. The R9000 has quite a bit of extra horsepower, and while I have a spare pi lying around (regarding the other thread's suggestion of routing through a pi for adblocking), I might as well use the horsepower in the router rather than introduce another piece of hardware (with additional latency).