Project

General

Profile

Actions

Support #196

closed

batadv-vis vs batctl o vs alfred

Added by Luca Postregna over 9 years ago. Updated about 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
09/23/2014
Due date:
% Done:

0%

Estimated time:

Description

Hi all,
I have a problem with my little batman-adv mesh network.
On my local node I get:

@kino:~

batctl o

[B.A.T.M.A.N. adv 2014.3.0, MainIF/MAC: enp1s0.3/00:05:1c:06:35:8e (bat0 BATMAN_IV)]
Originator last-seen (#/255) Nexthop [outgoingIF]: Potential nexthops ...
b0:48:7a:d1:fb:e0 0.612s (255) b0:48:7a:d1:fb:e0 [ enp1s0.4]: b0:48:7a:d1:fb:e0 (255)
90:f6:52:f2:8c:2c 0.471s (255) 90:f6:52:f2:8c:2c [ enp1s0.3]: 90:f6:52:f2:8c:2c (255)
90:f6:52:f2:8c:2d 0.710s (251) 90:f6:52:f2:8c:2c [ enp1s0.3]: 90:f6:52:f2:8c:2c (251)
a0:f3:c1:ac:6c:44 0.441s (225) 90:f6:52:f2:8c:2c [ enp1s0.3]: 90:f6:52:f2:8c:2c (225)
10:fe:ed:37:3a:39 0.981s (240) 90:f6:52:f2:8c:2c [ enp1s0.3]: 90:f6:52:f2:8c:2c (240)
a0:f3:c1:96:94:06 0.481s (240) 90:f6:52:f2:8c:2c [ enp1s0.3]: 90:f6:52:f2:8c:2c (240)

kino:~

cat /etc/local.d/alfred.start

alfred -i br0 -m -b bat0 &
batadv-vis -s -f dot &

kino:~

batadv-vis -f dot

digraph {
subgraph "cluster_00:05:1c:06:35:8d" {
"00:05:1c:06:35:8d"
"00:05:1c:06:35:8e" [peripheries=2]
}
"00:05:1c:06:35:8d" -> "b0:48:7a:d1:fb:e0" [label="1.000"]
"00:05:1c:06:35:8e" -> "90:f6:52:f2:8c:2c" [label="1.000"]
"00:05:1c:06:35:8d" -> "00:18:7d:0b:b3:31" [label="TT"]
"00:05:1c:06:35:8d" -> "42:07:48:68:58:82" [label="TT"]
"00:05:1c:06:35:8d" -> "42:07:48:68:58:82" [label="TT"]
"00:05:1c:06:35:8d" -> "00:11:22:b2:e7:7d" [label="TT"]
"00:05:1c:06:35:8d" -> "24:a4:3c:47:53:9a" [label="TT"]
"00:05:1c:06:35:8d" -> "dc:9f:db:0b:af:b9" [label="TT"]
"00:05:1c:06:35:8d" -> "dc:9f:db:f1:d8:a7" [label="TT"]
}@

And in all others nodes I have batadv-vis and alfred up and runnig, for example:

@root@franz:~# batctl o
[B.A.T.M.A.N. adv 2014.2.0, MainIF/MAC: eth0.8/10:fe:ed:37:3a:39 (bat0 BATMAN_IV)]
Originator last-seen (#/255) Nexthop [outgoingIF]: Potential nexthops ...
90:f6:52:f2:8c:2b 0.170s (254) 90:f6:52:f2:8c:2b [ eth0.8]: 90:f6:52:f2:8c:2b (254)
00:05:1c:06:35:8e 0.380s (240) 90:f6:52:f2:8c:2b [ eth0.8]: 90:f6:52:f2:8c:2b (240)
b0:48:7a:d1:fb:e0 0.710s (222) 90:f6:52:f2:8c:2b [ eth0.8]: 90:f6:52:f2:8c:2b (222)
90:f6:52:f2:8c:2d 1.000s (255) 90:f6:52:f2:8c:2b [ eth0.8]: 90:f6:52:f2:8c:2b (255)
a0:f3:c1:ac:6c:44 0.920s (255) a0:f3:c1:ac:6c:44 [ eth0.8]: a0:f3:c1:ac:6c:44 (255)
a0:f3:c1:96:94:06 0.940s (240) 90:f6:52:f2:8c:2b [ eth0.8]: 90:f6:52:f2:8c:2b (240)

root@franz:~# ps
...
1051 root 1108 S /usr/sbin/alfred -i br-mesh -m -b bat0
1057 root 1236 S /usr/sbin/batadv-vis -i bat0 -s
...@

why on my local node batadv-vis doesn't display complete topology?
can anybody help me about?

Actions #1

Updated by Sven Eckelmann over 9 years ago

Can these nodes actually reach each other via IPv6 link-local UDP messages over br0? Is br0 the bridge which has bat0 as a slave interface?

Why has one node br0 and the other br-mesh as communication interface?

Actions #2

Updated by Marek Lindner about 9 years ago

  • Status changed from New to Closed

Closed to due inactivity. Feel free to re-open if the issue persists.

Actions #3

Updated by Sven Eckelmann about 7 years ago

  • Status changed from Closed to Rejected
Actions

Also available in: Atom PDF