Weird Issues

7 posts / 0 new
Last post
Serv007
Serv007's picture
Weird Issues

I upgraded my firmware and now my router has a steady green power light, amber test light, and no wireless.  The thing is I can still ping the router but yet I can't access it in at all.  I still haven't tried using a serial console though.  Any help would be appreciated.

Serv007
Serv007's picture
I have been playing around

I have been playing around some more and realized that I can do nothing but ping, no ftp, and no web gui.

I have the dead wgr614l hooked up to a wrt54gl right now so I can have internet but the 192.168.1.1 is the dead one.

 

blackmacbook
blackmacbook's picture
If you can ping the router,

If you can ping the router, then what was the need to use the serial cable?  If the router is pingable, you can tftp back to the default netgear firmware.

Serv007
Serv007's picture
Me nor any of the people I

Me nor any of the people I work with can get it to tftp we have tried with xp and a router and with just OS X. I am just going to make a voltage divide circuit instead of buying a cable.

SouvikGhosh
SouvikGhosh's picture
Please do not use any cable

Please do not use any cable other the one suggested by Brandom this may brick your router. Please refer to the link below -
http://www.myopenrouter.com/article/10341/Recover-Your-WGR614L-Using-a-S...

SouvikGhosh
SouvikGhosh's picture
Another thing is your power

Another thing is your power LED is blinking? Actually since you can ping the router but not been able to access the UI I may assume that there was some problem with your image checksum and bootloader discarded this image to load and waiting in tftp listen state. In this state the Power led of your router should blink. If this is the case then you should be able to upload any image using tftp.

Serv007
Serv007's picture
My power light never blinks

My power light never blinks it is steady and I have had two Computer engineers and a Software engineer look at it and we still don't really know what the hell it is doing. It looks like the bootloader may of somehow been trashed, don't know what could have done that.