[Interop-dev] Topology JSON
Tue Feb 3 08:18:07 CET 2015
OLSR(v2) makes the same difference...
"neighbors" are connection between nodes... "links" are interface
specific connections between nodes.
OLSR(v2) generates the "neighbor" information from the HELLO protocol
that generates the "link" information.
On Mon, Feb 2, 2015 at 11:27 PM, Nemesis <(spam-protected)> wrote:
> I was talking with Gabriele Gemmi who is helping me implementing NetJSON to
> convert OLSR jsoninfo and batman alfred-vis into netjson.
> We were considering defining another object specific to topolgy, because the
> other is focused on routes.
> Something like this object:
> This reasoning came after Simon Wunderlich's feedback, written here:
> Simon Wunderlich:
> It may be interesting to track neighbors per interface for multi-radio nodes
> as well, and track primary/secondary interfaces - at least this is what
> alfred/vis in batman-adv can do (check the illustrations):
> http://www.open-mesh.org/projects/open-mesh/wiki/Alfred#batadv-vis In
> general it sounds like a good idea to have a single format to feed different
> drawing applications, although I'm not enough involved in these kind of
> things to judge the usefulness. For alfred-vis we have two formats, one is
> the classic graphviz-compatible output which is similar to the old OLSR
> output, and another JSON output.
> Gabriel's response:
> Gabriele Gemmi:
> I think we should have a different representation for the topology
> information, i've made another pad to develop the json structure see:
> What do you think?
> Please retain CC.
> Interop-dev mailing list
More information about the Interop-dev