Custom firmware build for R7800 v. 1.0.2.60SF

[Voxel]

Continuation of
. . .
https://www.snbforums.com/threads/custom-firmware-build-for-r7800-v-1-0-2-59sf.48579/

New version of my custom firmware build: 1.0.2.60SF.

Changes (vs 1.0.2.59SF):

1. Partial rollback: integrated binaries and kernel objects from the stock 1.0.2.58 are reverted back to 1.0.2.52
(except net-cgi, trafficmeter, ookla, greendownload) to avoid probelms with Wi-Fi stability.
2. expat package is upgraded 2.2.5->2.2.6.
3. at package is upgraded 3.1.20->3.1.23.
4. curl package is upgraded 7.61.0->7.61.1.
5. ethtool package is upgaded 4.17->4.18.

The link is:

https://www.voxel-firmware.com (thanks to vladlenas for his help with hosting and testing Wi-Fi stability).

NOTE: Most probably no reset is needed to upgrade from my previous versions. But if you face problems it is better to perform reset.

Voxel.

 

[routine]

i think NG is getting worse r7800 drivers to sell more xr500 ...

 

[pluto2003]

Is anyone know how to auto restart R7800 every night?

 

[Voxel]

i think NG is getting worse r7800 drivers to sell more xr500 ...

I do not think so. IMO just a bug. As I wrote QCA drivers in the stock 1.0.2.52 and in the stock 1.0.2.58 are the same. Rather bug somewhere in enclosed binary from GPL.

Voxel.

 

[Voxel]

Is anyone know how to auto restart R7800 every night?

Simplest way is to use cron from Entware and to schedule the command "reboot".

P.S.
There are other ways e.g. to use cron from firmware, but it requires adding such concrete job after every reboot (cron table is stored in RAM). I.e. something like own script in /etc/init.d and the last should schedule such reboot for cron.

Voxel.

 

[randytsuch]

So this fixes the problems in 59SF, and also revises a few packages?

Thanks again for all your work, I'll give it a try.

 

[Gallo]

@pluto2003 simply google schedule a cron reboot. here are some examples
https://askubuntu.com/questions/13730/how-can-i-schedule-a-nightly-reboot.
hope it helps

@Voxel ....... Thanks. Netgear sorta botched things up looking forward to trying 60

 

[Deleted member 22229]

59 sorta botched things up looking forward to trying 60

No fault of Voxel or 59 firmware. It was Netgear that botched things up and those changes made it into Voxel's release.

 

[Gallo]

none implied

 

[routine]

I bought the router a few days ago. Now I'm with v1.0.2.60sf.
It's great but in online gaming there seems to be some pings higher than normal at some point. maybe the ping is not 100% stable. I've always used openwrt and I find the most stable firmware for any router .. I love that distro. What's more in the Voxel R7800 firmware? Could I try with openwrt to solve this?

example:
64 bytes from 216.58.198.35: icmp_seq=231 ttl=53 time=25.603 ms
64 bytes from 216.58.198.35: icmp_seq=232 ttl=53 time=26.839 ms
64 bytes from 216.58.198.35: icmp_seq=233 ttl=53 time=28.355 ms
64 bytes from 216.58.198.35: icmp_seq=234 ttl=53 time=52.984 ms
64 bytes from 216.58.198.35: icmp_seq=235 ttl=53 time=142.546 ms
64 bytes from 216.58.198.35: icmp_seq=236 ttl=53 time=141.567 ms
64 bytes from 216.58.198.35: icmp_seq=237 ttl=53 time=116.479 ms
64 bytes from 216.58.198.35: icmp_seq=238 ttl=53 time=27.355 ms
64 bytes from 216.58.198.35: icmp_seq=239 ttl=53 time=27.151 ms
64 bytes from 216.58.198.35: icmp_seq=240 ttl=53 time=26.604 ms
64 bytes from 216.58.198.35: icmp_seq=241 ttl=53 time=25.697 ms

 

[Voxel]

So this fixes the problems in 59SF, and also revises a few packages?

Yeah. Why not to upgrade together with fixing?

Voxel.

 

[Voxel]

It's great but in online gaming there seems to be some pings higher than normal at some point. maybe the ping is not 100% stable.

