We are seeing a crash in batmand (beta, rv767-792) on kamikaze 7.09 /
atheros 2.6 / mips.
I am trying to get a core dump for Marek, but no file is created despite
doing ulimit -c 20000.
Does anyone know what must be done to get a core dump on this platform?
[mailto:email@example.com] On Behalf Of Axel Neumann
Sent: Sunday, November 11, 2007 9:16 AM
To: The list for a Better Approach To Mobile Ad-hoc Networking
Subject: Re: [B.A.T.M.A.N.] routing problem? / Changes in exp rv790
Now I have other question about routing...
I have 4 nodes: A,B,C and D
fromA> D via B dev ath0 proto static
fromD> A via C dev ath0 proto static
I have difficulties to clearly understand
the last two lines.
Is this what routing table 66 or table 65 tells you at node A and D.
its easier if you just paste the command and output of the command which
revealed this information, might also simplify to find other reasons for
In this sense, one question? Do you use different networks/netmasks for
different links. Because this might be one reason for problems.
The thing is:
when the batman network of node A is different from the batman networks
by node D then D will not search its routing table 66 for the
route to node A. Even if the correct route form D to A is listed by the
command: ip r ls t 66
The problem are the rules which are configured by the batman daemon.
The command: "ip rule" on node D might show something like:
0: from all lookup local
6599: from all lookup 65
6600: from all to x.y.D.0/24 lookup 66
32766: from all lookup main
32767: from all lookup default
while on node A it might show the same except for one line:
6600: from all to x.y.A.0/24 lookup 66
Rule 6600 tells the network layer to only search table 66 for certain
destinations. And if D is searching for a destination in x.y.A.0/24 it
not fit :-(.
Anyway, because there has been so much confusion about this, i changed
with exp 0.3 revision 790. The daemon now configures the critical rule
6600: from all lookup 66
No more restrictions for table 66. This should always fit.
Since revision 790, also the unreachable rule is omitted by default,
been another reason for confusion.
If you (or others) want to have back the old unreachable rules or the
restrictive mask for table 66, the daemon may be started with the
When A talk to D choose B while when D talk to A choose C.
In this scenario node D can't talk to A for example with ping.
does ping really
Is correct this type of routing?
Why not? According to your setup, both routes
would work. This would be
typical case for asymmetric routing. But generally nothing speaks
such a route.
B.A.T.M.A.N mailing list
B.A.T.M.A.N mailing list