[Battlemesh] Out of sync seqnos after reboot

Henning Rogge hrogge at googlemail.com
Sat Mar 10 10:15:13 CET 2012

No, thats the last 31 numbers. So if the most current sequence number
was 100, OLSR remembers which number from 100-31 to 100 it has
received. Everything lower than 100-31 is considered "outdated" (and
might trigger the 'sequence number jumped' action).


On Fri, Mar 9, 2012 at 14:52, Mitar <mitar at tnode.com> wrote:
> Hi!
>> The "remember the last 31 possible sequence numbers" is just a
>> uint32_t used as a binary mask that is shifted every times OLSRd
>> accepts a new message.
> Ehm, how exactly is this done? Last 31 sequence numbers are not
> necessary in direct sequence or yes? So how you store which last 31
> sequence numbers were received by just having a binary mask?
> Mitar

Steven Hawkings about cosmic inflation: "An increase of billions of
billions of percent in a tiny fraction of a second. Of course, that
was before the present government."

More information about the Battlemesh mailing list