<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 01/23/2014 08:44 PM, Stefano De Carlo wrote:<br>
<span style="white-space: pre;">> Il 22/01/2014 22:44, Clauz ha
scritto:<br>
>> Hi, Stefanauss.<br>
>> This is the code you are looking for:<br>
>>
<a class="moz-txt-link-freetext" href="https://github.com/ninuxorg/nodeshot/blob/master/nodeshot/scripts/read_topology_hna.py">https://github.com/ninuxorg/nodeshot/blob/master/nodeshot/scripts/read_topology_hna.py</a><br>
>><br>
>> The topology information, in "OLSR txtinfo plug-in
format" is fetched<br>
>> from URLs belonging to different islands which may use
different routing<br>
>> protocols. Links are drawn if the nodes are seen as
connected in these<br>
>> topologies. The color depends on the quality of the
links.<br>
><br>
> Hi Clauz,<br>
> thanks for your answer!<br>
> So, first things first: the URLs. They are the ones in
settings.py,<br>
> OLSR_URLS array, right?<br>
> In the nodeshot github the only URL that's reported it's the
default one<br>
> for the txtinfo plug-in (localhost:2006), so I guess it's
just a stub?</span><br>
<br>
Yes it's a stub.<br>
<br>
<span style="white-space: pre;">> Thanks to this, I've realized
that the our node hlcs in the VPN Isole<br>
> wasn't running the txtinfo plugin, so I loaded it and granted
access for<br>
> every address (0.0.0.0).<br>
> Despite that, still the link didn't appear.<br>
> On our node, echo "/all" | nc localhost 2006, contains the
desired link<br>
> in the Topology table, which it appears from a quick reading
of the code<br>
> the table the mapserver is targeting.<br>
><br>
> Table: Topology<br>
> Dest. IP Last hop IP LQ NLQ Cost<br>
> 172.17.87.4 172.17.87.2 1.000 1.000 1.000<br>
><br>
> Then I figured: do the other topology urls contain it? I
didn't know any<br>
> of them, so I tried vpnisole.ninux.org and got lucky:<br>
><br>
> echo "/all" | nc vpnisole.ninux.org 2006<br>
><br>
> I get over 1000+ line of topology, but our link isn't in
there. That's<br>
> our main issue, I guess.</span><br>
<br>
Let's see, in our config we have:<br>
<br>
BATMAN_URLS=[<a class="moz-txt-link-rfc2396E" href="http://eigenlab.org/topolinia">"http://eigenlab.org/topolinia"</a>,
<a class="moz-txt-link-rfc2396E" href="http://coppermine.eigenlab.org/battxtinfo.php">"http://coppermine.eigenlab.org/battxtinfo.php"</a>,
<a class="moz-txt-link-rfc2396E" href="http://10.0.5.100/data.txt">"http://10.0.5.100/data.txt"</a>]<br>
OLSR_URLS=[<br>
<a class="moz-txt-link-rfc2396E" href="http://127.0.0.1:2006/all">"http://127.0.0.1:2006/all"</a>, # roma<br>
<a class="moz-txt-link-rfc2396E" href="http://topology.ninux.l0g.in/ipv4/">"http://topology.ninux.l0g.in/ipv4/"</a>, # firenze<br>
<a class="moz-txt-link-rfc2396E" href="http://leto.korneolo.net:2006">"http://leto.korneolo.net:2006"</a> # vicenza<br>
]<br>
<br>
So, firenze and vicenza have their own OLSR txt info file reachable
via internet, and we parse that.<br>
<br>
For Vitrerbo and Reggio Calabria we surely can see thei routes in
our topology, because the links are drawn.<br>
<br>
In Cosenza's case, either we have (Roma) have to see your routes in
our topology or you can make one of your txt-info plugins reachable
in some way (a ninux ip address would be fine too) and send us the
URL (make sure the file is reachable and downlodable).<br>
<br>
<span style="white-space: pre;">><br>
> Are these OLSR_URLS entries manually written in the settings
file or is<br>
> there some script that it's not working for us?<br>
> If that's all manual, how do we get our URL into the
settings.OLSR_URLS<br>
> array?<br>
> Could we get the current list of Islands URLs? it might be
useful for<br>
> debugging purposes.<br>
><br>
> On the VPN Isole, our node has address 10.0.5.6, and txtinfo
plugin on<br>
> port 2006 seems to work fine.<br>
><br>
> Other questions: how often the mapserver refreshes the link?
If the<br>
> status is set to "reachable" in the admin panel, and then the
link<br>
> doesn't appear in the topologies when the read_topology
script is<br>
> executed, does Nodeshot automatically set to unreachable?<br>
><br>
> I have another idea about what could be going on.<br>
> We didn't compile and run OLSRd integration for babeld as
suggested in<br>
> <a class="moz-txt-link-freetext" href="http://wiki.ninux.org/IsoleVPN">http://wiki.ninux.org/IsoleVPN</a>.<br>
> We thought it would be just fine to announce our entire
assigned ip<br>
> range in babeld.conf<br>
><br>
> # redistribute our ip range<br>
> redistribute ip 172.17.87.0/24 proto 157<br>
> redistribute ip 10.87.0.0/16 proto 157<br>
><br>
> but doesn't this mean we lost every topology information the
map server<br>
> might need to draw the links?<br>
><br>
><br>
>> There were attempts to make the code cleaner, but there
are a lot of<br>
>> exceptions (e.g. VPN links) and details (e.g. OLSR MIDs)
that also pop<br>
>> up as community networks evolve (e.g. "ground routing").<br>
><br>
> Ground Routing, that's our case :)<br>
> We mirror very closely the Firenze configuration, which is
working in<br>
> the map server, so I don't think that's a factor in our case.
Might be<br>
> wrong, ofc.<br>
><br>
>> Don't hesitate to ask. Perhaps it would be nice to
arrange a short<br>
>> remote tutorial on how this script works?<br>
><br>
> That would be very nice. Let me know the means you prefer for
that and<br>
> I'll reach out to you next week (I'm not at home atm).<br>
> Ofc We'd be grateful if you also could elaborate on our
questions in<br>
> this thread. =)<br>
><br>
></span><br>
<br>
Clauz is more informed on these other doubts.<br>
<br>
Federico<br>
<br>
</body>
</html>