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.

Are both nodes in any way wire-connected?
(ethernet connected?, via an ethernet switch?)
How are the 2 nodes configured? Maybe not important to your issue, but
why are you sharing bandwidth with Part 15 channel '1' Wi-Fi?
73, Chuck
You may alter the lat/lon of each node to 'make them look nicer on a map'.
I recommend keeping all co-located (DtD'ed) nodes within a virtual distance of 100 meters.
73, Chuck
Not sure what you are trying to do with locations of co-located nodes. I have about a dozen nodes here with same lat/lon to within about 0.0005 deg. On the AREDN map,they are spread nicely. I am east of Plano TX, NE of Dallas, if you want to look.
And nodes are running nothing older than 4.26.1.0. They link to each other via tunnels 100%. There is an issue with rf links in Mikrotik nodes at the moment, but there is a workaround. I have abut 8 nodes linked via Ch -2 rf, and Neighborhood list shows by node names a few minutes after the node comes up.
--Tim K5RA