Custom firmware build for R7800 v. 1.0.2.72SF

[L&LD]

@Mr Levy can you use a device that is immune, such as one with a different os?

 

[percy3]

Some time ago I was wondering what are the reasons for quite high system load with Voxel's firmware but had nothing to compare against. Now I have OpenWrt build with similar feature set and average load while iddle (no VPN tunnel and no significant amount of data transfer) is 0.1 while the temperature average (over last month) is 49 oC.

Here is the top while idle:

Mem: 436488K used, 40420K free, 5572K shrd, 33164K buff, 287648K cached
CPU:   0% usr   0% sys   0% nic  97% idle   0% io   0% irq   2% sirq
Load average: 0.04 0.09 0.08 3/137 19163
  PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
 1504     1 root     S     786m 169%   0% /usr/sbin/dnscrypt-proxy -config /etc/
18744 18736 root     R     1100   0%   0% top
 7207     1 root     SN    4968   1%   0% /usr/sbin/collectd -C /tmp/collectd.co
   16     2 root     SW       0   0%   0% [ksoftirqd/1]
19061     2 root     IW       0   0%   0% [kworker/0:2-eve]
19075     2 root     IW       0   0%   0% [kworker/1:1-eve]
 3133     1 root     S    29352   6%   0% /usr/bin/minidlna -f /var/etc/minidlna
 7535  6795 root     S    27552   6%   0% /usr/sbin/smbd -F
