Tobias, > root@1043-49:~# batctl tg > Globally announced TT entries received via the mesh bat0 > Client (TTVN) Originator (Curr TTVN) > * 42:c9:62:7e:91:f2 ( 1) via bat57 ( 1) > * d6:0f:24:f1:43:3c ( 1) via bat59 ( 1) > * 04:11:80:50:38:c8 ( 1) via bat53 ( 1) > * 7a:7b:f4:ed:5c:24 ( 1) via bat52 ( 1) > * 04:11:80:2f:c4:c8 ( 1) via bat67 ( 1) > * be:57:9e:5b:e0:3e ( 1) via bat60 ( 1) > * fa:45:8f:a5:2c:75 ( 1) via bat55 ( 1) > * c2:90:a3:3b:4e:c9 ( 1) via bat58 ( 1) > * ea:4b:dd:55:f3:1f ( 1) via bat54 ( 1) > * 76:18:e9:ab:f9:40 ( 1) via bat51 ( 1) > > root@1043-49:~# batctl tl > Locally retrieved addresses (from bat0) announced via TT (TTVN: 1): > * 9e:90:fc:dc:99:09 > > > and ouput of batctl tl of this other node (fon-53)? > > root@fon-53:~# batctl tl > Locally retrieved addresses (from bat0) announced via TT (TTVN: 1): > * da:54:2c:e4:b9:1e
I have tried to reproduce your issue but was unsuccessful. Could you help narrowing down the cause by providing some more information ? For instance: * What is the simpliest setup that can provoke the issue ? Does it also happen if you only involve 2 nodes ? Or 3 / 4 / 5 ? Does the problem go away if you reduce the number of interfaces on each node ? * You provided some logs showing additions / deletions of a non-existing mac address and you said this would go away after a while. What do the logs say when the problem is about to disappear ? * Are the nodes that often exhibit this flakiness far apart or direct neighbors ? What does the topology look like ? Again, the simplier the setup the better. Regards, Marek
