[Olsr-dev] Migration from olsrd v1 to v2

Ferry Huberts (spam-protected)
Mon Jul 27 19:02:51 CEST 2015

IMHO you shouldn't abuse olsr (a routing protocol) to distribute user data.

Just implement a data grid on top.
There are plenty products out there.

On 27/07/15 18:59, Conrad Lara wrote:
> As long as convergence doesn't take too long for distributing the data it shouldn't be bad,  are you thinking something like a handshake at node join and transfer to distribute the data?
> Interesting enough I actually have hit (what I would call but may just be a difference in opinion of design) bugs in the old nameservice module where it looks like the thought was data was going to be mostly static and it wasn't considered about changing names (you can't change the IP a name points to unless the node is allowed to drop off the network and old names when you do change your name never expire. Unless you drop) same with services once advertised the service currently exists indefinitely and doesn't ever get removed until the device falls off the network for missing packets.
> Sent from my iPhone
>> On Jul 27, 2015, at 9:12 AM, Henning Rogge <(spam-protected)> wrote:
>>> On Mon, Jul 27, 2015 at 5:56 PM, Conrad Lara <(spam-protected)> wrote:
>>> Any chance at getting a high level concept run down before work begins?
>>> Unless it's "the same" model as before it opens up concerns as to if the module will fit the needs of those it's suppose to be deployed on, hashing out some of these design changes before work begins could save hours of work later to re-design the structure.
>> Basic idea is a distribution protocol for "mostly-static" data and
>> then build on top of it.
>> You don't change your DNS name, your service list or your node
>> position every day (or even more often)... so the protocol should be
>> optimized for this.
>> Henning Rogge

Ferry Huberts

More information about the Olsr-dev mailing list