* [B.A.T.M.A.N.] broadcast storms
@ 2018-10-22 13:07 Jake.Harris
2018-10-22 14:26 ` Simon Wunderlich
0 siblings, 1 reply; 8+ messages in thread
From: Jake.Harris @ 2018-10-22 13:07 UTC (permalink / raw)
To: b.a.t.m.a.n
[-- Attachment #1: Type: text/plain, Size: 1716 bytes --]
I'm sure a similar question to this has been answered, but I am new to this mailing list format and don't know an efficient way to search https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/
I'm having problems with broadcast messages effectively echoing around the network of 50ish nodes. I attached a few seconds of the batctl tcpdump output. I can't seem to find a pattern to what causes this, it tends to happen once every two or three weeks, the storm causes problems with the batman program where during the storm nodes drop all their neighbors (batctl n shows an empty list) indefinitely, which I have worked around that issue via a batch script that reloads batman if the neighbor list is empty. Reloading successfully reconnects to the network but the storm still persists.
The only way I've found to fix this is to reboot all the nodes at the same time such that the whole network is down to kill the echos.
I believe I had this problem much more frequently (every 4 days or so) a while ago on the same network when using discrete tcp destinations for the nodes to communicate, the storm frequency was reduced to what it is now by using broadcast packets and reducing the communication rate from 12 seconds to once every 40 seconds.
Rebooting the nodes that are responsible for the echoing messages has no effect, I rebooted 192.168.1.230 before running tcpdump that is attached and as it shows packets from 230 continued to bounce around while the node was powered off and after it rejoined the network. It doesn't appear broadcast uses a time-to-live parameter to limit the hops the packets will make.
I'm at a loss for a way to remedy this, there seems to only be multicast optimizations.
[-- Attachment #2: bat dump --]
[-- Type: application/octet-stream, Size: 52729 bytes --]
08:29:08.115107 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:08.119324 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:08.205002 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:08.621098 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:08.810210 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:08.940153 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:09.311924 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:09.494031 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:09.574937 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:09.583954 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:09.780270 IP 192.168.1.23.5007 > 192.168.255.255.5007: UDP, length 92
08:29:09.908730 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:10.107964 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:10.370808 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:10.400013 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:10.721533 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:11.084071 IP 192.168.1.23.5007 > 192.168.255.255.5007: UDP, length 92
08:29:11.179993 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:11.193189 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:11.215840 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:11.309026 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:11.379184 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:11.383624 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:11.399427 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:11.603180 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:11.604849 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:11.729243 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:11.735431 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:11.738976 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:11.881865 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:11.917740 IP6 fe80::e4d1:8cff:fe33:c120 > ff02::2 ICMP6, destination unreachable, unknown icmp6 type (133)
08:29:12.063963 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:12.142654 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:12.222906 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:12.229442 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:12.320131 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:12.362223 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:12.394770 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:12.517900 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:12.569720 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:12.579890 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:12.670376 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:12.735660 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:12.787027 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:12.795061 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:12.853707 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:12.855355 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:12.915206 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:13.020014 IP 192.168.1.10.5353 > 224.0.0.251.5353: UDP, length 190
08:29:13.113210 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:13.118828 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:13.131021 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:13.140689 IP6 fe80::8b0:c1ff:feb5:19c1.5353 > ff02::fb.5353: UDP, length 139
08:29:13.218779 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:13.361628 IPv6 unknown protocol: 0
08:29:13.378834 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:13.428149 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:13.516519 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:13.563267 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:13.572625 IPv6 unknown protocol: 0
08:29:13.618936 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:13.746020 IP 192.168.1.23.5007 > 192.168.255.255.5007: UDP, length 92
08:29:13.750090 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:13.837807 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:14.014158 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:14.024080 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:14.099211 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:14.248534 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:14.289237 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:14.428995 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:14.549172 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:14.553564 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:14.558365 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:14.563435 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:14.715033 BLA ANNOUNCE, backbone 68:1c:a2:08:3f:a4, bla group 1b6b, crc a90a
08:29:14.839025 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:14.858957 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:14.967703 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:14.979043 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:15.033517 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:15.088936 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:15.104105 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:15.133550 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:15.207838 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:15.229461 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:15.339343 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:15.429259 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:15.438679 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:15.539574 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:15.589069 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:15.609517 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:15.734094 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:15.848427 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:15.873581 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:15.913613 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:15.993827 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:16.047851 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:16.067621 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:16.213675 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:16.224157 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:16.294106 IP 192.168.1.23.5007 > 192.168.255.255.5007: UDP, length 92
08:29:16.298499 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:16.338384 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:16.437891 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:16.449111 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:16.544056 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:16.577866 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:16.823861 IP 192.168.1.23.5007 > 192.168.255.255.5007: UDP, length 92
08:29:16.939276 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:16.978635 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:17.068566 IP 192.168.1.23.5007 > 192.168.255.255.5007: UDP, length 92
08:29:17.212757 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:17.378297 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:17.433798 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:17.523533 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:17.567575 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:17.579200 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:17.682711 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:17.738298 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:17.907718 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:17.978627 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:18.663397 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:18.849185 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:18.869388 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:18.961763 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:18.967060 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:19.012805 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:19.148022 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:19.169422 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:19.275626 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:19.286921 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:19.305910 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:19.318810 IP6 fe80::f855:b1ff:fe2f:fafd > ff02::2 ICMP6, destination unreachable, unknown icmp6 type (133)
08:29:19.383565 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:19.394414 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:19.420163 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:19.447717 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:19.463867 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:19.483106 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:19.955265 IP 192.168.1.241.5007 > 192.168.255.255.5007: UDP, length 95
08:29:20.048872 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:20.060920 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:20.266125 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:20.276554 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:20.280155 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:20.333721 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:20.401813 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:20.431436 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:20.480636 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:20.544829 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:20.582377 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:20.634001 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:20.686021 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:20.689838 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:20.732738 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:20.743258 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:20.770490 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:20.834642 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:20.957083 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:21.003541 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:21.030671 BLA CLAIM, backbone 68:1c:a2:08:3f:a4, client d6:ec:ad:61:ad:e4, bla group 1b6b
08:29:21.030770 IP 192.168.1.42.5007 > 192.168.255.255.5007: UDP, length 99
08:29:21.066918 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:21.075680 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:21.151813 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:21.163052 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:21.251716 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:21.263044 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:21.319031 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:21.336788 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:21.372801 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:21.417213 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:21.452117 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:21.880868 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:21.997531 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:22.046460 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:22.100866 IP 192.168.1.190.5007 > 192.168.255.255.5007: UDP, length 80
08:29:22.280386 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:22.336821 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:22.338359 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:22.366007 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:22.422875 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:22.475023 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:22.513775 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:22.517036 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:22.725933 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:22.770972 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:22.867056 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:23.049020 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:23.171864 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:23.224927 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:23.284381 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:23.406544 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:23.542444 IP6 fe80::805:cdff:fe30:f402 > ff02::2 ICMP6, destination unreachable, unknown icmp6 type (133)
08:29:23.663088 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:23.724582 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:23.837912 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:24.186119 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:24.314269 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:24.398993 IP 192.168.1.35.5007 > 192.168.255.255.5007: UDP, length 99
08:29:24.400624 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:24.409450 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:24.412141 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:24.427328 IP 192.168.1.18.5007 > 192.168.255.255.5007: UDP, length 86
08:29:24.429032 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:24.454868 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:24.456407 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:24.467325 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:24.494683 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:24.591080 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:24.617994 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:24.619630 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:24.676205 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:24.693718 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:24.724850 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:24.739311 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:24.828693 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:24.841116 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:24.908491 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:24.954967 BLA ANNOUNCE, backbone 68:1c:a2:08:3f:a4, bla group 1b6b, crc 2185
08:29:24.955055 BLA LOOPDETECT, src backbone ba:be:5e:95:a1:b5, dst backbone ff:ff:ff:ff:ff:ff
08:29:25.049711 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:25.063364 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:25.159739 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:25.250986 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:25.284707 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:25.288442 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:25.367459 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:25.428133 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:25.434894 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:25.477102 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:25.563824 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:25.624832 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:25.643073 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:25.739831 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:25.743502 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:25.754720 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:25.788201 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:25.849364 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:25.853517 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:25.957000 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:25.963643 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:25.965237 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:26.077226 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:26.078764 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:26.220799 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:26.240436 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:26.421584 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:26.475053 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:26.587584 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:26.638337 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:26.687727 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:26.714481 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:26.796863 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:26.819373 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:26.950727 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:26.972776 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:27.061626 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:27.176326 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:27.509317 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:27.511327 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:27.571907 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:27.633598 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:27.647099 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:27.652203 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:27.845934 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:28.007201 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:28.150514 IP 192.168.1.28.5007 > 192.168.255.255.5007: UDP, length 90
08:29:28.530751 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:28.661815 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 104
08:29:28.689023 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:28.695703 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:28.764320 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:28.942917 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:28.959338 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:29.062150 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:29.071266 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:29.073229 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:29.074817 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:29.241173 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:29.243973 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:29.260466 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:29.375279 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:29.378838 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:29.380590 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:29.509973 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:29.511839 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:29.564845 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:29.580350 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:29.673747 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:29.675412 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
^[[5;7~08:29:30.250299 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:30.301737 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:30.335487 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:30.449935 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:30.691442 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:30.701919 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:30.822016 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:30.909941 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:31.132815 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:31.453470 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:31.453973 IP 192.168.1.1.5007 > 192.168.255.255.5007: UDP, length 86
08:29:31.460675 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:31.479234 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:31.852478 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:31.909884 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:32.172571 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:32.204072 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:32.305148 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:32.310358 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:32.430284 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:32.531353 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:32.649580 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:32.961365 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:33.116979 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:33.161230 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:33.222948 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:33.310702 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:33.341597 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:34.303271 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:34.398519 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:34.538719 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:34.543786 IP 192.168.1.42.5007 > 192.168.255.255.5007: UDP, length 99
08:29:34.643510 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:34.659305 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:34.892922 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:34.953694 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:35.164311 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:35.198779 BLA ANNOUNCE, backbone 68:1c:a2:08:3f:a4, bla group 1b6b, crc 2185
08:29:35.279414 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:35.299026 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:35.568439 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:35.639126 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:35.918808 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:35.968547 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:35.972710 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:35.997728 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:36.009140 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:36.134146 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:36.268279 IP 192.168.1.40.5007 > 192.168.255.255.5007: UDP, length 90
08:29:36.423715 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:36.538632 IP 192.168.1.18.5007 > 192.168.255.255.5007: UDP, length 83
08:29:36.543758 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:36.752865 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:36.763697 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:36.804304 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:36.879178 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:37.013875 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:37.078349 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:37.108808 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:37.153360 IP6 fe80::a84e:65ff:fe10:4f39 > ff02::2 ICMP6, destination unreachable, unknown icmp6 type (133)
08:29:37.177803 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:37.229380 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:37.374509 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:37.618727 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:37.624113 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:37.714254 IP 192.168.1.18.5007 > 192.168.255.255.5007: UDP, length 83
08:29:37.757819 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:38.068798 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:38.169233 IP 192.168.1.230.5353 > 224.0.0.251.5353: UDP, length 192
08:29:38.699026 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:29:38.864003 IPv6 unknown protocol: 0
08:29:39.095246 IP6 fe80::a84e:65ff:fe10:4f39.5353 > ff02::fb.5353: UDP, length 140
08:29:39.184333 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:39.529412 IP 192.168.1.18.5007 > 192.168.255.255.5007: UDP, length 87
08:29:40.402515 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:42.363567 IP 192.168.1.18.5007 > 192.168.255.255.5007: UDP, length 87
08:29:42.622598 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:42.648570 IP 192.168.1.23.5007 > 192.168.255.255.5007: UDP, length 92
08:29:42.675191 IP 192.168.1.23.5007 > 192.168.255.255.5007: UDP, length 92
08:29:42.752115 IP 192.168.1.23.5007 > 192.168.255.255.5007: UDP, length 92
08:29:42.923078 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:42.924695 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:42.930098 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:42.951178 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:42.975092 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:42.976755 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:42.996500 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:43.064853 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:43.066377 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:43.090162 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:43.100224 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:43.188390 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:43.237990 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:43.239111 IP6 fe80::e4d1:8cff:fe33:c120 > ff02::2 ICMP6, destination unreachable, unknown icmp6 type (133)
08:29:43.345407 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:43.472038 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:43.518330 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:43.527419 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:43.529078 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:43.591272 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:43.767211 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:43.803656 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:43.839486 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.016490 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.018055 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.053915 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.155583 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.205316 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.271332 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.294646 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.296319 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.350975 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.418908 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.450293 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.452039 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.528661 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.548715 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.579912 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.581592 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.613835 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.630140 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.632415 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.634609 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.667618 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.731474 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.765019 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.805634 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.821187 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.831933 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.849646 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.853956 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.976747 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:44.986570 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:45.059612 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:45.246391 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:45.251363 BLA CLAIM, backbone 68:1c:a2:08:3f:a4, client 9e:78:73:fa:ed:5b, bla group 1b6b
08:29:45.251474 IP unknown protocol: 2
08:29:45.371813 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:45.387766 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:45.434651 IP unknown protocol: 2
08:29:45.438946 BLA ANNOUNCE, backbone 68:1c:a2:08:3f:a4, bla group 1b6b, crc 4b0f
08:29:45.497547 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:45.507564 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:45.614073 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:45.685788 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:45.748097 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:45.788075 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:45.801406 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:45.883080 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:45.903528 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:45.916125 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:45.933402 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:46.015261 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:46.027614 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:46.035054 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:46.119702 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:46.129652 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:46.159573 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:46.163398 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:46.322540 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:46.395375 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:46.469279 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:46.587924 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:46.630755 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:46.702384 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:46.849463 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:46.920027 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:46.923421 IPv6 unknown protocol: 0
08:29:46.948033 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.029362 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.061877 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.065371 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.082278 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:47.223776 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.280582 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.649880 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.662413 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.749944 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.760407 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.775199 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.777585 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.797561 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.833259 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.839295 IP 192.168.1.10.5353 > 224.0.0.251.5353: UDP, length 190
08:29:47.841822 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.863347 IP6 fe80::8b0:c1ff:feb5:19c1.5353 > ff02::fb.5353: UDP, length 139
08:29:47.890690 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.894221 IPv6 unknown protocol: 0
08:29:47.902943 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:47.936047 IPv6 unknown protocol: 0
08:29:47.949409 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:47.987838 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:48.039043 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:48.071932 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:48.181995 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:48.213412 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:48.258647 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:48.267213 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:48.268943 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:48.274147 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:48.308392 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:48.312503 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:48.339968 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:48.358556 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 104
08:29:48.369605 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:48.371404 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:48.384615 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:48.496392 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:48.499698 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:48.550880 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:48.805273 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:48.903759 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:49.293667 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:49.403456 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:49.980046 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:49.981432 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.012360 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.040523 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.059635 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.061186 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.122668 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.149421 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.259356 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.262517 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.288567 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.395517 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.444480 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.531890 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.583459 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.685705 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.692553 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.718615 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.759019 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.852401 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:50.926022 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:51.762900 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:51.793211 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:51.881551 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.043847 IP 192.168.1.37.5007 > 192.168.255.255.5007: UDP, length 108
08:29:52.102336 IP 192.168.1.10.5007 > 192.168.255.255.5007: UDP, length 91
08:29:52.142457 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.185121 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.233590 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.262571 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.264150 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.358650 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.364478 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.381059 IP6 fe80::f855:b1ff:fe2f:fafd > ff02::2 ICMP6, destination unreachable, unknown icmp6 type (133)
08:29:52.400707 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.686661 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.761886 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.776395 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.848430 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.849974 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.857655 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.899828 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.924659 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.966407 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.967867 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.988728 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:52.996183 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:53.113721 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:53.620598 IP 192.168.1.186.5007 > 192.168.255.255.5007: UDP, length 81
08:29:55.675040 BLA UNCLAIM, backbone 68:1c:a2:08:3f:a4, client ae:6f:28:b0:c8:19, bla group 1b6b
08:29:55.675142 BLA UNCLAIM, backbone 68:1c:a2:08:3f:a4, client 8e:95:85:60:46:f1, bla group 1b6b
08:29:55.675287 BLA ANNOUNCE, backbone 68:1c:a2:08:3f:a4, bla group 1b6b, crc 8494
08:29:55.763943 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:55.857711 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:56.229042 IP 192.168.1.11.5007 > 192.168.255.255.5007: UDP, length 91
08:29:56.268642 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:56.614506 IP6 fe80::800c:35ff:fe78:e859 > ff02::2 ICMP6, destination unreachable, unknown icmp6 type (133)
08:29:56.978019 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:57.073960 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:57.123477 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:57.188012 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:57.194004 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:57.263774 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:57.343332 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:57.374484 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:57.413438 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:57.533779 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:57.573853 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:57.599432 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:57.623366 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:57.657806 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:57.839624 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:57.939072 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:57.974188 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:58.007940 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:58.009432 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:58.087854 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:58.108143 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:58.163549 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:58.307836 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:58.338677 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:58.348479 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:58.368379 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:58.743092 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:58.843785 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:58.879572 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:58.903422 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:58.958709 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:59.673093 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:59.777374 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:59.798776 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:59.839725 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:59.851092 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:59.858496 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:59.881655 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:59.916939 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:29:59.992776 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:00.108258 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:00.161453 IP 192.168.1.190.5007 > 192.168.255.255.5007: UDP, length 80
08:30:00.675710 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:00.937547 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:00.952316 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:01.038956 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:01.069606 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:01.088657 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:01.209221 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:01.265588 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:01.300021 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:01.301592 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:01.392955 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:01.394450 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:01.429055 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:01.519231 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:01.559753 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:01.561478 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:01.590428 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:01.603564 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:01.608754 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:01.612455 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:01.802175 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:01.811756 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:01.819898 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:02.184252 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:02.276483 IP 192.168.1.241.5007 > 192.168.255.255.5007: UDP, length 96
08:30:02.304619 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:02.435034 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:02.457145 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:02.667393 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:02.673864 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:02.681583 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:02.827959 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:02.857174 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:02.872979 IPv6 unknown protocol: 0
08:30:02.881215 IP6 fe80::a84e:65ff:fe10:4f39.5353 > ff02::fb.5353: UDP, length 140
08:30:02.909245 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:02.910803 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:02.916895 IP 192.168.1.230.5353 > 224.0.0.251.5353: UDP, length 192
08:30:02.939639 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:03.109637 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:03.132841 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:03.170263 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:03.424355 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:03.510607 IP6 fe80::a84e:65ff:fe10:4f39 > ff02::2 ICMP6, destination unreachable, unknown icmp6 type (133)
08:30:03.512299 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:03.539524 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:03.544581 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:03.560632 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:03.612250 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:03.640179 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:03.681643 IP 192.168.1.40.5007 > 192.168.255.255.5007: UDP, length 90
08:30:03.830401 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:03.865281 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:03.870493 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:03.895038 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:04.005368 IP 192.168.1.13.5007 > 192.168.255.255.5007: UDP, length 83
08:30:04.055058 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:04.100920 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:04.104439 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:04.260510 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:04.263989 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:04.939539 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:05.300070 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:05.358988 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:05.450063 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:05.531362 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:05.536483 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:05.570216 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:05.716351 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:05.721540 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:05.743962 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:05.902784 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:05.914682 BLA UNCLAIM, backbone 68:1c:a2:08:3f:a4, client 46:26:70:fa:0d:aa, bla group 1b6b
08:30:05.914775 BLA UNCLAIM, backbone 68:1c:a2:08:3f:a4, client 26:42:5e:45:03:15, bla group 1b6b
08:30:05.914810 BLA ANNOUNCE, backbone 68:1c:a2:08:3f:a4, bla group 1b6b, crc f091
08:30:05.924108 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:05.925639 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:05.956013 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:06.064337 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:06.158259 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:06.210533 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:06.212237 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:06.339558 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
08:30:06.341200 IP 192.168.1.230.5007 > 192.168.255.255.5007: UDP, length 91
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [B.A.T.M.A.N.] broadcast storms
2018-10-22 13:07 [B.A.T.M.A.N.] broadcast storms Jake.Harris
@ 2018-10-22 14:26 ` Simon Wunderlich
2018-10-22 17:27 ` Jake.Harris
0 siblings, 1 reply; 8+ messages in thread
From: Simon Wunderlich @ 2018-10-22 14:26 UTC (permalink / raw)
To: b.a.t.m.a.n
[-- Attachment #1: Type: text/plain, Size: 2440 bytes --]
Hi Jake,
could you make some pcap dumps on the wlan device where batman runs, and
provide that to us? Just the the full tcpdump (tcpdump -s 2000 -w /tmp/my.pcap
wlan0, assuming that wlan0 is your interface), not batctl dump? Then we can
check sequence numbers etc in wireshark.
Do you have some of your mesh nodes connected and bridged to Ethernet? If yes,
you should check the bridge loop avoidance which could also be causing this
effect, if you don't have it enabled and use such a topology:
https://www.open-mesh.org/projects/batman-adv/wiki/Bridge-loop-avoidance-II
Cheers,
Simon
On Monday, October 22, 2018 1:07:29 PM CEST Jake.Harris@zf.com wrote:
> I'm sure a similar question to this has been answered, but I am new to this
> mailing list format and don't know an efficient way to search
> https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/
>
> I'm having problems with broadcast messages effectively echoing around the
> network of 50ish nodes. I attached a few seconds of the batctl tcpdump
> output. I can't seem to find a pattern to what causes this, it tends to
> happen once every two or three weeks, the storm causes problems with the
> batman program where during the storm nodes drop all their neighbors
> (batctl n shows an empty list) indefinitely, which I have worked around
> that issue via a batch script that reloads batman if the neighbor list is
> empty. Reloading successfully reconnects to the network but the storm still
> persists.
>
> The only way I've found to fix this is to reboot all the nodes at the same
> time such that the whole network is down to kill the echos.
>
> I believe I had this problem much more frequently (every 4 days or so) a
> while ago on the same network when using discrete tcp destinations for the
> nodes to communicate, the storm frequency was reduced to what it is now by
> using broadcast packets and reducing the communication rate from 12 seconds
> to once every 40 seconds.
>
> Rebooting the nodes that are responsible for the echoing messages has no
> effect, I rebooted 192.168.1.230 before running tcpdump that is attached
> and as it shows packets from 230 continued to bounce around while the node
> was powered off and after it rejoined the network. It doesn't appear
> broadcast uses a time-to-live parameter to limit the hops the packets will
> make.
>
> I'm at a loss for a way to remedy this, there seems to only be multicast
> optimizations.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [B.A.T.M.A.N.] broadcast storms
2018-10-22 14:26 ` Simon Wunderlich
@ 2018-10-22 17:27 ` Jake.Harris
2018-10-22 18:17 ` Simon Wunderlich
0 siblings, 1 reply; 8+ messages in thread
From: Jake.Harris @ 2018-10-22 17:27 UTC (permalink / raw)
To: sw, b.a.t.m.a.n
[-- Attachment #1: Type: text/plain, Size: 3033 bytes --]
Generated this via:
sudo tcpdump -s 2000 -w /media/pi/KINGSTON/my.pcap -i
wlx681ca2083fa4
message after ^c
12090 packets captured
12251 packets received by filter
0 packets dropped by kernel
27 packets dropped by interface
-----Original Message-----
From: Simon Wunderlich <sw@simonwunderlich.de>
Sent: Monday, October 22, 2018 10:27
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Harris Jake LPR <Jake.Harris@zf.com>
Subject: Re: [B.A.T.M.A.N.] broadcast storms
* PGP Signed by an unknown key
Hi Jake,
could you make some pcap dumps on the wlan device where batman runs, and provide that to us? Just the the full tcpdump (tcpdump -s 2000 -w /tmp/my.pcap wlan0, assuming that wlan0 is your interface), not batctl dump? Then we can check sequence numbers etc in wireshark.
Do you have some of your mesh nodes connected and bridged to Ethernet? If yes, you should check the bridge loop avoidance which could also be causing this effect, if you don't have it enabled and use such a topology:
https://www.open-mesh.org/projects/batman-adv/wiki/Bridge-loop-avoidance-II
Cheers,
Simon
On Monday, October 22, 2018 1:07:29 PM CEST Jake.Harris@zf.com wrote:
> I'm sure a similar question to this has been answered, but I am new to
> this mailing list format and don't know an efficient way to search
> https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/
>
> I'm having problems with broadcast messages effectively echoing around
> the network of 50ish nodes. I attached a few seconds of the batctl
> tcpdump output. I can't seem to find a pattern to what causes this, it
> tends to happen once every two or three weeks, the storm causes
> problems with the batman program where during the storm nodes drop all
> their neighbors (batctl n shows an empty list) indefinitely, which I
> have worked around that issue via a batch script that reloads batman
> if the neighbor list is empty. Reloading successfully reconnects to
> the network but the storm still persists.
>
> The only way I've found to fix this is to reboot all the nodes at the
> same time such that the whole network is down to kill the echos.
>
> I believe I had this problem much more frequently (every 4 days or so)
> a while ago on the same network when using discrete tcp destinations
> for the nodes to communicate, the storm frequency was reduced to what
> it is now by using broadcast packets and reducing the communication
> rate from 12 seconds to once every 40 seconds.
>
> Rebooting the nodes that are responsible for the echoing messages has
> no effect, I rebooted 192.168.1.230 before running tcpdump that is
> attached and as it shows packets from 230 continued to bounce around
> while the node was powered off and after it rejoined the network. It
> doesn't appear broadcast uses a time-to-live parameter to limit the
> hops the packets will make.
>
> I'm at a loss for a way to remedy this, there seems to only be
> multicast optimizations.
* Unknown Key
* 0x42929EA1
[-- Attachment #2: my.pcap.tar.xz --]
[-- Type: application/octet-stream, Size: 100900 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [B.A.T.M.A.N.] broadcast storms
2018-10-22 17:27 ` Jake.Harris
@ 2018-10-22 18:17 ` Simon Wunderlich
2018-11-12 14:29 ` Jake.Harris
0 siblings, 1 reply; 8+ messages in thread
From: Simon Wunderlich @ 2018-10-22 18:17 UTC (permalink / raw)
To: Jake.Harris; +Cc: b.a.t.m.a.n
[-- Attachment #1: Type: text/plain, Size: 4078 bytes --]
Hello Jake,
I've checked your pcap files. I couldn't find a culprit directly, but it seems
like you are having so many repetitions / the network is getting so overloaded
that broadcasts stay in the queues of your WiFi driver for longer than 30
seconds (possibly in different devices, accumulated). At this point, batman-
adv assumes that the device has rebooted and the sequence number is validly
re-used, thus circumventing the broadcast duplicate check.
You could increase the define of BATADV_RESET_PROTECTION_MS to something
higher like 120000 (120 seconds) and see if that helps. But the "right" way
would be to avoid those deep queues in the first place.
Do you set a multicast rate higher than the default 1 MBit/s? If not, that's
worth a try. :) If you are using iw, there is a "mcast-rate" parameter, and
there is something equivalent in wpa_supplicant.
Cheers,
Simon
On Monday, October 22, 2018 5:27:28 PM CEST Jake.Harris@zf.com wrote:
> Generated this via:
> sudo tcpdump -s 2000 -w /media/pi/KINGSTON/my.pcap -i
> wlx681ca2083fa4
>
> message after ^c
> 12090 packets captured
> 12251 packets received by filter
> 0 packets dropped by kernel
> 27 packets dropped by interface
>
> -----Original Message-----
> From: Simon Wunderlich <sw@simonwunderlich.de>
> Sent: Monday, October 22, 2018 10:27
> To: b.a.t.m.a.n@lists.open-mesh.org
> Cc: Harris Jake LPR <Jake.Harris@zf.com>
> Subject: Re: [B.A.T.M.A.N.] broadcast storms
>
> * PGP Signed by an unknown key
>
> Hi Jake,
>
> could you make some pcap dumps on the wlan device where batman runs, and
> provide that to us? Just the the full tcpdump (tcpdump -s 2000 -w
> /tmp/my.pcap wlan0, assuming that wlan0 is your interface), not batctl
> dump? Then we can check sequence numbers etc in wireshark.
>
> Do you have some of your mesh nodes connected and bridged to Ethernet? If
> yes, you should check the bridge loop avoidance which could also be causing
> this effect, if you don't have it enabled and use such a topology:
>
> https://www.open-mesh.org/projects/batman-adv/wiki/Bridge-loop-avoidance-II
>
> Cheers,
> Simon
>
> On Monday, October 22, 2018 1:07:29 PM CEST Jake.Harris@zf.com wrote:
> > I'm sure a similar question to this has been answered, but I am new to
> > this mailing list format and don't know an efficient way to search
> > https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/
> >
> > I'm having problems with broadcast messages effectively echoing around
> > the network of 50ish nodes. I attached a few seconds of the batctl
> > tcpdump output. I can't seem to find a pattern to what causes this, it
> > tends to happen once every two or three weeks, the storm causes
> > problems with the batman program where during the storm nodes drop all
> > their neighbors (batctl n shows an empty list) indefinitely, which I
> > have worked around that issue via a batch script that reloads batman
> > if the neighbor list is empty. Reloading successfully reconnects to
> > the network but the storm still persists.
> >
> > The only way I've found to fix this is to reboot all the nodes at the
> > same time such that the whole network is down to kill the echos.
> >
> > I believe I had this problem much more frequently (every 4 days or so)
> > a while ago on the same network when using discrete tcp destinations
> > for the nodes to communicate, the storm frequency was reduced to what
> > it is now by using broadcast packets and reducing the communication
> > rate from 12 seconds to once every 40 seconds.
> >
> > Rebooting the nodes that are responsible for the echoing messages has
> > no effect, I rebooted 192.168.1.230 before running tcpdump that is
> > attached and as it shows packets from 230 continued to bounce around
> > while the node was powered off and after it rejoined the network. It
> > doesn't appear broadcast uses a time-to-live parameter to limit the
> > hops the packets will make.
> >
> > I'm at a loss for a way to remedy this, there seems to only be
> > multicast optimizations.
>
> * Unknown Key
> * 0x42929EA1
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [B.A.T.M.A.N.] broadcast storms
2018-10-22 18:17 ` Simon Wunderlich
@ 2018-11-12 14:29 ` Jake.Harris
2018-11-12 17:13 ` Simon Wunderlich
0 siblings, 1 reply; 8+ messages in thread
From: Jake.Harris @ 2018-11-12 14:29 UTC (permalink / raw)
To: sw; +Cc: b.a.t.m.a.n
My apologies bringing this back but I'm still having trouble with this. Each of my 50 nodes sends a 100 byte packet via broadcast every 30 seconds, even if coincidently they all transmit it at the same time that's only 5kB of data to move, much under the 1MB (default I believe?) bandwidth for multicast. Unless there's a large amount of broadcast traffic outside of my python program I don't see this being the culprit.
The storms tend to start when connection to a few nodes gets flakey, so I can see the reset protection setting being helpful, how do I set BATADV_RESET_PROTECTION_MS? Is this an environment variable or do I set it with batctl?
Thanks again for your help, I believe this has a good chance of remedying the issue.
-----Original Message-----
From: Simon Wunderlich <sw@simonwunderlich.de>
Sent: Monday, October 22, 2018 14:17
To: Harris Jake LPR <Jake.Harris@zf.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] broadcast storms
* PGP Signed by an unknown key
Hello Jake,
I've checked your pcap files. I couldn't find a culprit directly, but it seems like you are having so many repetitions / the network is getting so overloaded that broadcasts stay in the queues of your WiFi driver for longer than 30 seconds (possibly in different devices, accumulated). At this point, batman- adv assumes that the device has rebooted and the sequence number is validly re-used, thus circumventing the broadcast duplicate check.
You could increase the define of BATADV_RESET_PROTECTION_MS to something higher like 120000 (120 seconds) and see if that helps. But the "right" way would be to avoid those deep queues in the first place.
Do you set a multicast rate higher than the default 1 MBit/s? If not, that's worth a try. :) If you are using iw, there is a "mcast-rate" parameter, and there is something equivalent in wpa_supplicant.
Cheers,
Simon
On Monday, October 22, 2018 5:27:28 PM CEST Jake.Harris@zf.com wrote:
> Generated this via:
> sudo tcpdump -s 2000 -w /media/pi/KINGSTON/my.pcap -i
> wlx681ca2083fa4
>
> message after ^c
> 12090 packets captured
> 12251 packets received by filter
> 0 packets dropped by kernel
> 27 packets dropped by interface
>
> -----Original Message-----
> From: Simon Wunderlich <sw@simonwunderlich.de>
> Sent: Monday, October 22, 2018 10:27
> To: b.a.t.m.a.n@lists.open-mesh.org
> Cc: Harris Jake LPR <Jake.Harris@zf.com>
> Subject: Re: [B.A.T.M.A.N.] broadcast storms
>
> > Old Signed by an unknown key
>
> Hi Jake,
>
> could you make some pcap dumps on the wlan device where batman runs,
> and provide that to us? Just the the full tcpdump (tcpdump -s 2000 -w
> /tmp/my.pcap wlan0, assuming that wlan0 is your interface), not batctl
> dump? Then we can check sequence numbers etc in wireshark.
>
> Do you have some of your mesh nodes connected and bridged to Ethernet?
> If yes, you should check the bridge loop avoidance which could also be
> causing this effect, if you don't have it enabled and use such a topology:
>
> https://www.open-mesh.org/projects/batman-adv/wiki/Bridge-loop-avoidan
> ce-II
>
> Cheers,
> Simon
>
> On Monday, October 22, 2018 1:07:29 PM CEST Jake.Harris@zf.com wrote:
> > I'm sure a similar question to this has been answered, but I am new
> > to this mailing list format and don't know an efficient way to
> > search https://lists.open-mesh.org/pipermail/b.a.t.m.a.n/
> >
> > I'm having problems with broadcast messages effectively echoing
> > around the network of 50ish nodes. I attached a few seconds of the
> > batctl tcpdump output. I can't seem to find a pattern to what causes
> > this, it tends to happen once every two or three weeks, the storm
> > causes problems with the batman program where during the storm nodes
> > drop all their neighbors (batctl n shows an empty list)
> > indefinitely, which I have worked around that issue via a batch
> > script that reloads batman if the neighbor list is empty. Reloading
> > successfully reconnects to the network but the storm still persists.
> >
> > The only way I've found to fix this is to reboot all the nodes at
> > the same time such that the whole network is down to kill the echos.
> >
> > I believe I had this problem much more frequently (every 4 days or
> > so) a while ago on the same network when using discrete tcp
> > destinations for the nodes to communicate, the storm frequency was
> > reduced to what it is now by using broadcast packets and reducing
> > the communication rate from 12 seconds to once every 40 seconds.
> >
> > Rebooting the nodes that are responsible for the echoing messages
> > has no effect, I rebooted 192.168.1.230 before running tcpdump that
> > is attached and as it shows packets from 230 continued to bounce
> > around while the node was powered off and after it rejoined the
> > network. It doesn't appear broadcast uses a time-to-live parameter
> > to limit the hops the packets will make.
> >
> > I'm at a loss for a way to remedy this, there seems to only be
> > multicast optimizations.
>
> * Unknown Key
> * 0x42929EA1
* Unknown Key
* 0x42929EA1
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [B.A.T.M.A.N.] broadcast storms
2018-11-12 14:29 ` Jake.Harris
@ 2018-11-12 17:13 ` Simon Wunderlich
2018-11-13 14:55 ` Jake.Harris
0 siblings, 1 reply; 8+ messages in thread
From: Simon Wunderlich @ 2018-11-12 17:13 UTC (permalink / raw)
To: Jake.Harris; +Cc: b.a.t.m.a.n
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
Hi Jake,
On Monday, November 12, 2018 2:29:07 PM CET Jake.Harris@zf.com wrote:
> My apologies bringing this back but I'm still having trouble with this. Each
> of my 50 nodes sends a 100 byte packet via broadcast every 30 seconds, even
> if coincidently they all transmit it at the same time that's only 5kB of
> data to move, much under the 1MB (default I believe?) bandwidth for
> multicast. Unless there's a large amount of broadcast traffic outside of my
> python program I don't see this being the culprit.
Mhm, this is really not much data ... did you try the multicast as suggested
in an earlier reply?
>
> The storms tend to start when connection to a few nodes gets flakey, so I
> can see the reset protection setting being helpful, how do I set
> BATADV_RESET_PROTECTION_MS? Is this an environment variable or do I set it
> with batctl?
BATADV_RESET_PROTECTION_MS is a define in the batman-adv C-code, so it can't be
set at runtime but only at compile time.
Cheers,
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [B.A.T.M.A.N.] broadcast storms
2018-11-12 17:13 ` Simon Wunderlich
@ 2018-11-13 14:55 ` Jake.Harris
2018-11-13 15:26 ` Simon Wunderlich
0 siblings, 1 reply; 8+ messages in thread
From: Jake.Harris @ 2018-11-13 14:55 UTC (permalink / raw)
To: sw; +Cc: b.a.t.m.a.n
> Mhm, this is really not much data ... did you try the multicast as suggested in an earlier reply?
What earlier reply are you referring to? The only one I'm noticing is the tip to boost the multicast bandwidth, but I cannot see this being fruitful to update the configuration of all 50 nodes when worst-case I'm using less than 1% of the max throughput.
> BATADV_RESET_PROTECTION_MS is a define in the batman-adv C-code, so it can't be set at runtime but only at compile time.
While this sounds like an utter pain in the butt to recompile and update the code on all the nodes to make this change, I believe this has a far better chance of alleviating the issue, I'm looking into how to do this since I've never compiled anything myself but I can't see it being too difficult.
One observation I made when rebooting the swarm all at once, about a minute after all the pi's go down the laptop I work off (running batctl td bat0) reports a whole bunch of backbone unannounced messages I believe. I'm assuming there is one message per node but have not verified, my guess is this is normal and is not the cause of these issues?
Again, thank you
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [B.A.T.M.A.N.] broadcast storms
2018-11-13 14:55 ` Jake.Harris
@ 2018-11-13 15:26 ` Simon Wunderlich
0 siblings, 0 replies; 8+ messages in thread
From: Simon Wunderlich @ 2018-11-13 15:26 UTC (permalink / raw)
To: Jake.Harris; +Cc: b.a.t.m.a.n
[-- Attachment #1: Type: text/plain, Size: 1684 bytes --]
On Tuesday, November 13, 2018 2:55:31 PM CET Jake.Harris@zf.com wrote:
> > Mhm, this is really not much data ... did you try the multicast as
> > suggested in an earlier reply?
> What earlier reply are you referring to? The only one I'm noticing is the
> tip to boost the multicast bandwidth, but I cannot see this being fruitful
> to update the configuration of all 50 nodes when worst-case I'm using less
> than 1% of the max throughput.
One aspect is that the multicast rate is also changing the modulation rate of
beacons. If you have >50 nodes beaconing with 1 Mbit/s you are already filling
up your airtime with beacons. Do the math - one beacon takes about 1ms on 1
Mbit/s, each node sends about 10 beacons per second ...
This is actually very important and will most likely help already. It would be
a better fix than changing the protection window.
> > BATADV_RESET_PROTECTION_MS is a define in the batman-adv C-code, so it
> > can't be set at runtime but only at compile time.
> While this sounds like an utter pain in the butt to recompile and update the
> code on all the nodes to make this change, I believe this has a far better
> chance of alleviating the issue, I'm looking into how to do this since I've
> never compiled anything myself but I can't see it being too difficult.
>
> One observation I made when rebooting the swarm all at once, about a minute
> after all the pi's go down the laptop I work off (running batctl td bat0)
> reports a whole bunch of backbone unannounced messages I believe. I'm
> assuming there is one message per node but have not verified, my guess is
> this is normal and is not the cause of these issues?
>
> Again, thank you
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2018-11-13 15:26 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-22 13:07 [B.A.T.M.A.N.] broadcast storms Jake.Harris
2018-10-22 14:26 ` Simon Wunderlich
2018-10-22 17:27 ` Jake.Harris
2018-10-22 18:17 ` Simon Wunderlich
2018-11-12 14:29 ` Jake.Harris
2018-11-12 17:13 ` Simon Wunderlich
2018-11-13 14:55 ` Jake.Harris
2018-11-13 15:26 ` Simon Wunderlich
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.