[Olsr-dev] netjson plugin

[Conrad Lara]

I'm not an expert on netjson,   did I miss a line that says "known" links are local only on my quick read? If not doesn't OLSR "know" about all the links because of the OLSR packet forwarding?(dot_draw determines this already somehow to draw it's graphs)

Just because one isn't directly connected to the link doesn't mean (unless RFC says so) that you don't know about it.  The RFC calls for a source and  destination id for the link mapping. That could easily handle showing the remote node. If the source was just the same node why would the protocol call for a source node ID definition when's just a destination would tell you everything you need because the link could only be local? It also doesn't state that the source id must be the presenting node.

A quick google already showers at least one test sample file that shows this in action as part of the system test for netdiff https://github.com/ninuxorg/netdiff/blob/master/tests/static/netjson-3-links.json that it shows more then one source for the links to display (this is by no means a RFC proof of course as its not from the official source but makes me think this deserves more in depth discussion)


Sent from my iPhone

> On Apr 21, 2016, at 12:48 PM, Ferry Huberts <(spam-protected)> wrote:
> 
> 
> 
>> On 21/04/16 20:47, Gabriel wrote:
>> Hi, I've finally managed to get the netjson plugin working.
>> 
>> I noticed that the "links" section contains just the 1-hop links.
>> The NetworkGraph should be a representation of the whole network as
>> edges and nodes.
> 
> Incorrect, the RFC says:
> 
>> Definition: a list of nodes and links known by a node.
> 
> See http://netjson.org/rfc.html#rfc.section.4
> 
> 
> If you want the whole network, you must query all nodes and combine the info.
> 
> 
>> 
>> Is it just a bug or it has been implemented to contain just the 1-hop links?
>> 
>> 
>> Gabriel
> 
> -- 
> Ferry Huberts
> 
> -- 
> Olsr-dev mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-dev