example:
64 bytes from 216.58.198.35: icmp_seq=231 ttl=53 time=25.603 ms
64 bytes from 216.58.198.35: icmp_seq=232 ttl=53 time=26.839 ms
64 bytes from 216.58.198.35: icmp_seq=233 ttl=53 time=28.355 ms
64 bytes from 216.58.198.35: icmp_seq=234 ttl=53 time=52.984 ms
64 bytes from 216.58.198.35: icmp_seq=235 ttl=53 time=142.546 ms
64 bytes from 216.58.198.35: icmp_seq=236 ttl=53 time=141.567 ms
64 bytes from 216.58.198.35: icmp_seq=237 ttl=53 time=116.479 ms
64 bytes from 216.58.198.35: icmp_seq=238 ttl=53 time=27.355 ms
64 bytes from 216.58.198.35: icmp_seq=239 ttl=53 time=27.151 ms
64 bytes from 216.58.198.35: icmp_seq=240 ttl=53 time=26.604 ms
64 bytes from 216.58.198.35: icmp_seq=241 ttl=53 time=25.697 ms

Interesting. Do you use your client for ping or it is from R7800 console? If client then cable or wireless?

My results from client (cable) ping to your host:

PING 216.58.198.35 (216.58.198.35): 56 data bytes
64 bytes from 216.58.198.35: icmp_seq=0 ttl=53 time=53.076 ms
64 bytes from 216.58.198.35: icmp_seq=1 ttl=53 time=52.399 ms
64 bytes from 216.58.198.35: icmp_seq=2 ttl=53 time=52.375 ms
64 bytes from 216.58.198.35: icmp_seq=3 ttl=53 time=52.519 ms
64 bytes from 216.58.198.35: icmp_seq=4 ttl=53 time=52.496 ms
64 bytes from 216.58.198.35: icmp_seq=5 ttl=53 time=52.301 ms
64 bytes from 216.58.198.35: icmp_seq=6 ttl=53 time=52.273 ms
64 bytes from 216.58.198.35: icmp_seq=7 ttl=53 time=52.248 ms
64 bytes from 216.58.198.35: icmp_seq=8 ttl=53 time=52.387 ms
64 bytes from 216.58.198.35: icmp_seq=9 ttl=53 time=52.365 ms
64 bytes from 216.58.198.35: icmp_seq=10 ttl=53 time=52.335 ms
64 bytes from 216.58.198.35: icmp_seq=11 ttl=53 time=52.470 ms
64 bytes from 216.58.198.35: icmp_seq=12 ttl=53 time=52.125 ms
64 bytes from 216.58.198.35: icmp_seq=13 ttl=53 time=52.258 ms
64 bytes from 216.58.198.35: icmp_seq=14 ttl=53 time=52.280 ms
. . .

Try other target, e.g. 8.8.8.8

PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=119 time=4.819 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=4.755 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=119 time=4.676 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=119 time=4.759 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=119 time=4.685 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=119 time=4.773 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=119 time=4.701 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=119 time=4.782 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=119 time=4.732 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=119 time=4.819 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=119 time=4.628 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=119 time=4.719 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=119 time=4.805 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=119 time=4.721 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=119 time=4.807 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=119 time=4.402 ms
64 bytes from 8.8.8.8: icmp_seq=16 ttl=119 time=4.814 ms
64 bytes from 8.8.8.8: icmp_seq=17 ttl=119 time=4.781 ms
64 bytes from 8.8.8.8: icmp_seq=18 ttl=119 time=4.543 ms
64 bytes from 8.8.8.8: icmp_seq=19 ttl=119 time=4.794 ms
^C--- 8.8.8.8 ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max/stddev = 4.402/4.770/5.712/0.238 ms

Voxel.

 

[routine]

I'm with wireless on imac. the results are the same..
I noticed these spikes on online gaming with console.
My old tp-link 841 with openwrt had these spikes but less long..
I think the NG firmware does not have the best bufferbloat.
Maybe with LEDE it would be better.. But I do not know...
From what I read the best NG firmware for the bufferbloat seems to be 1.0.2.46 but I have not tried.

64 bytes from 8.8.8.8: icmp_seq=469 ttl=120 time=29.794 ms
64 bytes from 8.8.8.8: icmp_seq=470 ttl=120 time=30.932 ms
64 bytes from 8.8.8.8: icmp_seq=471 ttl=120 time=149.285 ms
64 bytes from 8.8.8.8: icmp_seq=472 ttl=120 time=34.252 ms
64 bytes from 8.8.8.8: icmp_seq=473 ttl=120 time=152.304 ms
64 bytes from 8.8.8.8: icmp_seq=474 ttl=120 time=153.724 ms
64 bytes from 8.8.8.8: icmp_seq=475 ttl=120 time=31.980 ms
64 bytes from 8.8.8.8: icmp_seq=476 ttl=120 time=30.793 ms
64 bytes from 8.8.8.8: icmp_seq=477 ttl=120 time=30.844 ms
....
64 bytes from 8.8.8.8: icmp_seq=613 ttl=120 time=28.166 ms
64 bytes from 8.8.8.8: icmp_seq=614 ttl=120 time=228.241 ms
64 bytes from 8.8.8.8: icmp_seq=615 ttl=120 time=31.180 ms

 

