wireless link between OLSR-enabled nodeA and non-OLSR-enabled nodeB that has its IP address announced in an HNA of nodeA

[cl4u2]

In the ninux Rome network, that uses OLSR, there are some wireless links built in the following way:

• on one side of the wireless link a device that does NOT talk OLSR, with IP address IP_X
• on the other side of the wireless link a device talking OLSR that announces as HNA a subnet that includes IP_X

The consequence is that IP_X does not appear explicitly in the OLSR topology returned by the txtinfo and jsoninfo olsrd plug-ins.

This means that, to have a complete topology, either:

• the application using netdiff should verify the matching between the IP addresses of the known devices and HNAs
• the application using netdiff should pass to netdiff the list of know devices, so that netdiff can do the matching between IP addresses and HNAs
• netdiff should return explicitly the list of all the hosts that could belong to the HNA. For example 254 hosts for a /24 HNA.

[gabri94]

I think this use case is just the result of a weird use of OLSR.
Covering this use case in the Olsr1Parser will introduce other problems like the other one related. Maybe we should just draw this weird links in a static way from nodeshot, just looking if one of the two endpoints is connected to the rest of the graph.
Otherwise, if we want to it dinamically, we can do another netdiff parser that implements just this use case, with a json of the hna's special links as input parameter.

[cl4u2]

I would investigate if this use case can be generalized to other routing protocols.

[nemesifier]

@cl4u2 let's find a name for both issues, eg: wireless link between OLSR-nodeA and non-OLSR nodeB which has ip announced in HNA of OLSR-nodeA