Removing a node causing mesh to stop
lucas.pickstone at minlog.com.au
Fri Apr 12 08:00:11 CEST 2019
We have problem where our mesh is failing after a node is removed from
it. We have a test set up of 3 computers (A, B and C) that can all
directly see each other in an ad hoc wireless network.
When we remove a node, the mesh between the remaining two nodes
continues to work for a time (batman pings get through), but "batctl
o" shows nothing recently last-seen. Once it times out after 200
seconds, the mesh dies (no further pings via batman get through).
If we bring the disconnected node back up, everything goes back to normal.
Has anyone else seen this problem or had any experience with something similar?
We're a little bit stuck on how to diagnose/debug what is happening.
We thought that maybe the underlying ad hoc network was causing
issues, but it seems okay - we can assign IP addresses on the wlan
interfaces and ping without interruption through the entire test.
Here is a link to a video showing the behaviour from node C, some time
after node A was removed. Both node B and C should still be connected.
- The terminal at the top shows the batman ping to node B (from node C).
- The middle terminal shows the standard ping via the adhoc network
wlan interface to node B (from node C).
- The lower window shows the B.A.T.M.A.N. originators table (as seen by node C).
Environment (identical on all computers):
- WiFi Card : SparkLAN WPEQ-160ACN(BT)
- WiFi driver: nl80211
- batman-adv: 2019.1
- batctl: 2019.1
- Linux Kernel: 4.4.0-130 Ubuntu 16.04 LTS
Any thoughts would be greatly appreciated.
More information about the B.A.T.M.A.N