[Olsr-dev] reduce OLSR bandwidth by tuning emission intervals

Clauz (spam-protected)
Fri Mar 1 12:33:07 CET 2013

What I see is that TCs, HNAs and MIDs are not forwarded immediately but
delayed until the next HELLO emission, like you can see in this trace
[*]. The network setup is the following:

n0 -- n1 -- n2 -- n3

OLSR setup:
n0 is a non-OLSR host and n1 announces the subnet containing n0 via HNA.
The emission intervals and validity times on n1 are at the default
values, while the emission intervals and validity times on n2 and n3 are
multiplied x15.

IP addresses:

In the trace, packets from n2 ( contain messages from n1
( that, according to your message below, should have been
forwarded almost immediately. Instead these are delayed until (roughly)
the next HELLO emission interval.

This tarball [^] contains the netkit network emulator "lab" that I used,
including the complete configuration files.


[*] http://zumbi.netgroup.uniroma2.it/~clauz/tmp/bigemission3.pcap
[^] http://zumbi.netgroup.uniroma2.it/~clauz/tmp/netkitolsrd_emission.tar.gz

On 02/28/2013 09:23 AM, Henning Rogge wrote:
> So what DO you see?
> Henning Rogge
> On Wed, Feb 27, 2013 at 11:47 AM, Clauz <(spam-protected)> wrote:
>> On 02/26/2013 02:39 PM, Henning Rogge wrote:
>>> Hi,
>>> incoming OLSR messages like TCs/MIDs/HNAs are delayed by a few hundred
>>> milliseconds (to allow message aggregation), but besides this they are
>>> (and have to be) forwarded instantly.
>> This is not what I see :/ Perhaps somebody else can check if this is
>> working as expected (i.e. it is a problem specific to my setup) or a bug?
>> Clauz
>> --
>> Olsr-dev mailing list
>> (spam-protected)
>> https://lists.olsr.org/mailman/listinfo/olsr-dev

More information about the Olsr-dev mailing list