Updated nodes to 3.20.3.1 and meshmap nnow does not show the tunnels and reports the node as DTD.
The node does report tunnel looking at the mesh status page ont the node. This issue appears not to be hardware relayed as we have tunnels with rockets
GL/s and nanostation. Upgraded the meshmap scripts from Eric (KG6WXC) thinking that was the issue with no luck.
Any ideas ?
Thank you
Bill
You are here
Meshmap and 3.20.3.1 not displaying tunnel and report node as DTD
Sat, 07/11/2020 - 17:27
#1
Meshmap and 3.20.3.1 not displaying tunnel and report node as DTD
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
Two items.
1. The function does not account for tunnel with a cost of 0.1 which is the case with 3.20.3.1.
2. Node Distance seems to come into play as the function assumes that a DTD link would not be greater
than a mile.
Bill
In any case, a version update may help.
Orv W6BI
My meshmap's node's links seem correct.
Node is Mikrotik hAP:
Node Name (cost to/from) distance bearing
NC8Q-uAP1 (DTD) 0.01mi (0.01km) 217.5°
NC8Q-uAP2 (DTD) 0.01mi (0.01km) 90°
NC8Q-M2-34 (1/1) 17.61mi (28.34km) 147.7° <-- tunnel
Chuck
The first thing is did was a git t pull down the latest meshmap with no luck. I verified that the git did give new files.
Eric said he will look at it.
Updated nodes to 3.20.3.1 and meshmap nnow does not show the tunnels...
My meshmap shows tunnels as gray lines.