Hi Georg, On Wed, 18 Oct 2006 at 10:46 +0200, Georg C. F. Greve wrote: > Hi all, > > I've been looking at FreeWRT for some time now, but while it is now > compiling fine without errors (SVN version 952 was the last I tried) > and I can tftp the image to the router, I could never log into the > routers or get it to actually respond. > > Not even ping seems to work reliably, when trying to ping the router > (ASUS WL-500gP in this case), I get the following result: > > [EMAIL PROTECTED]:/tmp/FreeWRTsvn952/bin$ 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=100 time=0.929 ms > 64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.04 ms > 64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=0.360 ms > 64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=0.541 ms > 64 bytes from 192.168.1.1: icmp_seq=13 ttl=100 time=610 ms > 64 bytes from 192.168.1.1: icmp_seq=14 ttl=100 time=0.442 ms > 64 bytes from 192.168.1.1: icmp_seq=15 ttl=100 time=440 ms > 64 bytes from 192.168.1.1: icmp_seq=16 ttl=100 time=0.446 ms > 64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=1.04 ms > 64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=0.349 ms > 64 bytes from 192.168.1.1: icmp_seq=28 ttl=100 time=244 ms > > Self-compiled OpenWRT has no problems, at all. I think that others are > using FreeWRT successfully, so I wonder what I'm missing. > > Any ideas?
One idea is, that you have choosen a configuration in menuconfig, saved it and then switched to another filesystem or target device afterwards. After that your compiled image will be broken. This ugly behavior is fixed in the latest svn version. I think I committed the changes on Tuesday in the late evening. I use FreeWRT stable branch on at least 5 Asus WL500gP devices without problems. Last time I had major problems was exactly after I changed the filesystem without removing ".config" before. If you change from OpenWrt to FreeWRT you always should use mtd to update the system in flash. Otherwise FreeWRT might try to mount an existing JFFS2 partition with startup scripts which do not work. Use following command: # mtd -r write freewrt-xx.bin linux There is one other possibility to get access to the FreeWRT system. Try the failsafe mode. In failsafe mode FreeWRT does not try to mount any other filesystems, it just spawns a telnet daemon on 192.168.1.1. How to get into failsafe? Startup the failsafe application in ./staging_dir_mipsel/bin/failsafe and bootup the embedded system. FreeWRT will send one UDP package to your connected client to signal that you can push the reset button. If you push the button at the correct time, FreeWRT will go into failsafe. But there is still one situation, where it does not help. In case there is an old partition the kernel use to execute the "nvram" binary (in preinit.arch), failsafe can not be reached. So in short: - remove .config - svn up - build a new image - install original firmware via tftp - use the webinterface to install the new FreeWRT image good luck Waldemar -- don't open your wrt, free it http://www.freewrt.org _______________________________________________ freewrt-users mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-users
