[fedoracooper]

I have discussed some of this in another thread:
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=264398

I flashed a Buffalo WHR-600D with build 23503 back in July. It worked almost flawlessly for three months; maybe one reboot required. I mostly use it for wireless: 2.4GHz and 5GHz with WPS2 and AES encryption. The main purpose was QOS so I could throttle my Roku to certain bandwidth to maintain low latencies.

Then one day I can come, and the wireless was down. No power outage, as my desktop was still running, but I discovered the WHR-600D appeared to be rebooting itself about once per minute.

The Web UI was all corrupted, and I was able to see the status page, but there were no images and most buttons were not present or not clickable. The only thing working was occasionally the wired connections would give me about 30 seconds of functionality between reboots. I couldn't do anything useful with it, so I performed a full 30/30/30 reset. This seemed to take effect, and the DHCP settings were reset.

Now the web UI is either totally unavailable (unable to connect to port 80), or similar issues with a corrupt UI, and I cannot even reset the password. It seems to reboot 2 or 3 times after a cold boot, then "run," with wired DHCP working and wireless probably on default. But it is not configurable, so it is useless. Buffalo said they won't support it, of course.

I realized that I was still able to telnet in. This revealed what I suspected: something got corrupted with the ROM image. This was especially troubling because I had not flashed it in months, and there was no apparent power surge or anything!

I tried to use wget to grab a new image from my local desktop, but wget says "Connecting to..." but doesn't actually save any content, even when I'm in the tmp directory. The scp program just says "permission denied" when I run it. I am able to create files manually under /tmp and /tmp/root.

I am giving up on this router, but I wanted to bring this up. Is it possible that dd-wrt has somehow allowed or caused ROM corruption during normal operating conditions? Perhaps the device was running too hot or with some improper settings that affected hardware reliability? Or was this just a freak glitch that could have affected the stock firmware? This second possibility is hard for me to accept.

In any case, the dmesg output indicates what appears to be normal bootup until I get a bunch of errors related to SQUASHFS getting bad blocks: