On Sun, 13 May 2012 14:07:15 -0700, William Bonner <
wbo...@gma.com>
wrote:
>I know you're one of (if not the) most respected guy on this forum so I do
>appreciate your advice.
Hang on while I polish my ego.
>I'm in the Santa Cruz mountains (like you) and we
>do get glitches in the power a lot. Seems to go down once a month
>sometimes, and other times it lasts for six months before the generator
>kicks in.
That's fairly typical for a low end consumer router. I have a home
made power line logger running at my palatical office looking for
power line glitches. It's fairly crude and only catches the big
glitches. We've had major two power glitches in the area during the
last week. I've been getting calls for dealing with hung routers,
modems, and computahs all week. It sometimes takes several days for
the effects of the glitch to show up. All that needs to happen is for
the glitch to trip one bit in RAM. No problem until the device needs
to use that bit. Then, it goes nuts. ECC RAM is not used on
commodity routers.
>So, maybe that's what happened.
Highly likely. I can see a wireless attack in a crowded metro area,
but not in the sparcely populated hills. Attacks from the internet
are possible, but unless the router has some built in vulnerabilities,
is grossly misconfigured, or is sensitive to malformed packets, it's
not going to happen. Just in case, try:
<
http://www.pcflank.com/exploits.htm>
It's old and incomplete, but I'm still finding modern routers that
fail some of the exploit tests.
>But, now it's even worse. With the router reset to defaults, I had no
>problem logging in. I decided to update the firmware, just in case, using
>the file FW_WRT54Gv5v6_1.02.8.001_US_20091005.bin downloaded from the
>Linksys site for the v5 that I have.
>
>This process went on for hours ... from about 11:00 to about 1:30 when I
>finally gave up and pulled the plug. (BTW, how long 'should' a firmware
>upgrade take anyway?).
The update should take about 60 seconds plus reboot time. Something
went wrong. Hopefully, you didn't try to do the upgrade via a
wireless connection. That's usually a guaranteed disaster.
Checking the web site, you have the correct version:
<
http://homesupport.cisco.com/en-us/support/routers/WRT54G>
No checksum, so I have no way to verify if it was correctly
downloaded. You might want to try another download just to be sure.
>Now I can't get anything to work on the Linksys router. No connection.
It's bricked, but probably not fatal.
>Two questions:
>Q1: How long should it take for firmware to install itself?
>(I gave up after almost 3 hours)
About 60 seconds plus a reboot.
>Q2: Should the power light be constantly blinking or should it be steady?
>(Mine is blinking)
Nope. That means there's a checksum error in the firmware.
I would normally consider this a great opportunity to purchase a new
router and get rid of the v5 abomination. However, if you want to
raise the dead, try this simple test:
1. Power OFF the router.
2. Temporarily set your computah to a static IP address of
192.168.1.99.
3. Start a continuous ping to 192.168.1.1 For Windoze, that's
ping -t 192.168.1.1
Don't worry if you see errors at this point. If you don't have TFTP:
<
http://www.dd-wrt.com/dd-wrtv2/downloads/others/tornado/Windows-TFTP/tftp2.exe>
IP=192.168.1.1
no password - leave blank
select the firmware
set retries to 99
4. Apply power to the router. You should see proper returns from the
pings after about 8 seconds. The returns will revert to errors after
about 5 more seconds. Try to record the times. You'll need them.
5. If you get proper returns in the previous step, there is hope.
6. Rename the firmware to "code.bin". This might also be a good time
to try loading the mini version of DD-WRT.
7. Under Windoze, type the following onto the command line (in a cmd
window):
tftp -i 192.168.1.1 PUT code.bin code.bin
Do not hit enter quite yet. Do not hit enter quite yet. Do not hit
enter quite yet. Do not hit enter quite yet. Got that? If you're
using tftp book, get ready to hit the start button.
8. Apply power to router and start counting seconds. The idea is to
start the TFTP program in the middle of when the pings were correctly
returned. You may have to do this several times to get it right.
9. When you hit enter, nothing should happen until code.bin is
properly uploaded. You'll get a message about ok to reboot (it varies
with the firmware). Ignore it and do nothing for at least 5 minutes.
Go get some coffee and keep your fingers off the keyboard. After 5
mins, pull the power to the router, wait for it to boot, and see if
you can get to the management page at 192.168.1.1.
10. If that works, don't foget to change the static IP address of the
computah back to DHCP. If it doesn't work, try again, or just get a
better router.
Some notes (and complications):