[Interop-dev] Topology JSON

Gabriel (spam-protected)
Tue Feb 17 19:57:21 CET 2015

Yeah, if we have a node A with a neighbor B, that will be the cost from
A to B.
The cost from B to A, that could be different, will be in the node B


Il 17 febbraio 2015 13:00:31 CET, Henning Rogge <(spam-protected)> ha

    Let me just check the current version again...

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


    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 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.funkfeuer.at/pipermail/interop-dev/attachments/20150217/534dff16/attachment.html>

More information about the Interop-dev mailing list