[Olsr-users] Flooding custom data in OLSRv2 networks

Ferry Huberts (spam-protected)
Tue Jul 5 22:50:14 CEST 2016

I think Henning is a bit grumpy ;-)

Both olsrd v1 and v2 are meant to be routing agents and nothing more.
They both have a plugin system, and in olsrd v1 this was 'abused' to 
piggy-back non-routing related information and functionality.

Sometimes this makes sense, but most of the time it does not.

Having clearly separated daemons/services/functions/concerns mostly wins 
over tightly integrated applications.

On 05/07/16 21:39, Henning Rogge wrote:
> On Tue, Jul 5, 2016 at 9:37 PM, Martin Garbe
> <(spam-protected)> wrote:
>> I now understand that this is a fundamental change between OLSRv1 and
>> v2.
> No, you do not.
>> OLSRv2 is only used for distributing routing information.
> OLSRv1 was the same until someone wrote the nameservice plugin...
> which was (in my oppinion not really a good solution for the problem).
>> All other
>> data distribution has to be done by another sparated service. some kind
>> of piggyback is not possible.
> Like I said, you are wrong.
> In theory OLSRv2 is even more flexible in how plugins can create new
> message types AND modify existing messages.
> Henning

Ferry Huberts

More information about the Olsr-users mailing list