It might give you some idea whether you have bricked the router or not. Do it while OpenWrt boots successfully. Compare the results while you have doubt. If you can see the ping replies, there might be a chance to access CFE/RedBoot or FailSafe mode without a serial cable.
Download fping.exe for Windows from http://www.kwakkelflap.com/fping.html. Windows users should also take care of "Media Sensing feature" or simply connect a dumb switch to keep the network interface always connected. Otherwise the network interface might take several seconds to initialize which could be much longer than boot_wait and you'll miss the opportunity to access the build-in tftp server of the router. Besides connecting a switch, sometimes a crossover ethernet cable is also necessary, especially for routers with a single ethernet port like La Fonera.
Open a command prompt. Run the following commmand before powering on the router. I suggest connecting a switching hub between pc and router so that the network interface of pc is always ready.
Numbers within the reply brackets are the ping sequences. The time between 2 pings is set by "-t" and timeout by "-w." Timeout is most important. You have to try different timeout values to access the build-in tftp server or catch the FailSafe signal.
Ping result of La Fonera+:
c:\>time 0:0 & fping 192.168.1.1 -l -T -c -s 1 -t 1000 -w 50
00:00:00 : 192.168.1.1: request timed out
...
00:00:01 : 192.168.1.1: request timed out
00:00:01 : Reply[30] from 192.168.1.1: bytes=4 time=15.1 ms TTL=64 #Reply from RedBoot
00:00:02 : Reply[31] from 192.168.1.1: bytes=4 time=0.8 ms TTL=64
00:00:03 : 192.168.1.1: request timed out
...
00:00:03 : 192.168.1.1: request timed out (4)
00:00:05 : Reply[40] from 192.168.1.1: bytes=4 time=4.9 ms TTL=64 #Reply from RedBoot at 00:00:05
00:00:06 : Reply[41] from 192.168.1.1: bytes=4 time=6.1 ms TTL=64 #Boot script timeout (1000ms resolution): 10
00:00:07 : Reply[42] from 192.168.1.1: bytes=4 time=5.3 ms TTL=64 #00:00:15 - 00:00:05 = 10 seconds
00:00:08 : Reply[43] from 192.168.1.1: bytes=4 time=5.4 ms TTL=64
00:00:09 : Reply[44] from 192.168.1.1: bytes=4 time=5.6 ms TTL=64
00:00:10 : Reply[45] from 192.168.1.1: bytes=4 time=5.8 ms TTL=64
00:00:11 : Reply[46] from 192.168.1.1: bytes=4 time=5.9 ms TTL=64
00:00:12 : Reply[47] from 192.168.1.1: bytes=4 time=6.1 ms TTL=64
00:00:13 : Reply[48] from 192.168.1.1: bytes=4 time=5.3 ms TTL=64
00:00:14 : Reply[49] from 192.168.1.1: bytes=4 time=5.4 ms TTL=64
00:00:15 : Reply[50] from 192.168.1.1: bytes=4 time=5.6 ms TTL=64
00:00:16 : 192.168.1.1: request timed out
...
00:00:29 : 192.168.1.1: request timed out
00:00:29 : Reply[284] from 192.168.1.1: bytes=4 time=3.5 ms TTL=64 #FailSafe packet received at 00:00:29
00:00:30 : 192.168.1.1: request timed out
...
FailSafe UDP packet:
Internet Protocol, Src Addr: 192.168.1.1 (192.168.1.1), Dst Addr: 192.168.1.255 (192.168.1.255)
User Datagram Protocol, Src Port: 44667 (44667), Dst Port: 4919 (4919)
Data: Press reset now, to enter Failsafe!
Ping result of ASUS WL-HDD2.5:
c:\>time 0:0 & fping 192.168.1.1 -l -T -c -s 1 -t 200 -w 200
00:00:00 : 192.168.1.1: request timed out
...
00:00:02 : 192.168.1.1: request timed out
00:00:02 : Reply[15] from 192.168.1.1: bytes=4 time=0.8 ms TTL=64 #PMON tftp server started at 00:00:02
00:00:03 : Reply[16] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64 #PMON tftp server @ 192.168.1.1
00:00:03 : Reply[17] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64 #PMON also accepts 192.168.1.220
00:00:03 : Reply[18] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64 #defined in NVRAM
00:00:03 : Reply[19] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64
00:00:04 : 192.168.1.1: request timed out
...
00:00:12 : 192.168.1.1: request timed out
00:00:12 : Reply[63] from 192.168.1.1: bytes=4 time=1.6 ms TTL=64 #While receiving the first icmp reply,
00:00:12 : Reply[64] from 192.168.1.1: bytes=4 time=0.9 ms TTL=64 #Press and hold reset button for at
00:00:13 : Reply[65] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64 #least 4 seconds to enter FailSafe mode.
00:00:13 : Reply[66] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64 #00:00:16 - 00:00:12 = 4 seconds
00:00:13 : Reply[67] from 192.168.1.1: bytes=4 time=0.6 ms TTL=64
00:00:13 : Reply[68] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64
00:00:13 : Reply[69] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64
00:00:14 : Reply[70] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64
00:00:14 : Reply[71] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64
00:00:14 : Reply[72] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64
00:00:14 : Reply[73] from 192.168.1.1: bytes=4 time=0.9 ms TTL=64
00:00:14 : Reply[74] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64
00:00:15 : Reply[75] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64
00:00:15 : Reply[76] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64
00:00:15 : Reply[77] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64
00:00:15 : Reply[78] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64
00:00:15 : Reply[79] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64 #FailSafe packet received at 00:00:16
00:00:16 : Reply[80] from 192.168.1.1: bytes=4 time=0.7 ms TTL=64 #Press reset now, to enter Failsafe!
00:00:16 : 192.168.1.1: request timed out
...
root@OpenWrt:~# nvram show | grep "192.168"
lan_ipaddr_t=192.168.1.220
dhcp_start=192.168.1.2
dhcp_end=192.168.1.254
lan_ipaddr=192.168.1.220
FailSafe UDP packet:
Internet Protocol, Src Addr: 192.168.1.1 (192.168.1.1), Dst Addr: 192.168.1.255 (192.168.1.255)
User Datagram Protocol, Src Port: 2048 (2048), Dst Port: 4919 (4919)
Data: Press reset now, to enter Failsafe!
OpenWrt / Bricked WRTSL54GS - Newb question
OpenWrt / DIR-300 Kamikaze 8.09 problem
(Last edited by fyi on 10 Oct 2010, 13:26)