I've read through all the forums re: "de-bricking", resetting, etc. but haven't found anything that solves my problem.

I screwed up and didnt set boot_wait.

I CAN: I have a wap54g 1.1. Wifi is working with default settings. I can ping 192.168.1.245. I can open said IP in browser -  I get "No webpages currently available - perhaps you need to install a pakeage?"

I CANNOT: Telnet, or TFTP, or figure out the pin short method.

If anyone has been in a similar circumstance and has successfully recovered their AP, your help is appreciated.

EXACT same problem here,but with Xarp i can see the mac adress of the router when i ping 192.168.1.245 but is wrong with 00-11-22-33-44-56 and if i ping 192.168.1.1 i get 00-00-00-00-00-00 from the lan port, with wifi i can connect like junglerotkid but no ping telnet http... try the tftp thing dunno if its timing issue but i try with with 2 os linux (in vmware) and winxp and the tftp command timout. Any hack to reset or reflash my WAP54G v1.1 from serial port? pin shorting (realy not sure about this one)

try to force mac adress with arp -s MACADDRESS 192.168.1.245
and with arp -s MACADDRESS 192.168.1.1
no success
i use the mac adress writen on the pcb board

try on the wifi port to with the mac adress of the minipci card with my laptop

no ping reply http telnet ...

So do you think my unit is dead?

Any sugestion will be try thx

Xarp --- http://www.chrismc.de/developing/xarp/

Hello!
      I'm using a WRT54GL v1.1 with RC6 and have encountered a problem that sounds similar to the previous [old/ignored] posts - and I believe in recycling.

I screwed-up firewall.user, so pwr-cycled and pressed reset (after DMZ LED came on.)  Next boot, the router started showing a LAN-side MAC address of 00-00-00-00-00-00 - like this, ping and telnet don't work, however, if I press reset while booting (after DMZ LED comes on) the router will show a non-zero MAC address and ping and telnet work!

During all this I've tftp'd a new RC6 bin, and run "firstboot" - MAC address always shows 00-00-00-00-00-00 after boot.  It seems some exceptional/unusual action is needed - assuming it's possible to get the router out of this state.

Any ideas(AKA: "charity") would be appreciated!

Cheers!

(Last edited by booboo on 3 Jul 2007, 21:05)