Don't try this on Merlin

[Fraoch]

I just installed 3.0.0.4.270.26 Merlin on my brand-new N66U.

I like it so far!

File this under the "that was stupid" department - don't ever try the command "top" in the Tools - Run Cmd tab.

I thought I'd be smart and check to see what processes were running, how much memory and CPU they were using, etc. but instead the web UI froze.

The router was still working but the webpage was frozen. After closing the frozen web GUI, it would not load again.

I resorted to the reset button. An initial short press halted all routing activity and lead to a web GUI page which would not load. I had to press and hold the reset button for about 10 seconds to get the web GUI to load again and it was back to factory defaults.

Whew!

I suspect any command which will run indefinitely should not be attempted because there's no way for it to report back continuously, just one line at a time.

 

[RMerlin]

I just installed 3.0.0.4.270.26 Merlin on my brand-new N66U.

I like it so far!

File this under the "that was stupid" department - don't ever try the command "top" in the Tools - Run Cmd tab.

I thought I'd be smart and check to see what processes were running, how much memory and CPU they were using, etc. but instead the web UI froze.

The router was still working but the webpage was frozen. After closing the frozen web GUI, it would not load again.

I resorted to the reset button. An initial short press halted all routing activity and lead to a web GUI page which would not load. I had to press and hold the reset button for about 10 seconds to get the web GUI to load again and it was back to factory defaults.

Whew!

I suspect any command which will run indefinitely should not be attempted because there's no way for it to report back continuously, just one line at a time.

Just turning the router off and back on would have fixed this. You basically told the web server to run a command that never stops running (top), which hung the httpd process as it kept waiting for it to complete.

 

[Fraoch]

Just turning the router off and back on would have fixed this. You basically told the web server to run a command that never stops running (top), which hung the httpd process as it kept waiting for it to complete.

I was considering doing that and I should have. Fortunately I don't have that many custom options set and I was back up and running in less than a minute.

Thanks very much for this firmware, RMerlin!