Henning Rogge | 31 Jul 08:42 2015
Picon

OONF v0.9.1 bugfix release

Hi,

the v0.9.0 release just has happened but as always I found a few
important bugs shortly afterwards.

Most of them are multitopology routing related, but there was also a
bug in the Olsrv2 originator configuration settings.

Henning Rogge

--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev

Bastian Bittorf | 29 Jul 13:27 2015

http://olsr.org/git/oonf.git/info/refs

this is at least an issue for the OpenWrt-feeds.

thanks & bye, bastian

--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev

Henning Rogge | 28 Jul 09:08 2015
Picon

OONF release 0.9.0

Hi,

I just tagged the version 0.9.0 of the Olsr.org Network Framework
(which includes DLEP and Olsrd2).

The release contains a few major changes:
- rewritten DLEP code with support for DLEP draft 15
- fixes for link-local Originator Addresses for Olsrd2
- support for source-specific routing for IPv6
- fixes for musl libc (important for OpenWRT Chaos Calmer)

and a lot of other small changes.

So finally, after years of "BABEL rules source-specific routing"
Olsrd2 got the same capability. I think this will become very
important in the future for IPv6 and multihomed mesh networks.

Thank you to Matthieu who implemented source-specific routing first on
Babel (and went through all the pittraps first) and the rest of the
people who kept asking me about the feature.

Henning

--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev

Conrad Lara | 27 Jul 19:24 2015
Picon
Picon

Re: Migration from olsrd v1 to v2


Ferry: 
I'll admit it seems somewhat a kludged on in many ways, unfortunately/fortunately the module was designed
and distributed and the project I've gotten involved uses it that way so for a while it's likely to stay for
that project.

I would be interested in a set of names of other solutions (one or two) if you can think of them off hand to
provide a starting point as I wouldn't mind doing some digging to see other options as possible
replacement for when we hit a protocol break in the future which gives us a chance to redesign our platform
to better handle itself.

Henning:
Understood will be curious to see where it goes and develops. Thanks you for the highlevel on it.

Sent from my iPhone

> On Jul 27, 2015, at 10:04 AM, Henning Rogge <hrogge <at> gmail.com> wrote:
> 
>> On Mon, Jul 27, 2015 at 7:02 PM, Ferry Huberts <mailings <at> hupie.com> wrote:
>> 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.
> 
> I am aiming on something independent of the routing protocol. See "Homenet".
> 
> Henning

--

-- 
Olsr-dev mailing list
(Continue reading)

Conrad Lara | 27 Jul 18:59 2015
Picon
Picon

Re: Migration from olsrd v1 to v2

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 <hrogge <at> gmail.com> wrote:
> 
>> On Mon, Jul 27, 2015 at 5:56 PM, Conrad Lara <ipstealer <at> cox.net> 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

(Continue reading)

Conrad Lara | 27 Jul 17:56 2015
Picon
Picon

Re: Migration from olsrd v1 to v2

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.

Sent from my iPhone

> On Jul 27, 2015, at 8:37 AM, Henning Rogge <hrogge <at> gmail.com> wrote:
> 
>> On Sun, Jul 26, 2015 at 11:28 PM, Bastian Rosner <bro <at> d00m.org> wrote:
>> Henning Rogge <hrogge <at> gmail.com> [10.07.2015 13:24]:
>>> So a direct question to everyone here on the list, do you deploy the
>>> plugin on ALL nodes of a mesh? I have some ideas about how to replace
>> 
>> In Freifunk-Berlin we use nameservice-plugin for decentralized
>> distribution of DNS, GPS/node-location and service information on all nodes.
>> 
>> We even push these as RRs to real bind9 nameservers, since all of these
>> translate directly to well known DNS record types and parsing files
>> generated by nameservice-plugin is fairly easy.
> 
> I think I have a plan how to replace the nameservice plugin now... it
> will take a while to get a prototype up and running, but we will get
> more capability for less overhead...
> 
> Henning
> 
> -- 
> Olsr-dev mailing list
(Continue reading)

Bastian Rosner | 26 Jul 23:28 2015

Migration from olsrd v1 to v2

Henning Rogge <hrogge <at> gmail.com> [10.07.2015 13:24]:
> So a direct question to everyone here on the list, do you deploy the
> plugin on ALL nodes of a mesh? I have some ideas about how to replace

In Freifunk-Berlin we use nameservice-plugin for decentralized
distribution of DNS, GPS/node-location and service information on all nodes.

We even push these as RRs to real bind9 nameservers, since all of these
translate directly to well known DNS record types and parsing files
generated by nameservice-plugin is fairly easy.

Cheers
Bastian

--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev

Shane Melton | 21 Jul 23:40 2015

Custom Routing Metrics

Hi everyone,

I am a student doing research on adaptive routing through mobile mesh networks and I decided to use olsr to create the test bed for our experiments. I've been looking through olsrd's source over the past couple of weeks trying to become more familiar with its functionality.

