You are here

2 nodes listed as Current & Previous Neighbors

4 posts / 0 new
Last post
WA6MZW
2 nodes listed as Current & Previous Neighbors

The Toro Mesh Status.jpg shows
KE6BXT-Toro-M5R-INDIO 
and 
KE6BXT-M5R-Tem-11
listed twice.  Once for Current and once for Previous Neighbors.  The 3 nodes (including KE6BXT-Toro-M5RXW-128) have never shared the same channel and therefore never should have been in the previous neighbors.  Each node is running a different channel and are connected dtd.  All 3 nodes are running VERY slow to no connection.  I was able (over an hour to download) to download the support data for KE6BXT-Toro-M5RXW-128.
KE6BXT-Toro-M5RXW-128 is running firmware 634-837a3c6

File Attachment: 
w6bi
w6bi's picture
Screenshot
Dale, reload the Mesh Status screenshot as a .jpg file.  It will then be visible.
Orv W6BI
WA6MZW
2 nodes listed as Current & Previous Neighbors
Here is the JPG
Image Attachments: 
AE6XE
AE6XE's picture
"Each node is running a
"Each node is running a different channel and are connected dtd."

From memory, it's possible mesh status will show the RF path as a previous neighbor, if that path goes down.   The RF and DTDLink paths have unique IP addresses and paths.   The Mesh status page converts all IP addresses in use to the main hostname and IP address of the node, so it hides the fact that the dtdlink path uses different hostnames and IP addresses.     Generally, if you can turn off mesh RF, because the dtdlink hard cable path is cleaner to use, and there are no other RF neighbors, then do so, to avoid confusion.

Joe AE6XE

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer