You are here

4.26.1.0, Neighborhood Nodes not functioning as expected

4 posts / 0 new
Last post
N4SV
4.26.1.0, Neighborhood Nodes not functioning as expected
Picked up a couple of new devices compatible with the latest Babel version 4.26.1.0.  AREDN load went OK, after a bit of work with TinyPXE, now both nodes are loaded and functional...sort of.  Reading the latest docs under the Neighborhood Nodes section, and neither of my nodes are working as expected (from the way they worked in previous builds) and not according to the docs.  First, instead of the neighbor node name, that node's MAC address is showing, same on both nodes seeing them other over 2.4 GHz RF, channel -1 at 10 MHz.  In previous builds, the neighbor node name was a clickable link to go to that nodes interface, not working that way with my two nodes.  Plus if I hover the mouse over the neighbor node name (MAC address) it states "Link:disconnected".  I've been digging into both the 4.26.1.0 docs, as well as the "latest" docs, and the neighbor nodes function is just not working as documented, and as I am used to them working in previous builds.  There is certainly a possibility I have something mis-configured, but I followed all the documentation for loading the kernel and then the squash version, that all went as described.  My new devices are both Mikrotik, a hAP AC2 and an SXT sq Lite2.  So any help, doc reference or troubleshooting info appreciated.  I'm trying to embrace the new Babel as well as the new node GUI interface (I'm used to the look and feel of the original AREDN GUI, but trying to learn the new) but need some pointers. 
nc8q
nc8q's picture
node's MAC address is showing
N4SV:

Are both nodes in any way wire-connected?
(ethernet connected?, via an ethernet switch?)

How are the 2 nodes configured?
AC2 ........... SXT
 ?  Mesh ....... ?
 ?  Mesh PtMP .. ?
 ?  Mesh PtP ... ?
 ?  LAN Hotspot  ?
 ?  WAN Client . ?
Maybe not important to your issue, but
why are you sharing bandwidth with Part 15 channel '1' Wi-Fi?

73, Chuck
 
N4SV
Node status
Chuck, there is no wired connection between the nodes, they are strictly RF but located within the same room for testing.  Both are configured as "Mesh".  And as I indicated they are on channel -1, 2402 Mhz, so not within the shared Part 15 segment.  There is significant other 2.4 GHz equipment on premises, including the legacy AREDN network on older Ubiquiti devices, same channel and bandwidth...do you think there is an interference possibility? 
N4SV
UPDATE
I made a couple of changes which seems to have fixed the issue.  First I moved both devices from channel -1 to channel -2, then I also added the Lat/Lon for both.  Even thought both are currently in the same room I have the Lat/Lon separated by about 40 virtual miles.  Now both devices are seeing the other via RF and the Neighborhood Nodes are correct in each node, showing the other node and the node name (rather than the MAC as before).  And the node name is now a clickable link to access the other nodes AREDN config interface.  All appears to be functioning normally.  Now over time I'll purchase upgraded devices to replace the remaining older Ubiquiti devices, and then the entire network will have been upgraded.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer