Project

General

Profile

Actions

Bug #413

closed

B.A.T.M.A.N. V aggregation causes originator loops

Added by Sven Eckelmann over 3 years ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
07/23/2020
Due date:
% Done:

100%

Estimated time:

Description

It was reported that some installations with enabled OGMv2 aggregation can cause the own originator to appear in the originator table via a different node:

My originator messages look wrong as I can see my host originator messages along with all the neigbor nodes:

root@OpenWrt:/etc/config# batctl o -n
[B.A.T.M.A.N. adv 2020.1-openwrt-2, MainIF/MAC: mesh0/00:30:1a:4e:b8:26 (bat0/f2:07:f1:5f:e0:78 BATMAN_V)]
   Originator        last-seen ( throughput)  Nexthop           [outgoingIF]
 * 00:30:1a:4e:b8:18    0.570s (       86.7) 00:30:1a:4e:b8:2e [     mesh0]
   00:30:1a:4e:b8:18    0.570s (       21.6) 00:30:1a:4e:b8:18 [     mesh0]
 * 00:30:1a:4e:b8:2e    1.510s (      212.6) 00:30:1a:4e:b8:2e [     mesh0]
   00:30:1a:4e:b8:2e    1.510s (       38.9) 00:30:1a:4e:b8:18 [     mesh0]
   00:30:1a:4e:b8:26    1.510s (       38.9) 00:30:1a:4e:b8:18 [     mesh0]
 * 00:30:1a:4e:b8:26    1.510s (      108.9) 00:30:1a:4e:b8:2e [     mesh0]

root@OpenWrt:/etc/config# batctl n -n
[B.A.T.M.A.N. adv 2020.1-openwrt-2, MainIF/MAC: mesh0/00:30:1a:4e:b8:26 (bat0/f2:07:f1:5f:e0:78 BATMAN_V)]
IF             Neighbor              last-seen
00:30:1a:4e:b8:2e    0.490s (      179.0) [     mesh0]
00:30:1a:4e:b8:18    0.380s (       79.2) [     mesh0]

Disabling aggregation seems to solve this problem.

See also:

Actions

Also available in: Atom PDF