You want Kong's builds for the R7000. Very similar to BrainSlayer's weekly builds, just less frequent and more tested. Roughly every couple months he posts a new build here:
I have family R7000s on Kong Builds 33770 with uptime over 34 days with heavy WiFi usage, most if not all device are WiFi only. I wouldn't use any older build since this one and newer has the WiFi CRACK fixes.
My two R7000s have an uptime of over 34 days with lite Wifi usage on Kong Build 35550. In my home network I have most things wired. With this build I do get HTTP errors in the logs when I log into the routers but doesn't effect the operation with over 34 days uptime.
My signature has link for CloneVince's Backup of Kong's ARM Firmware. for the R7000, if you are updating from DDWRT firmware use build named dd-wrt.v24-K3_AC_ARM_STD.bin. If your R7000 has stock NetGear Firmware use builld names dd-wrt.K3_R7000.chk. _________________ Home Network on Telus 1Gb PureFibre - 10GbE Copper Backbone
2x R7800 - Gateway & WiFi & 3xWireGuard - DDWRT r53562 Std k4.9
Off Site 1
R7000 - Gateway & WiFi & WireGuard - DDWRT r54517 Std
E3000 - Station Bridge - DDWRT r49626 Mega K4.4
Off Site 2
R7000 - Gateway & WiFi - DDWRT r54517 Std
E2000 - Wired ISP IPTV PVR Blocker - DDWRT r35531
Already tried this final build and it works ok only for some hours. After that the internet connection is down and I have to reboot the router.
Do an:
nvram erase
if you have not done so already, depending on setup bad wireless params from firmwares with older drivers will cause a driver crash leading to a reboot with in a few hours.
Yea kong's latest builds are as good as it gets for the R7000. It runs very solid for most people. If you have issues maybe try XWRT-Vortex, or back to stock.
Yea kong's latest builds are as good as it gets for the R7000. It runs very solid for most people. If you have issues maybe try XWRT-Vortex, or back to stock.
If I recall correctly Kong said Vortex screws your partition so it's impossible to go back unless you had a backup. _________________ R6400v2 (boardID:30) - Kong 36480 running since 03/09/18 - (AP - DNSMasq - AdBlocking - QoS) R7800 - BS 31924 running since 05/26/17 - (AP - OpenVPN Client - DNSMasq - AdBlocking - QoS) R7000 - BS 30771 running since 12/16/16 - (AP - NAS - FTP - SMB - OpenVPN Server - Transmission - DDNS - DNSMasq - AdBlocking - QoS) R6250 - BS 29193 running since 03/20/16 - (AP - NAS - FTP - SMB - DNSMasq - AdBlocking)
Already tried this final build and it works ok only for some hours. After that the internet connection is down and I have to reboot the router.
Do an:
nvram erase
if you have not done so already, depending on setup bad wireless params from firmwares with older drivers will cause a driver crash leading to a reboot with in a few hours.
Other than that there is no known issue that can cause this.
Can you please clarify whether it's "nvram erase" or "erase nvram" ?
Already tried this final build and it works ok only for some hours. After that the internet connection is down and I have to reboot the router.
Do an:
nvram erase
if you have not done so already, depending on setup bad wireless params from firmwares with older drivers will cause a driver crash leading to a reboot with in a few hours.
Other than that there is no known issue that can cause this.
Can you please clarify whether it's "nvram erase" or "erase nvram" ?
Tia.
Since some 35xxx version the command changed to nvram erase, he said he would add a wrapper to make it consistent with how it was before (because of this exact same reason of confusing people) but apparently it's still yet to be done. _________________ R6400v2 (boardID:30) - Kong 36480 running since 03/09/18 - (AP - DNSMasq - AdBlocking - QoS) R7800 - BS 31924 running since 05/26/17 - (AP - OpenVPN Client - DNSMasq - AdBlocking - QoS) R7000 - BS 30771 running since 12/16/16 - (AP - NAS - FTP - SMB - OpenVPN Server - Transmission - DDNS - DNSMasq - AdBlocking - QoS) R6250 - BS 29193 running since 03/20/16 - (AP - NAS - FTP - SMB - DNSMasq - AdBlocking)
I tried again this time with nvram erase and nothing changed. The router freezes after some time: minutes or hours.
Firmware: v3.0-r36070M kongac (05/31/2018)
Joined: 18 Mar 2014 Posts: 12887 Location: Netherlands
Posted: Wed Jun 06, 2018 11:44 Post subject:
After "nvram erase" or "erase nvram", both works on the latest version, all settings shoud be gone.
Important, reboot after erasing and put settings in manually do not restore from backup.
After "nvram erase" or "erase nvram", both works on the latest version, all settings shoud be gone.
Important, reboot after erasing and put settings in manually do not restore from backup.
If you use erase nvram then the router responds with Flash is NAND and the erased size, I am not sure if both commands nvram erase and erase nvram are doing the same, maybe Kong can explain?
I tried both "nvram erase" and "erase nvram". Every time reboot after erasing and put settings in manually and I have the same behaviour: freeze after some time and manually reboot to recover.
As far as I know we should use "nvram erase".
Yea kong's latest builds are as good as it gets for the R7000. It runs very solid for most people. If you have issues maybe try XWRT-Vortex, or back to stock.
+1. I just installed XWRT-Vortex and I am so happy I did. I appreciate all the hard work that Kong and others have put into DDWRT, but whatever combination of settings I had did not result in stability. Vortex is clean, fast, and above all, works. I just mentioned this in another thread on this forum as well...
