[Olsr-dev] brainstorming for new feature - HNA routes read from the kernel

[L. Aaron Kaplan]

Well, it does make sense in certain setups.

Let me give you an example: we have a tunnel server which connects FF Graz and Vienna and other community networks.
Between them, they speak BGP.
It might make sense to dynamically re-distribute certain announcements to the FF Vienna OLSR mesh cloud (or filter them out - depending on the intentions of the sysadmin).

So, yes, I do see a use-case for this which extends static HNA announcements.

sorry for TOFU quoting, I knooow :)

On Feb 25, 2013, at 7:58 PM, Saverio Proto <(spam-protected)> wrote:

> Hello,
> 
> this email is about implementing a new feature that I like because I
> experienced it in babeld.
> 
> in babeld you dont configure HNA networks in the config file, you tell
> babel to redistribute routes from the kernel that match a specific
> protocol (for example static). There are also filters to prevent
> distribution of stuff you dont want to distribute.
> 
> I find this approach much more flexible and dynamic of the one we have
> now, with HNA fixed in the configuration file and immutable unless a
> demon restart.
> 
> I think porting this feature to olsrd is a must, and we can reuse some
> babeld code :)
> 
> Also, this could be a task for a GSoC 2013 student ?
> 
> This is just brainstorming at the moment.
> 
> ciao,
> 
> Saverio
> 
> -- 
> Olsr-dev mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-dev