[Deleted member 22229]

Hi Voxel. Does the .60 code have the security fixes Netgear has in there .58 firmware ?

 

[Voxel]

Hi Voxel. Does the .60 code have the security fixes Netgear has in there .58 firmware ?

You know, release notes just say:

· Fixes security issues

No any concrete information why/what/where they were fixed. If there is something vital usually NG informs that e.g. "PSV-2016-0131 is fixed". Not such a case with 1.0.2.58.

So the answer: I cannot say “yes” or “no”. Usually security issues are in net-cgi processor (WebGUI). If so then it is fixed in my version. There are some changes in miniupnpd but it is enclosed part of NG GPL and they use too outdated version so I do not recommend to use it even if it is updated now. There are a lot of security holes left in 1.0.2.58 because of old outdated packages so do not worry . I perform upgrade of packages not because I like to do that but to close vulnerability and to fix bugs of third party. Just for example, only some outdated packages in the stock version and known security issues with these versions:

OpenSSL:
CVE-2016-6304
CVE-2016-2183
CVE-2016-6303
CVE-2016-6302
CVE-2016-2182
CVE-2016-2180
CVE-2016-2177
CVE-2016-2178
CVE-2016-2179
CVE-2016-2181
CVE-2016-6306

OpenVPN:
CVE-2018-9336

dnsmasq:
CVE-2009-2957
CVE-2009-2958
CVE-2012-3411
CVE-2013-0198

proftpd
CVE-2009-3639
CVE-2010-3867
CVE-2010-4221
CVE-2010-4652
CVE-2011-1137
CVE-2011-4130
CVE-2012-6095

expat:
CVE-2012-0876
CVE-2012-1147
CVE-2012-1148
CVE-2013-0340

transmission:
CVE-2014-4909

redis:
CVE-2016-10517
CVE-2018-11218
CVE-2018-11219
CVE-2018-12326
CVE-2018-12453

avahi:
CVE-2017-6519

ffmpeg:
CVE-2013-4358
CVE-2014-8541
CVE-2014-8542
CVE-2014-8543
CVE-2014-8544
CVE-2014-8545
CVE-2014-8546
CVE-2014-8547
CVE-2014-8548
CVE-2014-8549
CVE-2015-1208
CVE-2017-9608
CVE-2018-14394
CVE-2018-14395

e2fsprogs:
CVE-2015-0247
CVE-2015-1572

wget:
CVE-2014-4877

etc.

At least all CVE above are fixed in my build (I hope ). But at least some of them are left in 1.0.2.58.

Voxel.

 

[randytsuch]

Hi all
I upgraded to .60sf last night, and it seems to be working fine.
I don't game and didn't do any ping testing, I'll leave that to others.

I noticed ssh stopped working, but I restored my backup
cd /
tar xf /mnt/sda1/backup.tar
reboot

And after that ssh worked again.

But it looks like Entware is not installed now.

Do I have to reinstall Entware?
Or is there an easier way?

Thanks
Randy

 

[RMerlin]

BTW @Voxel, try to access this thread using Taptalk. The first post is nearly endless as Taptalk inserts preview for every links that you provide in it, making it hard to access in Taptalk Might be a good idea IMHO to stop linking all the previous threads, maybe limit it to just the last one?

 

[routine]

I made some test. Last NG OTA update seems to be best with ping.(firmware 1.0.2.46)
There is'nt Smartconnect in this version.
All the ping under 30ms even if a little less in download ..
For the game I think that is the best version.
Less cpu load (1.5 vs 2 - 2.5 ) of other version.

 

[Voxel]

But it looks like Entware is not installed now.

Do I have to reinstall Entware?
Or is there an easier way?

Try to reboot your router. Entware should be OK, but maybe ReadyCLOUD from NG (it is installed after flashing automatically) is not ready yet. ReadyCLOUD uses /opt. The same as Entware.

Voxel.

 

[Voxel]

BTW @Voxel, try to access this thread using Taptalk. The first post is nearly endless as Taptalk inserts preview for every links that you provide in it, making it hard to access in Taptalk Might be a good idea IMHO to stop linking all the previous threads, maybe limit it to just the last one?

Ugh.. OK I see. I hate to use small gadgets for accessing forums... Only when I am far away w/o laptop

Well, I understand. Let's limit the history (last thread). Thanks for your suggestion.

Voxel.