This is the r7000 build steelskinz.
The r7000.chk file is for coming from another firmware such as stock. Once your on dd-wrt you flash with .bin files.
steelskinz wrote:
Why don't you use the R7000 build instead of AC ARM STD ?
_________________ Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode
Joined: 03 Jul 2013 Posts: 13 Location: United States
Posted: Fri May 18, 2018 5:47 Post subject:
Router: R7000
Firmware: DD-WRT v3.0-r35900M kongac (05/08/18 )
Kernel: Linux 4.4.131 #551 SMP Tue May 8 12:14:17 CEST 2018 armv7l
Status: Partially working
Reset: Yes
Errors: Yes
Creating a bridge 'br1' for a guest network on both bands to share one DHCP server causes one VLAN (usually 2.4GHz) to stop broadcasting.
5GHz band broadcasts just fine, but 2.4 usually does not.
As it happened before with older builds, after 7-8 days, extender cannot connect to R8000 anymore without a reboot.
It didn't seem to happen with 35550 so roll back to check the difference.
I have started to have the same issue after 8 days, dhcp, wireless, dnsmasq, httpd seem to have crashed for some reason. Using a static ip didn't help, neither telnet or ssh couldn't gain access, a reboot will put things back to normal at least for me a few hours, it safe to assume to go back to previous version till a fix or new build is issued out. My router setup is a dhcp from isp docsis 3 modem connection not a bridge, no vpn just a gateway type of connection for network, wireless does run well on both radios till the lock out was occurring since last early this morning 3 am had rebooted to find it back down 5 hrs later, friday morning and rebooted again to gain access the only thing i am doing for now is disabled qos and see if that does anything?
Router: Asus RT-AC66U_B1 HW version B2
Firmware: DD-WRT v3.0-r35900M kongac (05/10/1 Kernel: Linux 4.4.131 #553 SMP Thu May 10 09:47:47 CEST 2018 armv7l DD-WRT
Status: WebGUI is laggy, border-line non-responsive
Reset: No
Errors: Yes - Log is full of daemon.err httpd[1069]: Request Error Code 408: No request appeared within a reasonable time period. HTTPD process is spiking CPU to 50% on every WebGUI command
Will probably revert back to an older version although the stable version looses connectivity after working 20-24 hours.
