Posted: Sat Oct 24, 2009 2:49 am Post subject: ASUS wl-500w not bricked, but bricked
I've got an Asus WL-500W that was (is) running EKO v24 TNG svn12533. At some point today, the kids unplugged it, probably for several hours. When I got home and plugged it back in, the AIR light wouldn't come on. It wouldn't ping over hard connection on either the custom address I've given it or the default. So I've done all the various resets - 30/30/30, Asus discovery/firmware tool, tftp, etc. I still get nothing (none of the update tools seemed to be able to get to the router, which makes sense given that I can't ping). I've had to return a WL-500W once before because it would spontaneously reboot, but this isn't acting like that one did.
When I power up, I get the power LED and any plugged in LAN ports (I get WAN too if I plug that in). When I ping, I see the LAN port blink, and the router doesn't flash all lights or anything. It's almost as if I just can't guess the right IP, though why that wouldn't get reset with a 30/30/30 is unknown. One oddity - when I put it in recovery mode and use the ASUS tool to push firmware to it, the timer starts counting up for ~3 seconds, and then JUMPS to saying "33 seconds" even though no time has passed. The router lights all blink, and then it's out of recovery mode, but the tool says upload failed.
Any suggestions for next steps? Thanks, and sorry if I've screwed up protocol in some way - I tried to read Peacock's sticky thread and such, but found nothing that I hadn't tried that seemed appropriate for this situation.
Set network adapter to static IP of 192.168.1.10, subnet mask to 255.255.255.0 and default gateway 192.168.1.1. Also unplug WAN cable and everything but LAN1....
Enter dos command prompt and do a ping -t 192.168.1.1
See what happens... _________________ Asus WL520gU
Posted: Sat Oct 24, 2009 6:19 pm Post subject: Ping
I'm very familiar with TCP/IP, so I'm confused but confident: when I ping 192.168.1.1, I get "Destination host unreachable". I am SURE of the IP and subnet mask on the PC, and I've rebooted just to be super sure of the TCP stack in Windoze. It takes a while per packet to do it, so I read it as a timeout. Power supply measures ok, but without opening the router that's all I know (I'll do that if I have to, but not sure if this might still be in warranty).
Posted: Sun Nov 08, 2009 3:26 am Post subject: No joy
Finally got back around to this. I setup the wired NIC as IPs on all three subnets I thought the thing might be - 192.168.0.2, 192.168.112.2, 192.168.1.2. I opened up 3 prompts and ran "ping -t" to each of the .1's on the subnets. I did a 30-30-30. At no point in that process did anything reply.
Another note - I put wireshark on the net card. Not a single packet is sent by the router it seems. Yet when I ping, I see the light on the Asus flicker.
