This thread points to a DNS bug based on some basic testing. In my case for sure with a Microtik Router Board. Looking the the below thead other models and type perhaps also?
https://www.arednmesh.org/content/new-node-no-name-resolution
My last post on the above thread:
"I did more testing just upgrading my MicroTik Router Board to 3.22.6 and then to 3.22.8 from 3.22.1 and DNS worked fine while resolving the DtD connected Nanostation and RF connected Rocket (Nanostation to Rocket) I left the Nanostation and Rocket at 3.22.1 and only was upgrading the Router Board.
Once again when I upgrade the Router Board to 3.22.12 the DNS issue started again, I could resolve the rocket or the Nanostation but never both. Seems like rebooting would flip things some times. Upgrading the the latest Nightly Build I see the same effect (DNS doesn't work right as with 3.22.12). Downgrading back to 3.22.8 all is fine again and no issues. So for sure some sort of bug with 3.22.12 and above."
Not sure about your specific network but it's possible that this code PR will fix your issue. It's available for testing in Nightly Build 2331 and newer.
Will let you know. Thank you NG1P Bill
Is this on a very small stand alone network - only a few nodes that never change connectivity?
If yes, see AB7PA's note above about nightly 2331.
So far it seems to be working better with the exception of not being able to route/ping to the MESH RF IP address on the Routerboard. localnode.local.mesh gets me in but if I use the hostname as assigned it resolves correctly but no path to that IP from the local Routerboard.
Thank you Bill NG1P
I'm new to the AREDN system. My current setup here on the table are two Microtik hASP, two TP-Link CPE510 Ver 3. , a Linux computer and a Raspberry 3.
I flashed the Mikrotik and TP Link devices with Ver 3.22.12 and found that the DNS is not working. In the "Mesh Status" and the "Neighbor Status" I saw the IP addresse instead of the Node names. I got a tip and downsized the Mikrotik to Version 3.22.8 and it was working.
I spent the last three day's to setup MeshChat on the Raspberry and one of the TP-Link nodes. It was not working. Today I saw that the Neighbor Status of the CPE510 showed the IP address of the Mikrotik instead of the name. I downsized the firmware of the TP-Link to 3.22.8 and now also MeshChat is working and synchronize with the CPE510.
There is definitely an issue with the DNS resolution in Ver. 3.22.12., with Ver. 3.22.8 it is working.
73 de DL7ATR
Hans-Juergen
73
Orv W6BI
EDIT: comment deleted and moved to new thread here:
https://www.arednmesh.org/content/regular-stable-release-cycle-please
- Don / AA7AU
I can confirm the observation by DL7ATR using two Nanostations MS5-XW.
My station for firmware testing is #1.
(A): #1 shows the name of #2 on the mesh display page.
However, clicking the name of #2 leads to browser timeout, same when pinging using the ...local.mesh address leads to no response.
At the same time, the neighbour status page shows the IP network address of station #2, clicking the link here leads to #1 homepage.
Maybe firmware version 3.22.12.0 could receive a side-note about this?
Does this version work differently (i.e. well) on other hardware?
73
Orv W6BI
I think everything worked at first. WAN share even went all the way through but lately i see the neighbors in mesh status but the hostname will not resolve
If i reloaded the mesh status before the hostname propagates i can connect with IP directly
Randomly on network reboots a hostname will resolve.
I see that this may be resolved in the nightlys and if i get around to installing the latest before the next release i will report back.
Is there a way to see the IP on mesh status and not the hostname?
Thanks for all the hard work guys!