Node Name not resolving, not connecting, showing Wi-Fi address in list N-1145+ on UBNT 32MB devices with NO RF or Marginal RF connection

[k1ky]

Nightly 1145 on some 32MB Devices isn't connecting (DTD) and is showing the Wi-Fi addy of the non-connecting node in the node list. I've seen this issue with N-1145 on all nodes and with older versions on other nodes. This is happening so far with some UBNT AirRouter and UBNT Nanobridge devices. Issue probably popped up since the Services fix.


supportdata-K1KY-ARAR-900-LAVERGNE-202204172113.zip
supportdata-W4GHD-RKM5XW-109-LAVERGNE-100TWR-345-202204172121.zip

[aanon4]

The log file of 900-LAVERGNE indicates that OLSRD errored while trying to talk to the dtdlink network interface, although later parts of it recovered. Did rebooting either of the nodes change anything.

Also - as both these nodes appear to have configured Mesh WiFI, the "Service fix" is not active.

[k1ky]

Reboots usually no change, however I just rebooted the Rocket and the name did resolve now, but still can't "connect" to the node by selecting the link. I have other units at the site that are doing the same thing. Rebooting them also seem to fix the name resolution, but still can't connect to the GUI. I'm pretty sure that earlier reboots did not help. I have a computer connected directly to the AirRouter at the site and it does connect to the GUI.

[k1ky]

Further review after reboots - Selecting the AR-900 unit from units that are DTD connected at the site will now connect to the GUI, but other nodes on the network away from the site don't show the AR-900 in the node list. I can access the AR-900 by entering http://10.33.237.33:8080/ directly in my browser on a computer connected to the network away from the site.

[k1ky]

After a day of stabilization, the AR-900 shows up in the node list, but won't connect away from the MESH site. It shows the "redirecting message" and then fails to connect - screen shot below: C:\Users\k1kyt\My Drive\MESH_HAMNET\SUPPORT_DATA\2022-04-18 22_44_46-k1ky-arar-900-lavergne.local.mesh.png

[k1ky]

More info. This seems to happen when the affected node doesn't have a or any good RF path or connection when RF is enabled. I suspect it has something to do with when DTD connections to such nodes resolve to the Wi-Fi addy instead of the LAN addy of the node.

Where 10.68.249.125 is the WIFI addy of the DTD connected AirRouter node and RF is turned off. Interesting to note that network traffic does appear to pass through the node in question - it just won't resolve name and won't connect to the GUI across the network. I believe it will connect to the GUI if a computer is connected directly to the node.
Hope this helps,

[k1ky]

This appears to be limited to 32MB UBNT devices. I am still able to connect DTD to a PBEM5XW with RF not connected. or RF disabled.

[k1ky]

This issue still exists with Nightly 1191 as of 4/26/22 and 1222 as of 5/2/22. Primary concern is with AirRouter with no RF or margingal RF connection that is DTD connected to network.

[k1ky]

Issue seems to be resolved as of Nightly 1235. Both no RF and Marginal RF connection now resolve and connect throughout the network. This appeared to be mainly an AirRouter issue. I'll close this issue and revisit if any further problems are discovered.