Zitat von elektra <onelektra(a)gmx.net>et>: [Zitattext verstecken] Hi - Routing is working and there is enough memory. I have setup a cron job to call "batmand -c -d [2,7,8,9]" every minutes to update the status files on ramdisk. The webinterface then access the content of the status file which reduces the cpu load. just a stupid question to verify things - you have not forgotten to add -b for batch mode to the command? yes, you are right. I just forgot this option in the previous post. The firmware uses the -b option. When I create the firmware I'm using the whiterussian kit 1.4.5. It generates the same firmware for different routers. So when I flash the WRT54GS and the WRT54GL with the same firmware, the WRT54GL batmand hangs. There are still 2Mbyte Ram unused. restarting batman does almost not change the memory consumtion. I use the "top" command for this. I have made a log when the batmand stopps. Perhaps it helps you a little. http://www.ddmesh.de/batmand-hanglog.txt /Stephan

Hi Axel, The crontab contains an entry such like: 0-59/1 * * * * /etc/init.d/S53batmand check this calles the following commands after another: batmand -cb -d2 >/tmp/batmand_gateway batmand -cb -d7 >/tmp/batmand_gateway batmand -cb -d8 >/tmp/batmand_gateway batmand -cb -d9 >/tmp/batmand_gateway But I also did put these commands into an loop: while true; do batmand -cb -d2;....;done I have also disabled this "logging" completely and let only run batmand to build up the net. I can not say if the access to the debug output leads to blocking the batmand faster.I also have seen that batmand blocks after awhile if it is only running for building the network. I have put a logfile on my webpage. http://www.ddmesh.de/batmand-hanglog.txt In one of the previous threads someone had a problem with "batmand going crazy". I'm not sure to remember right. But I think that it had to do with sequence number that's wrapping around. The logfile ends at the time batmand stopps. At the end of this log you will find something like "prevRxSeqno: 0, currRxSeqno-prevRxSeqno 0," perhabs it is the same reason. batmand is currently started with two interfaces eth1 and tbb. eth1 is the wireless interface and tbb is a tun/tap device that is used by vpn tincd. tincd has got invalid hostnames, so it never creates a connection. Perhabs batmand has a problem with this kind of "dead" interfaces. I have tried to remove this tbb interface when starting batmand. batmand was running at least for two days. But the "dead" interface may also have no influence to this problem. Currently batmand is running since 10 hours with eth1 and tbb (dead interface). I never have seen this problem with the WRT54GS, only with GL. /Stephan

Hello, my last 10h log (with tap dev) was also crashing. I'm currently let run without the tap dev since few hours. I like to run it longer. I have looked at that, but did not find any strange log The number of task are the same. But I have seen, that when the -d4 output stopps and I keep this batmand running when accessing an different log level from another terminal, I see the socket-connection logs in -d4 output. Also I still can just call "batmand -c" to see the parameters and current gateway settings. I also can change the gateway settings. The batmand seems to stop processing any OGMs. I haven't tried it, yet. but this also came in my mind. I will this check after finishing the "no-tap-dev-test" I can not say, because implementing tinc and updateing the batmand version was at same time. Yes, the GL is running standalone with stubid tincsetup and also the GS was running with same parameters and standalone (no network cable). Perhaps it is more random and is depending on speed of the router when the event occurs. bye Stephan