Ever since I updated the version of KONG I had on my R8000 my router reboots about once a day. I've tried going back to other versions of Kong an it does the same thing. I've done the 30/30/30 reset and restored my backup and have no clue whats causing this issue. Before my router would be up for weeks with no issue.
Rehabilitation, underground utilities, sewer installation and repair
American Sewer and Utilities has consistently demonstrated excellence in the design and construction of a myriad of projects encompassing underground utilities, site development, leach fields, pump stations, landscaping, sanitary sewer, and municipal & residential rehabilitation. Our distinguished team comprises seasoned professionals and skilled artisans, dedicated to providing superior construction consultation and management servicesRecent comments
- After the initial Kong Mod 11 months 3 weeks ago
- Working the EXACT same 11 months 3 weeks ago
- While the "5 Easy Steps" 1 year 16 hours ago
- R8000P would be grate to see. 1 year 1 day ago
- Have a R8000 but ordered a 1 year 1 day ago
You may want to check Kong's download site directly and see if there's an updated firmware version. Sometimes it takes many days or weeks before it gets posted this this site.
http://desipro.de/ddwrt/K3-AC-Arm/
One last thought, I was having all sorts of unspecific problems with my R8500 - even after having reinstalled different firmware versions and doing the 30/30/30 reset. I tried a last ditch effort, and did a fresh install of the Kong's latest firmware after having performed a 30/30/30 reset. I then did *not* resotre my backup settings but recreated them from scratch. Tedious, but it worked like a charm. I've had no issues since and, since then, have been able to upgrade firmware versions and restore my settings no problem.
Hope this helps!
I tried rolling back versions and doing the 30/30/30 reset and it kept rebooting at least once a day. I restored from backup then changed my 2.4ghz to G instead of mixed and the router has been up for over a day without a reboot. Do you currently have your 2.4 configured that way?
Two days up time with no reboots. I don't know why chaging the 2.4 to G instead of mixed seemd to fixed the issue.
It was probably fighting with a neighbour.