Custom firmware build for R7800 v. 1.0.2.40SF & 1.0.2.41SF

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

Voxel

Very Senior Member
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/

New version of my custom firmware build: 1.0.2.40SF.

Changes (vs 1.0.2.39SF):
1. OpenSSL is upgraded 1.0.2l->1.0.2m. Fixes (OpenSSL changelog):
* bn_sqrx8x_internal carry bug on x86_64 (CVE-2017-3736).
* Malformed X.509 IPAddressFamily could cause OOB read (CVE-2017-3735).
2. Changes in OpenVPN client:
* "--cd $OPENVPN_CONF_DIR" option is added to startup script.
3. ReadyCLOUD is upgraded 20161026->20170914, startup/upgrade script is optimized.
4. redis package (client/server) is upgraded 2.6.13->4.0.2 (used in QoS).
5. libubox package is upgraded 2017-09-29->2017-10-06.
6. ubus package is upgraded 2017-02-18->2017-11-06.
7. libxml package is upgraded 2.9.6->2.9.7.
8. sqlite package is upgraded 3200100->3210000.
9. expat package is upgraded 2.2.4->2.2.5.
10. Several packages are optimized to decrease resulting size.

Update (recovering problem with QoS)

New version of my custom firmware build: 1.0.2.41SF.

Changes (vs 1.0.2.40SF):
1. redis package (client/server) revert back 4.0.2->2.6.13 (used in QoS).

(thanks to Mark Eagles and Jeanmi for reporting bug).

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.
 
Last edited:

Mark Eagles

Occasional Visitor
Nice work.
Upgraded but all info on QoS has gone i.e mb being used and by what device and what protocol the + is missing even with a reset by button and re-configure
 

Voxel

Very Senior Member
OK, sorry guys. Experiment with upgrading redis server and client was wrong :confused: Prebuilt modules are oriented to old version of redis...

Wait for a QoS fixing version (revert redis) 1.0.2.41SF.

Voxel.
 

ulaganath

Senior Member
Is there any default timeout for the firmware upload through any means.
 

ulaganath

Senior Member
I believe even 41F is crashing. Last know firmware to work without crash is 37F.

Would it broken if i downgrade from 41F
 

Voxel

Very Senior Member
I believe even 41F is crashing. Last know firmware to work without crash is 37F.
Please do not scare users of my FW. First, you mean that you have unclear crashing QoS, but not FW itself. Second, you have the same crashing QoS with stock FW. Third, this problem is something unique, and maybe exists only in your environment: nobody else reported such problem, neither with stock FW, nor with my build. And I've put previous version of QoS for download especially for you. And you have confirmed that previous version of QoS is working OK for you, right?

Also, "I believe even 41F is crashing": you believe or it is so? Notice, that changes in my FW since 37SF do not touch QoS.

Voxel.
 

ulaganath

Senior Member
I didn't mean the router crash. its QOS crash. May be its my environment. I didnt want it to crash. The firmware when you introduced the I/O handler it stopped crashing. Which few asked why is it required. And few stayed away. After that next version also stable. Starting from 39F i am facing this issue.

May be a refresh to router might resolve the issue. Will try this weekend.

Since i connect another router in Bridge mode. Most of the clients wireless connects to my R7800 and only Wired DesktopPC and NAS connects to linksys EA7500.

May be the EA can cause this issue. I need a direct connect from Router to PC and NAS. I cant move it to the Prime R7800 location.

Anyway. You fimware was far better than stock and really meant to be the firmware Which netgear would have done from the begining.

the release a hardware and leave it unless it is vulnerable and need a real attention. Otherwise if untile the core functionality is not affected it wont be a neceessity for them to patch it.

You does every module upgrade to latest which includes the basic fix and improvement over the preivous version.

Thanks
 

Voxel

Very Senior Member
I didn't mean the router crash. its QOS crash. May be its my environment. I didnt want it to crash.
So maybe you should try again with previous version of QoS. I still keep it for downloading. In past it was helpful for your issue.

The firmware when you introduced the I/O handler it stopped crashing. Which few asked why is it required. And few stayed away. After that next version also stable. Starting from 39F i am facing this issue.
It is rather strange because irqbalance is still in my builds. Changes in 39 and above are mainly related to Samba optimization and the last does not touch QoS at all. You know, I tried to upgrade redis server/client in 40SF especially for your case, but unfortunately newer version is not compatible with version used in QoS. Redis is used by all QoS applications. So QoS related stuffs are now the same as in 37SF.

You are welcome :). Try previous QoS DB.

Voxel.
 

Jeanmi

Occasional Visitor
Hello Voxel,
Qos is still blocked
is it possible to restart Qos from ssh / telnet without restarting the router
Thank you
 

Killhippie

Senior Member
Hello Voxel,
Qos is still blocked
is it possible to restart Qos from ssh / telnet without restarting the router
Thank you
Did you download 1.0.2.41SF that should fix QoS, if need be reboot the router, it wont do any harm its not like doing a reset.
 

Voxel

Very Senior Member
Hello Voxel,
Qos is still blocked
is it possible to restart Qos from ssh / telnet without restarting the router
Thank you
Hello,

I do not know, mine is still working (3 days after last reboot). Try to clear cache in your browser.

Command to restart QoS from console:

Code:
/etc/init.d/streamboost stop
/etc/init.d/streamboost start
iptables should display some error messages, but just ignore them.

Check that QoS is working after restart (or/and before):
Code:
/bin/ps | grep appflow
Voxel.
 

Jeanmi

Occasional Visitor
no appflow process

[email protected]:/$ /bin/ps | grep appflow
3128 root 320 S grep appflow

[email protected]:/$ /etc/init.d/streamboost stop
streamboost: StreamBoost: Executing stop all

