Project

General

Profile

Actions

Bug #380

closed

Too high number of OGMs after interface up->down->up

Added by Sven Eckelmann almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
06/02/2019
Due date:
% Done:

100%

Estimated time:

Description

It seems there is a problem with a too high number of management frames on some devices/firmwares (gluon). The culprit seems to be the OGM interval on these devices.

The details are slightly unclear but Linus wrote following in IRC:

ok, I think I found the issue. it seems that the interface activate functions are called twice, with a deactivate in between
however each activate starts OGM timer
so there are basically two timers running, explaining why we see this 2s, 3s, 2s, 3s interval for OGMs
and we calculated and compared statistics with compat14 / batman-adv-legacy. there, we do not have this issue
I'm wondering whether I might have messed something up with the forw-packet changes I had made somewhere around v2016.x
and yeah, it's reproduceable in VMs. "batctl if add dummy0; ip link set up dev dummy0" -> 1x OGM per interval. then "ip link set down dummy0; ip link set up dev dummy0" -> 2x OGMs per interval
nope, not my forw-packet fix in v2016.5. the issue was introduced with the API changes in v2016.3
v2016.2 -> good, v2016.3 -> bad

Actions

Also available in: Atom PDF