18047  6795 root     S    27508   6%   0% /usr/sbin/smbd -F
 6795     1 root     S    27376   6%   0% /usr/sbin/smbd -F
 6946  6795 root     S    25160   5%   0% {cleanupd} /usr/sbin/smbd -F
 6945  6795 root     S    25156   5%   0% {smbd-notifyd} /usr/sbin/smbd -F
 6796     1 root     S    16060   3%   0% /usr/sbin/nmbd -F
 1085     1 root     S     4316   1%   0% /usr/sbin/hostapd -s -n phy1 -g /var/r
  837     1 root     S     4268   1%   0% /usr/sbin/hostapd -s -n phy0 -g /var/r
  838     1 root     S     4220   1%   0% /usr/sbin/wpa_supplicant -s -n phy0 -g
 1086     1 root     S     4220   1%   0% /usr/sbin/wpa_supplicant -s -n phy1 -g
 7243     1 root     SN    4016   1%   0% /usr/sbin/uhttpd -f -h /www -r xxxxxx
 5796     1 nobody   S     3664   1%   0% /usr/sbin/openvpn --syslog openvpn(vpn
 5795     1 nobody   S     3656   1%   0% /usr/sbin/openvpn --syslog openvpn(vpn

And the same during SMB data transfer from attached ext4 hard drive to wireless client at around 460 Mbps:

Mem: 452356K used, 24552K free, 5572K shrd, 31504K buff, 271060K cached
CPU:   0% usr  37% sys   0% nic  17% idle   8% io   0% irq  34% sirq
Load average: 3.77 1.90 0.84 2/146 19293
  PID  PPID USER     STAT   VSZ %VSZ %CPU COMMAND
18047  6795 xxx@hotm R    30840   6%  52% /usr/sbin/smbd -F
   87     2 root     SW       0   0%   3% [usb-storage]
    9     2 root     RW       0   0%   3% [ksoftirqd/0]
   28     2 root     SW       0   0%   3% [kswapd0]
19061     2 root     IW       0   0%   1% [kworker/0:2-eve]
   16     2 root     SW       0   0%   1% [ksoftirqd/1]
   10     2 root     IW       0   0%   1% [rcu_sched]
19290     2 root     IW       0   0%   1% [kworker/1:0-eve]
 1504     1 root     S     786m 169%   0% /usr/sbin/dnscrypt-proxy -config /etc/
 7207     1 root     SN    4968   1%   0% /usr/sbin/collectd -C /tmp/collectd.co
 5933     1 dnsmasq  S     1340   0%   0% /usr/sbin/dnsmasq -C /var/etc/dnsmasq.
18744 18736 root     R     1100   0%   0% top
19074     2 root     IW       0   0%   0% [kworker/u4:2-at]
 3133     1 root     S    29352   6%   0% /usr/bin/minidlna -f /var/etc/minidlna
 7535  6795 root     S    27552   6%   0% /usr/sbin/smbd -F
 6795     1 root     S    27376   6%   0% /usr/sbin/smbd -F
 6946  6795 root     S    25160   5%   0% {cleanupd} /usr/sbin/smbd -F
 6945  6795 root     S    25156   5%   0% {smbd-notifyd} /usr/sbin/smbd -F
 6796     1 root     S    16060   3%   0% /usr/sbin/nmbd -F
 1085     1 root     S     4316   1%   0% /usr/sbin/hostapd -s -n phy1 -g /var/r

What are your readings?

 

[kamoj]

The Average load measures in Netgear FW, e.g. top is corrupt.

 

[pege63]

No new FW before X-mas Voxel?

 

[Voxel]

No new FW before X-mas Voxel?

Why not? There should be something like Xmas edition, right?

Voxel.

 

[pege63]

Why not? There should be something like Xmas edition, right?

Voxel.

Soon 2 months ago (191025) and everyone else gets updates, except this workhorse as it looks .

 

[NetBytes]

Why not? There should be something like Xmas edition, right?

Voxel.

Have you had a chance to look at the early connection of the WAN port as if the router is in Bridge mode during boot?

 

[Voxel]

Have you had a chance to look at the early connection of the WAN port as if the router is in Bridge mode during boot?

I am really sorry but it is impossible to debug this issue and find the solution in the brain. I just cannot reproduce such environment. I suggest you to continue your experiments. In my guessing the problem could be even not in net-wan but in net-lan. I.e. it is started too early and your modem is bombarded by MAC addresses of your device when it can accept only one "friendly" from R7800. This problem is not unique for R7800 and my version of fw. E.g.

https://community.netgear.com/t5/Ni...g-connection-in-bridge-mode/m-p/1641596#M4161

something similar.

You may try chenge the MAC of router to MAC of computer in your LAN connected by cable to router. Changing /etc/init.d/net-lan etc... For example set delay in this net-lan. As I guess: as soon as your LAN is UP it starts this bombarding by MAC. Confusing your modem.

Sorry, I cannot provide you real help w/o real access to devices. 62SF was based on the stock 1.0.2.60, more recent versions have the changes from the stock 1.0.2.62. I do not have full source codes to understand what else was changed in all the binaries...

Voxel.

 

[Voxel]

Soon 2 months ago (191025) and everyone else gets updates, except this workhorse as it looks .

Desserts should be eaten last

Voxel.

 

[NetBytes]

I am really sorry but it is impossible to debug this issue and find the solution in the brain. I just cannot reproduce such environment. I suggest you to continue your experiments. In my guessing the problem could be even not in net-wan but in net-lan. I.e. it is started too early and your modem is bombarded by MAC addresses of your device when it can accept only one "friendly" from R7800. This problem is not unique for R7800 and my version of fw. E.g.

https://community.netgear.com/t5/Ni...g-connection-in-bridge-mode/m-p/1641596#M4161

something similar.

You may try chenge the MAC of router to MAC of computer in your LAN connected by cable to router. Changing /etc/init.d/net-lan etc... For example set delay in this net-lan. As I guess: as soon as your LAN is UP it starts this bombarding by MAC. Confusing your modem.

Sorry, I cannot provide you real help w/o real access to devices. 62SF was based on the stock 1.0.2.60, more recent versions have the changes from the stock 1.0.2.62. I do not have full source codes to understand what else was changed in all the binaries...

Voxel.

Thank you for all your work on this firmware. I greatly appreciate a better working device than the stock FW.
When I can I will devote some more time to attempting a fix.

I like your idea of delaying the net-lan startup.
What about starting net-wan first?
I will wait for the next Voxel FW before I dive into this again, though.

 

[Voxel]

What about starting net-wan first?

Yes it would be good to test it. You need to create symlinks in /etc/rc.d for net-wan and net-lan... "S##" in its name is priority to start.

Voxel.

 

[NetBytes]

Voxel,
I did tests using ifconfig $WAN_IF down; sleep 10; ifconfig $WAN_IF up
which did not seem to do anything?
Is 'ifconfig $WAN_IF down' the right thing to try to bring down the wan port power/connection?
And $WAN_IF was set to eth0.

 

[*Legion*]

Saw in the README the bit about wanting to see if people are still using this. I'm still rocking my R7800 and very happy to have these updates still coming. Thank you for your efforts, Voxel.

 

[microchip]

Add me to the list of a happy Voxel user
And the awesome new addon by kamoj

 

[Jarkko Laine]

Here's also one happy Voxel firmware user. Running rock solid for me.
Big thanks to Voxel.

 

[hannez8014]

Hi
Big thanks for your efforts to keep up with great firmware to the R7800. Many thanks!!!

Skickat från min POT-LX1 via Tapatalk

 

[kokishin]

Here is Voxel's readme.1st file included with 72SF. It states:

Goal of this project is the continuous support of really good router R7800 (I mean hardware)
from NETGEAR keeping its firmware up-to-date (fixing vulnerability issues, bugs removal,
optimization of the speed, adding new features/functionality etc).

But please find your time if you like it (just few minutes) to at least press the button
[Like] on SNB forums in the thread of this release of firmware (V. 1.0.2.72SF):

https://www.snbforums.com/forums/netgear-ac-wireless.53/

I do not need the scores or so on SNB (increasing number of your likes), it gives me
nothing, but I have to know that not only 27 guys and ladies (27 is total amount of
"likes" for previous 1.0.2.70SF) are interested in continuation of my really hard work
(this project).

I think it is normal human reaction to say "thank you" to the man who is helping you,
right?

Thank you for understanding,
Voxel.

@Voxel,

PLEASE keep supporting the R7800.

You've taken a sow's ear (Netgear firmware) and turned it into a silk purse.

Presuming you are getting many more downloads than 'likes", that in itself speaks of the popularity of your firmware.

Your online support on SNB forums (along with a touch of humor) is also very appreciated.

In summary, thank you and keep up your excellent work!

[Note to Voxel firmware users:
On Voxel's firmware download site http://www.voxel-firmware.com/Downloads/Voxel/html/r7800.html, he provides a link to make a donation to help with the cost of his work. I'm generally a stingy guy but I made an exception and sent Voxel a donation a few months ago. As we enter the holiday season, why not send Voxel a little Christmas gift? He's earned it. I used Paypal with no issues.]

 

[Infinitum]

Your online support on SNB forums (along with a touch of humor) is also very appreciated.

In summary, thank you and keep up your excellent work!

Thanks, kokishin, for calling out both the donation link and "like" feature; after a year on Voxel's firmware, I just availed myself of both options.

More importantly, thank you, Voxel, for your brilliance, patience and hard work! Happy Xmas and New Year!

 

[vladlenas]

Wow, 130 likes is a record.
Thank you so much for your excellent work. You are not only a great developer, but also a cute, responsive person!

 

[DRiP]

There seems to be an issue with STUBBY (DoT) using the provided config file. Has anyone been able to address this?

root@R7800:/tmp/log$ cat stubby.log
Tue Dec 17 17:25:54 GMT 2019
[23:25:54.735267] STUBBY: Read config from file /etc/stubby/stubby.yml
[23:26:07.515961] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:07.516180] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:07.516305] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:07.516617] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:10.017492] STUBBY: 2606:4700:4700::1111                     : Upstream   : !Backing off TLS on this upstream    - Will retry again in 2s at Tue Dec 17 23:26:12 2019
[23:26:11.267726] STUBBY: 2606:4700:4700::1001                     : Upstream   : !Backing off TLS on this upstream    - Will retry again in 2s at Tue Dec 17 23:26:13 2019
[23:26:11.299529] STUBBY: 1.1.1.1                                  : Upstream   : !Backing off TLS on this upstream    - Will retry again in 2s at Tue Dec 17 23:26:13 2019
[23:26:11.326395] STUBBY: 2606:4700:4700::1111                     : Upstream   : No valid upstreams for TLS... promoting this backed-off upstream for re-try...
[23:26:11.326895] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:11.327270] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:11.327551] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:11.327832] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:11.328113] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:11.328363] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:11.328582] STUBBY: 1.0.0.1                                  : Upstream   : !Backing off TLS on this upstream    - Will retry again in 2s at Tue Dec 17 23:26:13 2019
[23:26:13.829488] STUBBY: 2606:4700:4700::1001                     : Upstream   : No valid upstreams for TLS... promoting this backed-off upstream for re-try...
[23:26:15.137610] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:15.137767] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:15.137892] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:15.138204] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:15.138485] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:15.138766] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:15.139016] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:15.139297] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:15.139547] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:17.433549] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:17.433893] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:17.434174] STUBBY: 2606:4700:4700::1111                     : Upstream   : !Backing off TLS on this upstream    - Will retry again in 2s at Tue Dec 17 23:26:19 2019
[23:26:18.787501] STUBBY: 2606:4700:4700::1001                     : Upstream   : !Backing off TLS on this upstream    - Will retry again in 2s at Tue Dec 17 23:26:20 2019
[23:26:18.812462] STUBBY: 1.1.1.1                                  : Upstream   : !Backing off TLS on this upstream    - Will retry again in 4s at Tue Dec 17 23:26:22 2019
[23:26:18.836392] STUBBY: 2606:4700:4700::1111                     : Upstream   : No valid upstreams for TLS... promoting this backed-off upstream for re-try...
[23:26:18.836861] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:18.837236] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:18.837486] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:18.837829] STUBBY: 1.0.0.1                                  : Upstream   : !Backing off TLS on this upstream    - Will retry again in 4s at Tue Dec 17 23:26:22 2019
[23:26:20.636173] STUBBY: 2606:4700:4700::1001                     : Upstream   : No valid upstreams for TLS... promoting this backed-off upstream for re-try...
[23:26:20.636548] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:20.636892] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:20.637204] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:20.637329] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:20.637454] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:20.637704] STUBBY:    *FAILURE* no valid transports or upstreams available!
[23:26:20.637954] STUBBY:    *FAILURE* no valid transports or upstreams available!
root@R7800:/tmp/log$