Just use the device you are telnet'ing with to securely copy the file via Filezilla/WinSCP to /tmp and follow those commands listed except for wget since you don't seem to have an internet connection on the router.
so this is another garbage build with a broken gui?
The router is working fine...it is just the gui, and you can Putty back into to it if you get locked out.
Someone else said that their router is running lower temps with this build, so that is bonus. Any reduction in heat is good since heat = resistance, which makes things slow.
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Thu Jul 13, 2017 13:07 Post subject:
An observation.
The CPU load goes way up as you bounce around in the GUI. the process "httpd -p 80" is the culprit. I'm not sure why its using so many CPU cycles and on the old builds the httpd process hardly budges.
Not being a programmer...I'm not sure what changed...all I can tell you is what I observe.
redhawk _________________ The only stupid question....is the unasked one.
Router: Asus RT-N66U
Firmware: DD-WRT v3.0-r32597 big (07-08-2017)
Previous: DD-WRT v3.0-r26138 big (02-04-2015)
Reset: Reset defaults post flash
Errors: GUI stops responding
It does appear to be a bad one as mentioned.
Been running the recommended r26138 build in client mode without issue.
Flashed through the GUI + Reset to Factory Defaults
Upon rebooting the router seems to briefly show the miniCFE server @ 192.168.1.1, then shows the expected first startup page. Managed to set a password just before the whole thing craps itself and won't respond at 192.168.1.1. Power/wireless lights stay constant; the unit doesn't enter a reboot cycle.
Wiped the unit by holding the WPS button after applying power, put it into recovery mode, flashed DD-WRT v3.0-r32170 big through the miniCFE server. Back to normal again.
