Our mesh is pretty large and covers two cities. I have a repeater (room server) I would like to monitor that is 6 hops away and roughly ~45km. When attempting to add monitoring to one such repeater the expected anon_request floods out over the mesh. The repeater responds and provides path info but not before the integration times out, and, funnily enough, the path to that contact updates for future attempts despite saying timed out.
You can see this from the below. Five repeats is a direct path, ~20 repeats is a flood.
Even with the direct path though the integration is still timing out what seems like right before the response is received. On my personal companion when I log into this node it waits a very very long time before timing out over 6 hops (and then lets me in). These images are from different attempts but you get the idea.
Our mesh is pretty large and covers two cities. I have a repeater (room server) I would like to monitor that is 6 hops away and roughly ~45km. When attempting to add monitoring to one such repeater the expected anon_request floods out over the mesh. The repeater responds and provides path info but not before the integration times out, and, funnily enough, the path to that contact updates for future attempts despite saying timed out.
You can see this from the below. Five repeats is a direct path, ~20 repeats is a flood.
Even with the direct path though the integration is still timing out what seems like right before the response is received. On my personal companion when I log into this node it waits a very very long time before timing out over 6 hops (and then lets me in). These images are from different attempts but you get the idea.