[Olsr-dev] Migration from olsrd v1 to v2
Thu Jul 30 14:19:01 CEST 2015
Can Quagga import data from routing tables?
On Thu, Jul 30, 2015 at 2:15 PM, Bastian Rosner <(spam-protected)> wrote:
> Quagga and OLSRv1 can exchange routes via plugins.
> Bird and OLSRv2 can exchange routes via kernel tables.
> Quagga and Bird can exchange routes via BGP.
> Doesn't that mean that we can somehow exchange routes between OLSRv1 and
> OLSRv2 via BGP? Am i missing something?
> Of course we would loose metrics, at least in case of routes exported to a
> OLSRv1 mesh as HNA.
> Am 28.07.2015 12:59, schrieb Henning Rogge:
>> On Tue, Jul 28, 2015 at 12:44 PM, Saverio Proto <(spam-protected)>
>>>> maybe it is too early for production.
>>>> our migration path is: olsrd2 for IPv6 and olsrd1 for IPv4
>>>> (which means: if there is something wrong with IPv6 you can still use
>>> That looks like a reasonable migration path.
>>> If I think of a migration path for Ninux Roma, this could be a possible
>>> However we get our IPv6 upstreams from special severs that run IPv6
>>> BGP(quagga) / olsrd1 with quagga plugin.
>>> I have no idea if olsrdv2 interacts with Quagga at the moment. Does it ?
>>> If not that could be a blocking feature to propose the upgrade in Ninux
>>> I think this is something worthed to be discussed at the Battlemesh.
>>> Unfortunatly this year I will not make it to be there.
>> It should be quite easy to integrate Quagga in olsrd2... if you have
>> experience with Quagga.
>> I have never worked with Quagga myself, so this is a problem. We
>> cannot use Quagga's Zebra library because it is GPL, which is in
>> conflict with the OONF license.
>> I would really like to have a clean rewrite of the necessary Zebra
>> client code to get something with a clean license... the Quagga plugin
>> for olsrd has a hack as a license.
>> So if you find someone to do the work towards the Quagga side I will
>> do the work on the OONF side.
> Olsr-dev mailing list
More information about the Olsr-dev