Upon debugging a network with dangling, bogus TT entries, I found a
couple of bugs for which I would like to propose fixes. The network showed
the following symptoms:
* DAT was enabled
* VLANs were used, but not every originator used the same VLANs
* I've found global entries assigned to originators which actually
never had the client in question connected to them. These false target
originators didn't even had the VLANs in use or bridged for which
the entry was done. This caused packets sent to be sent to these wrong
originators.
* The wrong entries also didn't get purged automatically, since they
didn't announce the VLAN in question through their TT TLVLs, and the
TT code didn't check for excess VLANs.
* Furthermore, the temp flag was removed too early from the TT entries
so that the purge function was not removing the entry after a timeout
as well.
* I've found that with DAT, the cached ARP replies may cause these
TT entries to be created on behalf of the answering host. This is wrong,
since the answering host (usually) doesn't actually has the client
connected.
Three of these four patches fix various issues connected with the problem
described above. The fourth one is merely a style fix which does not neccessarily
have to be adopted to maint.
We have not yet tested these patches in the network, and the bug also appears
only once in a couple of days. Therefore I'd like to ask to review these patches
thoroughly, and if you agree to the fixes we will apply them in this production
network.
Thanks,
Simon
Simon Wunderlich (4):
batman-adv: fix speedy join for DAT cache replies
batman-adv: avoid keeping false temporary entry
batman-adv: unify flags access style in tt global add
batman-adv: detect local excess vlans in TT request
net/batman-adv/routing.c | 17 +++++++++++++----
net/batman-adv/translation-table.c | 33 ++++++++++++++++++++++++++++++---
2 files changed, 43 insertions(+), 7 deletions(-)
--
2.5.0