Moe,

The connectivity you show with your traceroute might exist, but I can't connect to, or display node status pages for the south Dayton nodes.

When viewed from the mesh status page of my services node, I see no remote nodes beyond XWARN, (unless tunnelled directly to me, and my tunnel to DARA is down).  I do see the Wilmington and NJ nodes.

When viewed from my Omni's Mesh Status page, the Dayton South nodes (meaning all the MVHS connected nodes, NC8Q, LRJ, etc) do show up as remote nodes, but I cannot connect to any of them to bring up their node status page.

Likewise, I can view the mesh status page of the DARA node connecting to XWARN, and see the Dayton South nodes as remote nodes, and again, cannot connect to any of them to display their node status info. 

I expect this may be the OLSR Storm block working; I don't know how it works, but it looks like it blocks mesh status (OLSR) information from nodes that are more than X hops away. 

At this point, I wonder if network connectivity (the ability to both route AND pass traffic) to these nodes is preserved, even while passing node status information is blocked.  Your traceroute showed routing connectivity, and yet I was unable to bring up status pages for any of the south nodes, even when I could see them as remote nodes on my Omni's Mesh Status page.

Bill

On Sun, Oct 31, 2021, 12:16 AM Moe <ab8xa@luffshack.com> wrote:


On Oct 30, 2021, at 22:37, William Curtice <william.curtice@gmail.com> wrote:

I can no longer see any of the MVHS nodes; no NC8Q nodes,  no KE8MVM nodes, no W8LRJ nodes, no W6CDR nodes, no N8NQH nodes, no KI7ODK.  

Where is this not working? (nodes names paraphrased). Try traceroute or mtr..

WA8APB-OMNI <-> XWARN-OMNI
XWARN-TO-DARA-LHG <-> DARA-TO-XWARN-LHG
NC8Q-DARA-TO-MVHS-LHG <-> NC8Q-MVHS-TO-DARA-LHG
NC8Q-MVHS-TO-KETTERING <-> NC8Q (down now)
NC8Q-MVHS-TO-P-PLAZA <-> NC8Q-P-PLAZA
NC8Q-MVHS-TO-BELLBROOK <-> N8NQH
NC8Q-MVHS-TO-BEAVERCREEK <-> W8LRJ
W6CDR-MVHS <-> W6CDR-MadRiver