OpenWrt Forum Archive

Topic: Failsafe mode in ASus wl500g

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

Hi!

I crashed my WL500g with OpenWRT.

I tried to reflash the firmware with OpenWRT, it didnt work. How I get into Fail safe? there is no DMZ light as documented.

what i did for Failsafe:
pressed the reset button upto 5 and 10 second, and tried to get access from WAN port, but didnt work. cant  do ping either.


what should i do now? may be  i need a right failsafe sequence ?

Please, reply

Regards,

Try it from LAN1

Use ASUS firmware restoration tool to reflash firmware.

Thank you very much guys for your reply. I want to mention something here which is a bit contrast from given manual. In my case when I got into fail safe mode, I got telnet reply in LAN port rather than WAN(as it was written in documentation reply will be on WAN port). I am not sure about the exact time to keep the button pressed but anyways it is definetly a 10 sec or a bit longer.  According to documentation ASUS router should revert into the LAN ip address, which I set 10.10.10.10, but in this case it reverts into the defualt IP of router 192.168.1.1.

Regards and thanks.

I'm using WhiteRussian RC2 SquashFS on a WL500g.  I seem to be able to get it to go into Failsafe mode - I can see the PWR led flashing, and I can ping the router on it's LAN_IPADDR (192.168.107.1) address.  I can't ping it on 192.168.1.1 (I set my PCs interface to 192.168.1.2/24) and I can't telnet into it.  I've port-scanned it and there are no ports open - nmap reports all ports filtered.

I can't ping any IP address on the physical WAN port - but I had it unconfigured anyway.  I had the radio in client mode and it still seems to be in client mode when in failsafe mode because I can't see it pop up as an AP in a wireless network scan.

I can't get into the WL500g because I foobar'd the /etc/init.d/S50dnsmasq file.

I put

 args="-d -l /tmp/dhcp.leases -K -F $(int2ip $start),$(int2ip $end),$(int2ip $netmask),12h 2>&2 >/dev/null &"

in it instead of the usual args line.  I was trying to fix the dnsmasq bug described here and obviously got my shell things mixed up.  So now all the init files after S50dnsmasq won't run at boot - meaning S50dropbear doesn't get executed.

But in Failsafe mode, the router should ignore my edited file and use the one in /rom/etc/init.d/ shouldn't it?  And telnet should be enabled, right?

I'd rather not have to reflash the firmware if I don't have to, but right now it seems that failsafe mode has failed me.  Any suggestions?

Update:

The flashing PWR led isn't Failsafe mode on the WL500g - it's the firmware recovery mode.  If you hold down reset before connecting power, or immediately after, you go into a mode whereby you can upload a new firmware.  The router IP address is the LAN_IPADDR that was set by the user - so if you mess up that NVRAM variable you might be in trouble.

I ended up reflashing WhiteRussian RC2 SquashFS - it didn't do firstboot after reflashing so I manually rebooted it.  I wasn't able to telnet in straight away - I don't know why, but after reflashing I was able to get the WL500g into OpenWRT Failsafe mode by the usual method - rebooting, waiting about 3 seconds, and pressing the reset button for a few seconds.  The router's LAN IP came up as 192.168.1.1 and I was able to telnet in.  By doing a "df -h" I was able to see that firstboot had not yet run - there was no JFFS2 partition.  I ran firstboot manually and rebooted.  The router was is now back to normal - minus all the packages and configuration I had put on it.  I have found that after firstboot has run I am unable to put the router in Failsafe mode.  I have tried waiting various amounts of time after power-on, and tried pressing the reset button for various amounts of time but I can't get it to work.   The only conclusion I can come to is that for some reason, under WhiteRussian SquashFS RC2, Failsafe on a WL500g doesn't work after firstboot has been run - which sort-of defeats the purpose of Failsafe mode. smile  I don't have any more time to experiment with this, but I'd appreciate it if someone else with a WL500g could have a go at getting Failsafe mode to work.  And if you get it to work, please tell me how!

In the meantime, I'm going to get a USB-serial adaptor to work so I have a backdoor in case I foobar the network init scripts again. smile

The discussion might have continued from here.