In this if statement, the b.bits entries that are being set to false should first be checked to see if any are already false, and if so the lostCounter should be incremented for each.
This means any case where you lose more than 1 packet, you risk not counting older packet loss that it skips over.
What version of
nebula
are you using? (nebula -version
)master
What operating system are you using?
not relevant
Describe the Bug
https://github.com/slackhq/nebula/blob/3f6a7cb250a756314da65e8a440628dd94e7976f/bits.go#L66-L68
In this if statement, the
b.bits
entries that are being set tofalse
should first be checked to see if any are alreadyfalse
, and if so thelostCounter
should be incremented for each.This means any case where you lose more than 1 packet, you risk not counting older packet loss that it skips over.
Logs from affected hosts
not relevant
Config files from affected hosts
not relevant