ErroRs

=== locust world mesh networking === 
It seems I took this to the wrong channel, as my employer receives direct support.
However, I just wanted to comment that although what you say is undoubtedly true, the fact remains that reporter shows no route to boxes that in fact are reachable, and occasionally lists boxes to which there is apparently no route via SSH.
Don’t take the map too seriously, it takes a very long time for it to up date a couple of days at least.
 
I'm having intermittent problems connecting directly between some of the boxes on our mesh via the 1.x.x.x addresses.
Even if reporter shows an available route, when there are 2+ hops to the target box, it's hit and miss whether I can SSH to it directly. Is this at all related to whether the route is verified by the known_hosts files on each box?
Also, looking at the realm graph at Locustworld, I can see which boxes are connected in a contiguous mesh, but this information is not reflected in the output of reporter. Reporter show most of the boxes shown to be contiguous by the graph, but normally omits one or two
Occasionally, I can SSH to a box shown to be linked in on the graph, which is not listed by reporter.
Our boxes are using build 1939.
=== links ===
MeshNetworking , MeshCommands , MeshCamAndRouters
Category:Sasecurity
Category:Mesh