Hello all, add this to the search/crawl/info missing in Babel only build list ...
Just now I wanted to do a traceroute and iperf3 from my location to a node some distance away on our mesh. I know the node exists, but using the tools menu in the lower left corner on a node running 3.25.10.0 the node is not found the normal way by typing a few characters of the node name into the search field. Whatever process crawls the mesh and finds the other nodes is blocked I suspect at the same point in our mesh where a node has Babel only applied ... the node does show up in my "see what is on the local babel mesh" list and when I manually type the node name into the iperf3 and traceroute fields the tools function.
I don't know the sum total of the functions now working now with a mix of 3.25.10.0 and Babel only ... but am tracking
RMS Express and RMS Relay ... AREDN Winlink Post Office advertising to add AREDN Post Offices no longer works on 3.25.10.0 across a Babel only divide but does now work if your node is Babel only (so now fixed so long as everyone operates Babel only nodes ... so will eventually resolve)
Meshinfo by Scott Searcy (KI7ONK) depends on a function of OLSR. Meshinfo and Meshmaps (the ones without internet) don't pick up nodes beyond a Babel only barrier in the mesh. Scott is aware of the issue and is working on it. This version of Meshmap is so far as I'm aware the only one that will function when internet has failed and we like how customizable it is.
And now the embedded search tools for traceroute and iperf3 don't find nodes in the search process.
I don't know what else depends on these OLSR packages for discovery of the mesh topology, but I'm sure there are others. The way to tell is that your service or tool used to show you XXX different nodes, but now only shows you XX nodes. I didn't post this at Github as it's not a new issue, just seems to be related to the existing issue.
Ed
Just now I wanted to do a traceroute and iperf3 from my location to a node some distance away on our mesh. I know the node exists, but using the tools menu in the lower left corner on a node running 3.25.10.0 the node is not found the normal way by typing a few characters of the node name into the search field. Whatever process crawls the mesh and finds the other nodes is blocked I suspect at the same point in our mesh where a node has Babel only applied ... the node does show up in my "see what is on the local babel mesh" list and when I manually type the node name into the iperf3 and traceroute fields the tools function.
I don't know the sum total of the functions now working now with a mix of 3.25.10.0 and Babel only ... but am tracking
RMS Express and RMS Relay ... AREDN Winlink Post Office advertising to add AREDN Post Offices no longer works on 3.25.10.0 across a Babel only divide but does now work if your node is Babel only (so now fixed so long as everyone operates Babel only nodes ... so will eventually resolve)
Meshinfo by Scott Searcy (KI7ONK) depends on a function of OLSR. Meshinfo and Meshmaps (the ones without internet) don't pick up nodes beyond a Babel only barrier in the mesh. Scott is aware of the issue and is working on it. This version of Meshmap is so far as I'm aware the only one that will function when internet has failed and we like how customizable it is.
And now the embedded search tools for traceroute and iperf3 don't find nodes in the search process.
I don't know what else depends on these OLSR packages for discovery of the mesh topology, but I'm sure there are others. The way to tell is that your service or tool used to show you XXX different nodes, but now only shows you XX nodes. I didn't post this at Github as it's not a new issue, just seems to be related to the existing issue.
Ed
Orv W6BI