Hi guys,
Ok, and the second bug, which has been there even before the 0.2 release if I remember right, is, that seemingly random entries in the vis-servers output are missing, even when having a setup with single-interface nodes only. The probability seems to increase the more nodes are in the mesh network. For instance, I'm right now running a setup of 4 wifi routers + my laptop with the current batman-adv maintenance version with my last vis patch. They are all right next to each other and connected over wifi, therefore they're all in the same neighbourhood. No downloads or any other highly disturbing wifi traffic around.
With just 3 routers, there are only missing entries from time to time, but with 5 devices, there is usually always at least one entry missing. For example:
----------------------------------------------------------------- sh-4.1# ./batctl vd dot && ./batctl o digraph { "06:22:b0:98:94:0b" -> "06:22:b0:98:87:f9" [label="1.20"] "06:22:b0:98:94:0b" -> "06:22:b0:44:c6:59" [label="1.0"] "06:22:b0:98:94:0b" -> "00:13:e8:50:c0:ff" [label="1.0"] "06:22:b0:98:94:0b" -> "06:22:b0:44:94:5d" [label="1.20"] "06:22:b0:98:94:0b" -> "00:22:b0:98:94:0b" [label="HNA"] "06:22:b0:98:94:0b" -> "02:c7:5f:09:af:0f" [label="HNA"] subgraph "cluster_06:22:b0:98:94:0b" { "06:22:b0:98:94:0b" [peripheries=2] } "06:22:b0:98:87:f9" -> "06:22:b0:98:94:0b" [label="1.20"] "06:22:b0:98:87:f9" -> "06:22:b0:44:c6:59" [label="1.71"] "06:22:b0:98:87:f9" -> "00:13:e8:50:c0:ff" [label="1.32"] "06:22:b0:98:87:f9" -> "00:22:b0:98:87:f9" [label="HNA"] "06:22:b0:98:87:f9" -> "9e:03:d3:3e:3e:15" [label="HNA"] subgraph "cluster_06:22:b0:98:87:f9" { "06:22:b0:98:87:f9" [peripheries=2] } "06:22:b0:44:c6:59" -> "06:22:b0:98:87:f9" [label="1.15"] "06:22:b0:44:c6:59" -> "00:13:e8:50:c0:ff" [label="1.28"] "06:22:b0:44:c6:59" -> "06:22:b0:44:94:5d" [label="1.80"] "06:22:b0:44:c6:59" -> "46:b4:01:60:f6:57" [label="HNA"] "06:22:b0:44:c6:59" -> "00:22:b0:44:c6:59" [label="HNA"] subgraph "cluster_06:22:b0:44:c6:59" { "06:22:b0:44:c6:59" [peripheries=2] } "00:13:e8:50:c0:ff" -> "06:22:b0:98:87:f9" [label="1.3"] "00:13:e8:50:c0:ff" -> "06:22:b0:98:94:0b" [label="1.28"] "00:13:e8:50:c0:ff" -> "06:22:b0:44:c6:59" [label="1.36"] "00:13:e8:50:c0:ff" -> "06:22:b0:44:94:5d" [label="1.53"] "00:13:e8:50:c0:ff" -> "2e:bb:47:5b:b1:5e" [label="HNA"] subgraph "cluster_00:13:e8:50:c0:ff" { "00:13:e8:50:c0:ff" [peripheries=2] } "06:22:b0:44:94:5d" -> "06:22:b0:98:87:f9" [label="1.0"] "06:22:b0:44:94:5d" -> "06:22:b0:98:94:0b" [label="1.89"] "06:22:b0:44:94:5d" -> "06:22:b0:44:c6:59" [label="1.28"] "06:22:b0:44:94:5d" -> "00:13:e8:50:c0:ff" [label="1.49"] "06:22:b0:44:94:5d" -> "00:22:b0:44:94:5d" [label="HNA"] "06:22:b0:44:94:5d" -> "da:ef:64:a7:33:a7" [label="HNA"] subgraph "cluster_06:22:b0:44:94:5d" { "06:22:b0:44:94:5d" [peripheries=2] } } Originator (#/255) Nexthop [outgoingIF]: Potential nexthops ... [B.A.T.M.A.N. adv 0.2.1-beta, MainIF/MAC: wlan0/00:13:e8:50:c0:ff] 06:22:b0:98:87:f9 (252) 06:22:b0:98:87:f9 [ wlan0]: 06:22:b0:98:87:f9 (252) 06:22:b0:98:94:0b (232) 06:22:b0:44:94:5d (232) 06:22:b0:44:c6:59 (229) 06:22:b0:98:94:0b (249) 06:22:b0:98:94:0b [ wlan0]: 06:22:b0:98:94:0b (249) 06:22:b0:44:94:5d (217) 06:22:b0:98:87:f9 (235) 06:22:b0:44:c6:59 (234) 06:22:b0:44:c6:59 (246) 06:22:b0:44:c6:59 [ wlan0]: 06:22:b0:44:c6:59 (246) 06:22:b0:44:94:5d (221) 06:22:b0:98:94:0b (229) 06:22:b0:98:87:f9 (225) 06:22:b0:44:94:5d (242) 06:22:b0:44:94:5d [ wlan0]: 06:22:b0:44:94:5d (242) 06:22:b0:98:94:0b (225) 06:22:b0:98:87:f9 (212) 06:22:b0:44:c6:59 (227) sh-4.1# -----------------------------------------------------------------
I'd expect all 5 nodes to have a direct connection to all other 4 nodes. However, for instance 06:22:b0:98:87:f9 is just having three. A couple of seconds later, the missing entry is there again, but other ones can be missing.
What I also just noticed is, that when I refresh the vis-output every second only the TQ values of _2_ entries at a time get updated, the other ones are static for quite a while. However, looking at wireshark tells me, that I'm still getting a vis-packet of all other 4 nodes every second. So it looks like the vis-server might not be always updating its vis_hash to me, but not sure about that.
I'm also attaching a capture on the laptop's wifi interface while I had been sending ping-floods to ensure that the tq-values should be changing frequently (which is not the case according to the vis-server-output).
Cheers, Linus