Ticket #343 (closed defect: invalid)

Opened 1 year ago

Last modified 1 year ago

No way to connect to failsafed device (ASUS WL500g)

Reported by: greve@fsfeurope.org Assigned to: wbx
Priority: minor Milestone: 1.x (low prio)
Component: general Version: trunk
Keywords: failsafe Cc:

Description

Hi all,

I have an ASUS WL500g, which I can flash with a new image (from WiB), but never reach it by any means. My suspicion was a broken fwcf, so I did the following:

  • Reflashed original firmware (which worked fine) -- reflashed FreeWRT, same problem
  • Flashed OpenWRT (which worked fine) -- reflashed FreeWRT, same problem

On the grounds of that I then tried to put the device into failsafe mode (on FreeWRT).

Here is the output:

greve@cerebro:$ ./failsafe Msg from 192.168.1.1: Press reset now, to enter Failsafe! Msg from 192.168.1.1: Entering Failsafe!

greve@cerebro:$ ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=4.88 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.820 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.655 ms

--- 192.168.1.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.655/2.120/4.886/1.957 ms

greve@cerebro:/tmp/freewrt/tools/failsafe/src$ nmap 192.168.1.1

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2007-06-24 10:55 CEST mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using --system-dns or specify valid servers with --dns_servers All 1680 scanned ports on 192.168.1.1 are closed

Nmap finished: 1 IP address (1 host up) scanned in 2.094 seconds

As you can see, entering failsafe seems to work fine and while I could not ping the box when not entering failsafe mode, I can now ping it. But nmap shows that all ports are closed, so there is ultimately no way to connect.

Help appreciated.

Attachments

Change History

06/24/07 11:10:58 changed by greve@fsfeurope.org

As another application of murphy's law, the device became responsive after I filed this.

It seems that the key generation for SSH took longer than expected.

Maybe it would be useful to add something like

"Give your device some time to generate the SSH key before trying to connect, this can take several minutes."

to the failsafe output (and documentation).

Sorry for the wrong alert.

06/26/07 18:09:00 changed by wbx

  • status changed from new to closed.
  • resolution set to invalid.

Add/Change #343 (No way to connect to failsafed device (ASUS WL500g))




Action