[Interop-dev] link-specifc / interface-specific / neighbour link data [was: RFC: add parameter link-type]

Henning Rogge (spam-protected)
Fri Sep 4 12:53:04 CEST 2015


On Fri, Sep 4, 2015 at 12:41 PM, Nemesis <(spam-protected)> wrote:
> Is there an equivalent of this in olsrv1 jsoninfo plugin?

txtinfo and jsoninfo should deliver the second and third one... (olsrd
has no concept of linklayer data)

Still, olsrv1 also lacks link-specific information about its two-hop neighbors.

> Or anything else in one of the olsrv2 plugins?
the first would be a combination of "layer2info" and "nhdpinfo", the
second one would be "nhdpinfo" only and the third one is "olsrv2info".

> If yes, could you please send some attachments to look at?
I am already using the same data-sources as nhdpinfo/olsrv2info to
build my current netjson output. I am not sure what you are looking
for.

> Also, the most important question IMHO is not what could we do with it?
> But what do we want to do with it? What's the most pressing need?

I think all of them ARE interesting, it depends what you want to do.

If you want to visualize the local knowledge of a node, got for the
node- but not link-specific topology data.

If you combine information from all mesh nodes, go for the link-set of
neighbors and build you own image.

Henning




More information about the Interop-dev mailing list