OpenWrt Forum Archive

Topic: Unable to SSH or SCP in failsafe

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

I am able to telnet to the router (wrtsl54gs) in failsafe after setting my network properties to a static IP of 192.168.1.2. 

To change the passwd without errors I must first run firstboot on the router.  I change the password but then I cant telnet, ssh or scp - "connection refused."  tftp just times out.

I can ping 192.168.1.2 from the router and 192.168.1.1 from my pc.

Anybody have an idea about how to get my firmware.trx file transferred to it?

After many resets and hard reboots I was able to get in.  Im getting pretty good at this.  Its only taken me 6 hours to get back to where I was before it went bad.  Each time this happens it seems to be progressively worse.  Each time I think its busted for good. Then Im able to bring it back to life.

The lesson is: Do not "ipkg install kmod-lp" on a wrtls54g as part of step 3 in the printer sharing howto.http://wiki.openwrt.org/PrinterSharingHowto?highlight=(printer)|(sharing)#head-71b5de5812c9ab457edea4774a4533b6a87b6788

Ok now I think its busted for good.  I cannot get it into failsafe mode.  The SES light will not come on at all and the power light blinks rapidly.  I am able to ping it successfully but no telnet or ssh.  Anyone know what this means?

(Last edited by dawghed on 11 Jun 2008, 14:14)

Its back.  tftp the kamikaze bin at just the perfect moment. power, command, reset.  After countless tries.  I couldnt believe it.  the port light strobed for less than 10 seconds and it did its thing.  mtd whiterussian and now to try to get it back to the previous configuration before the disaster, 24 hours later.

The discussion might have continued from here.