<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Yeah, if we have a node A with a neighbor B, that will be the cost
from A to B.<br>
The cost from B to A, that could be different, will be in the node B
section.<br>
<br>
<br>
Gabriel<br>
<br>
<div class="gmail_quote">Il 17 febbraio 2015 13:00:31 CET, Henning
Rogge <a class="moz-txt-link-rfc2396E" href="mailto:hrogge@gmail.com"><hrogge@gmail.com></a> ha scritto:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex;
border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">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 <a class="moz-txt-link-rfc2396E" href="mailto:gabriel@autistici.org"><gabriel@autistici.org></a> wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">
On 17/02/2015 12:44, Henning Rogge wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> On Tue, Feb 17, 2015 at 12:29 PM, Gabriel <a class="moz-txt-link-rfc2396E" href="mailto:gabriel@autistici.org"><gabriel@autistici.org></a> wrote:
<blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"> 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</blockquote>
At the end we got multiple topologies in the olsrv2info plugin? or these
multiple topologies with different metrics get joined in one?
</blockquote>
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.</blockquote>
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
</blockquote></pre>
</blockquote>
</div>
</body>
</html>