[email protected]:/$ /etc/init.d/streamboost start
streamboost: StreamBoost: Executing start all
[ OK ] 01_redis start
[ OK ] 10_policy-reader start
[ OK ] 11_sbsaved start
[ OK ] 12_settings-loader start
[ OK ] 13_prio-reader start
[ OK ] 25_sea start
[ OK ] 30_sbnoded start
[ OK ] 31_nodedetectd start
[ OK ] 32_sbnamed start
[ OK ] 33_sbmacouid start
[ OK ] 34_jigglyp0f start
[ OK ] 35_leash start
streamboost: Action
[ FAIL ] 40_qdiscman start
Setting up qdiscs on interface brwan
Setting up qdiscs on interface br0
RTNETLINK answers: Invalid argument
Starting Firewall...
Done!
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
streamboost: StreamBoost: Executing stop all
[ OK ] 60_ozker stop
streamboost: Automatic updates are disabled. Using existing files.
[ OK ] 52_p0f stop
[ OK ] 50_drflocs stop
[ OK ] 49_cape stop
[ OK ] 45_flowman stop
[ OK ] 44_overlord stop
[ OK ] 43_flowmark stop
[ OK ] 40_qdiscman stop
[ OK ] 35_leash stop
[ OK ] 34_jigglyp0f stop
[ OK ] 33_sbmacouid stop
[ OK ] 32_sbnamed stop
[ OK ] 31_nodedetectd stop
[ OK ] 30_sbnoded stop
[ OK ] 25_sea stop
[ OK ] 13_prio-reader stop
[ OK ] 12_settings-loader stop
[ OK ] 11_sbsaved stop
[ OK ] 10_policy-reader stop
[ OK ] 01_redis stop
streamboost: flushing conntrack
Starting Firewall...
Done!
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
killall: poll_set_priority: no process killed

[email protected]:/$ /bin/ps | grep appflow
3865 root 320 S grep appflow
 

Voxel

Very Senior Member
no appflow process

[email protected]:/$ /bin/ps | grep appflow
3128 root 320 S grep appflow

[email protected]:/$ /etc/init.d/streamboost stop
streamboost: StreamBoost: Executing stop all

[email protected]:/$ /etc/init.d/streamboost start
streamboost: StreamBoost: Executing start all
[ OK ] 01_redis start
[ OK ] 10_policy-reader start
[ OK ] 11_sbsaved start
[ OK ] 12_settings-loader start
[ OK ] 13_prio-reader start
[ OK ] 25_sea start
[ OK ] 30_sbnoded start
[ OK ] 31_nodedetectd start
[ OK ] 32_sbnamed start
[ OK ] 33_sbmacouid start
[ OK ] 34_jigglyp0f start
[ OK ] 35_leash start
streamboost: Action
[ FAIL ] 40_qdiscman start
Setting up qdiscs on interface brwan
Setting up qdiscs on interface br0
RTNETLINK answers: Invalid argument
Starting Firewall...
Done!
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
streamboost: StreamBoost: Executing stop all
[ OK ] 60_ozker stop
streamboost: Automatic updates are disabled. Using existing files.
[ OK ] 52_p0f stop
[ OK ] 50_drflocs stop
[ OK ] 49_cape stop
[ OK ] 45_flowman stop
[ OK ] 44_overlord stop
[ OK ] 43_flowmark stop
[ OK ] 40_qdiscman stop
[ OK ] 35_leash stop
[ OK ] 34_jigglyp0f stop
[ OK ] 33_sbmacouid stop
[ OK ] 32_sbnamed stop
[ OK ] 31_nodedetectd stop
[ OK ] 30_sbnoded stop
[ OK ] 25_sea stop
[ OK ] 13_prio-reader stop
[ OK ] 12_settings-loader stop
[ OK ] 11_sbsaved stop
[ OK ] 10_policy-reader stop
[ OK ] 01_redis stop
streamboost: flushing conntrack
Starting Firewall...
Done!
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
killall: poll_set_priority: no process killed

[email protected]:/$ /bin/ps | grep appflow
3865 root 320 S grep appflow
Strange. Seems you have problems similar to ulaganath's.

My code (start QoS after stopping, checked right now):

Code:
 /etc/init.d/streamboost start
streamboost: StreamBoost: Executing start all
 [  OK  ] 01_redis start
 [  OK  ] 10_policy-reader start
 [  OK  ] 11_sbsaved start
 [  OK  ] 12_settings-loader start
 [  OK  ] 13_prio-reader start
 [  OK  ] 25_sea start
 [  OK  ] 30_sbnoded start
 [  OK  ] 31_nodedetectd start
 [  OK  ] 32_sbnamed start
 [  OK  ] 33_sbmacouid start
 [  OK  ] 34_jigglyp0f start
 [  OK  ] 35_leash start
 [  OK  ] 40_qdiscman start
 [  OK  ] 43_flowmark start
 [  OK  ] 44_overlord start
 [  OK  ] 45_flowman start
 [  OK  ] 49_cape start
 [  OK  ] 50_drflocs start
 [  OK  ] 52_p0f start
 [  OK  ] 60_ozker start
Starting Firewall...
Done!
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: Bad rule (does a matching rule exist in that chain?).
ip6tables: No chain/target/match by that name.
ip6tables: No chain/target/match by that name.
streamboost: streamboost update
Downloading https://updates.r7800.netgear.streamboost.yeti.bigfootnetworks.com/banana/packages-2/Packages.gz.
Updated list of available packages in /var/opkg-lists/streamboost.
streamboost: [  OK  ] Everything is up-to-date.
Maybe you should do reset of your R7800. Backup settings, reset and restore. Is something specific in your ISP connection?

Voxel.
 

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