What I would like to do is create some additional metrics that will be gathered by each node to be used in calculating the best routes for the network. What these metrics will be hasn't been decided yet, but they will vary at each nodes location so we would like to adapt the route based on the values measured. So my primary question: How would I go about adjusting the routing information throughout the network based on some external data that can come from each node?

I believe I can write a plugin to accomplish this task, I'm just not sure where to begin or if there is better method of going about this. Any help to get in going in the right direction would be greatly appreciated.

Thanks,

Shane


--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev
Diogo Gonçalves | 13 Jul 19:49 2015
Picon

Fwd: Improving SPF with binary heaps

Hi, 

2015-07-13 14:10 GMT-03:00 Henning Rogge <hrogge <at> gmail.com>:
Hi,

since we have some people to ask when we have questions about it, I
think it will be good to merge.

But I would also like someone of you to look after it when I build it
into the olsrd2 dijkstra.

Ok, I available to support the code and help porting my binary heap to olsrd2
 
If you can clean up the "heap.h" file so
that it only contains the necessary functions for an user (and not the
internal ones), it should be easy to supply a few good accessor macros
(similar to list.h and avl.h in OONF).

No problem, i'll fix it.

--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev
Conrad Lara | 10 Jul 16:57 2015
Picon
Picon

Re: Migration from olsrd v1 to v2


I won't classify the networks I work with as dense, we use it extensively on every device.

Emergency Communications full redundancy and no centralized point of failure is a mandatory system spec
for the project I work with where devices will come and go and there is no guarantee of a set command
structure and a split must be presumed to happen at any moment.

I do agree with the concern on flooding data it's a tough subject. I know that's been tried to be lessened in
the past on some parts by doing tried floods (1 hop, 3hop IIRC, 255 hop)  reduce flooding but increase
convergence time.

Sent from my iPhone

> On Jul 10, 2015, at 4:24 AM, Henning Rogge <hrogge <at> gmail.com> wrote:
> 
> The reason why I ask is that I would like to build something that does
> NOT flood this (static) information every 30 seconds through the whole
> mesh.
> 
> Henning
> 
>> On Fri, Jul 10, 2015 at 1:33 PM, Bastian Bittorf <bittorf <at> bluebottle.com> wrote:
>> * Henning Rogge <hrogge <at> gmail.com> [10.07.2015 13:24]:
>>> So a direct question to everyone here on the list, do you deploy the
>>> plugin on ALL nodes of a mesh? I have some ideas about how to replace
>> 
>> yes here - in all networks.
>> 
>> bye, bastian
> 
> -- 
> Olsr-dev mailing list
> Olsr-dev <at> lists.olsr.org
> https://lists.olsr.org/mailman/listinfo/olsr-dev

--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev

sp2ong | 10 Jul 08:48 2015
Picon

Migration from olsrd v1 to v2

Hi,

We have use in our local mesh network openwrt olsrd v1 with configuration which I attach below.

How to try migrate from olsrd v1 to olsrd v2 ? all features like plugins nameservices jsoninfo are available in olsrd2 ??? It is good time to migrate from v1 to v2 or too early for this process?

Regards

Waldek

====== olsrd v1 conf ================

config olsrd
        option IpVersion '4'
        option FIBMetric 'flat'
        option AllowNoInt 'yes'
        option TcRedundancy '2'
        option NatThreshold '0.75'
        option Pollrate '0.1'
        option LinkQualityAlgorithm 'etx_ffeth'
config LoadPlugin
    option library 'olsrd_arprefresh.so.0.1'
config LoadPlugin
    option library 'olsrd_httpinfo.so.0.1'
    option port '1978'
    list Net '0.0.0.0 0.0.0.0'
    option Resolve 'true'
config LoadPlugin
    option library 'olsrd_txtinfo.so.0.1'
    option accept '127.0.0.1'
    option port '2006'
config LoadPlugin
    option library 'olsrd_jsoninfo.so.0.0'
    option accept '127.0.0.1'
    option port '9090'
config LoadPlugin
    option library 'olsrd_watchdog.so.0.1'
    option file '/tmp/olsrd.watchdog'
    option interval '30'

config InterfaceDefaults
        option MidValidityTime '500.0'
        option TcInterval '2.0'
        option HnaValidityTime '125.0'
        option HelloValidityTime '125.0'
        option TcValidityTime '500.0'
        option Ip4Broadcast '255.255.255.255'
        option MidInterval '25.0'
        option HelloInterval '3.0'
        option HnaInterval '10.0'
config Interface
    list interface 'mesh'
    option Mode 'mesh'
    option Ip4Broadcast '255.255.255.255'
config LoadPlugin
    option library 'olsrd_nameservice.so.0.3'
    option sighup_pid_file '/var/run/dnsmasq.pid'
    option name_change_script 'touch /tmp/namechange'
    option suffix '.ampr.org'
    option interval '30'
    option timeout '300'
    option services_file '/var/run/services_olsr'
    option lat '52.23'
    option lon '17.0123'
     option name 'N0CALL'
--

-- 
Olsr-dev mailing list
Olsr-dev <at> lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-dev

Gmane