Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERR_NAME_NOT_RESOLVED when using GL-inet AR-300Ms #748

Closed
convolved-KY4G opened this issue Mar 13, 2023 · 2 comments
Closed

ERR_NAME_NOT_RESOLVED when using GL-inet AR-300Ms #748

convolved-KY4G opened this issue Mar 13, 2023 · 2 comments

Comments

@convolved-KY4G
Copy link

I have two GL-inet AR-300Ms in an AREDN testbed. The two are connected via the mesh network and can be seen by each other by clicking the mesh status button. The connection sometimes shows a link of the name of the other node (e.g KY4G-GLAR300 which resolves to http://ky4g-glar300.local.mesh:8080/) and sometimes shows a link to its IP address (e.g. 10.23.85.83 which resolves to http://10.23.85.83:8080/cgi-bin/mesh). If the IP address is shown, it can be clicked on and successfully goes to the status page of the other node. If the name of the other node is shown, when you click on the name it says ERR_NAME_NOT_RESOLVED. This happens consistently between the two nodes. If you manually enter the IP address directly into a browser, it navigates to the status page just fine. This seems like a bug. I am running firmware 3.22.12.0 on both nodes. There are three images below to further show what I am seeing.

Capture1
Capture2
Capture3

@aanon4
Copy link
Contributor

aanon4 commented Mar 13, 2023

Are you running a release or a nightly. This should be fixed in the nightly build.

@convolved-KY4G
Copy link
Author

I was running the latest release. I thought the nightly build only fixed an issue specific to the AR150s. I upgraded the nodes and it did indeed fix it for the AR300s too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants