OpenWrt Forum Archive

Topic: wrt54gl semi-bricked (kamakaze 7.06 bdcm2.4)

The content of this topic has been archived on 12 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,

I have semi-bricked my wrt54gl v1.1 somehow when setting up kamakaze 7.06.

Firstly, the tftp bootup wouldn't work with the stock firmware, so I instaleld the

firmware using the stockfirmware's web admin thing - it worked, rebooted.
I telneted to the machine on 192.168.1.1, set the admin password and quit telnet.
i then ssh'd into the box fine using root/password.

I edited the /etc/config/network file and changed the ip address from 192.168.1.1 to

10.0.0.1. and added Option Gateway 10.0.0.5 (which is the main router to the internet)
saved the file and dropped back to the prompt.

now, without thinking I did ifconfig down eth0.0, which as you can imagine killed the

ssh session.

I unplugged the power from the router, and plugged it back in, hoping that it'd

reconnect eth0.0 and would be up and running again.

Since then I have been unable to connect to the router using IP.
-------------

All four lan ports work fine as a network switch, the wan port if plugged in requests an

IP from the dhcp server and pings fine - but everything on that IP is firewalled.

When it boots up it broadcasts 192.168.1.0/24 port 4919 !Press reset now, to enter

Failsafe!  - however, pressing the reset button on the back does nothing at all and it

will not drop back to failsafe.

wifi is turned off (I didn't set this up yet)

I still can't use tftp to install a firmware on it, it either times out or gives an

error saying "Error in recfrom() call." I have tried this directly plugging the wrt54gl

into my laptop's ethernet port and through another switch

Altho, after the router boots up I do have a record in my arp cache saying that

192.168.1.1 is the mac address of the router - but I have a feeling that IP is only

there for about 1/2second because of the amount of trouble getting it to even ping let

alone getting tftp to do anything but a timeout
--------------

I'm at the end of everything I've done so far and not sure what to do next.
But I have learnt how to bridge to network cards in WinXP :)

The discussion might have continued from here.