Hi,
i've seen this behavior bevor, but couln't reproduce it until now:
If B.A.T.M.A.N.-III v0.1.1 beta2 (compability version 2) is startet with a -p(refered gateway) option and the given gateway is (at least) 2 hops away (may also not/-always/-directly reachable after start), batmand crashes.
This happens reproduceble ~30-60sec. after start. Until this point routes are written. No output. No purging of written routes.
Tests used: batmand -p <gateway> -r 2 eth1:bat br0:bat
With a 1-hop-to-prefered-gateway enviroment batmand seems to have no problems...
Regards Lui
Hi,
i've seen this behavior bevor, but couln't reproduce it until now: This happens reproduceble ~30-60sec. after start. Until this point routes are written. No output. No purging of written routes.
could you send a core dump and your binary ?
How to create a core dump: Connect to your device (via ssh) and type: ulimit -c 20000 Afterwards start batmand with a debug level > 0, e.g.: batmand -d 3 -p <gateway> -r 2 eth1:bat br0:bat Wait until it crashed and you will find a file named "core" in your current directory which represents the state of batman in the moment when it crashed.
Regards, Marek
b.a.t.m.a.n@lists.open-mesh.org
-
Lui -
Marek Lindner