[Interop-dev] Topology JSON

[Henning Rogge]

Let me just check the current version again...

the "weight" value is the metric cost of the link towards the neighbor?

Henning

On Tue, Feb 17, 2015 at 12:58 PM, Gabriel <(spam-protected)> wrote:
>
>
> On 17/02/2015 12:44, Henning Rogge wrote:
>> On Tue, Feb 17, 2015 at 12:29 PM, Gabriel <(spam-protected)> wrote:
>>>> Yes, olsrd2 is multi-topology capable.
>>>>
>>>> In practice this means you run multiple routing metrics, transport
>>>> multiple metric values in the Hello's/TCs, run the dijkstra multiple
>>>> time and write the results in different routing tables.
>>>>
>>>> Henning
>>>>
>>>
>>> At the end we got multiple topologies in the olsrv2info plugin? or these
>>> multiple topologies with different metrics get joined in one?
>>
>> You get one JSON entry for each value for each metric.
>>
>> So if you are running 2 topologies, you get two times the JSON arrays.
>>
>> Thats why there is a "domain" number in each of the JSON arrays.
>>
>
> So i don't see particular problems with our json representation.
>
> we can have multiple topology json, with each metric specified in the
> proper attribute.
>
> Gabriel