-
Notifications
You must be signed in to change notification settings - Fork 67
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
TP-Link cpe210 v2 Nightly build DNS refused #540
Comments
Have you verified that you only have one network connection to your computer? That is, if it's a laptop and you're wired to the TP-Link, is the wireless turned off on your laptop? That's a frequent source of DNS issues. Orv W6BI |
I did. I have a wifi router set up as access point for the node that I ran the nightly build on. The router is directly connected to the node and its set default to hand out 5 ip's. I did get ip address and DNS server was the nodes gateway. I did clear a few weeks of cache from my laptop browser. It seemed like it couldn't resolve the neighbor nodes by there FQDN if that's the correct term. I tried ping from cli but failed by name. With the stable firmware I can ping and use nslookup by using ( ko4bjv-node-2.local.mesh ). I guess this is an accurate way to test. It may just be some mistake on my end. Aredn is an amazing network. I'm in the flat land here on the east coast so the trees are an issue but it still works reliably for my needs. Thank you to all the developers and contributors. Kyle |
I put the nightly build on my CPE210-v1 yesterday and found no issues. Dunno what's going on... |
Okay Thanks for checking. I must have been doing something wrong on my end, |
Hello. Sorry if this is already known .
Firmware [aredn-1853-91cf71f-ath79-generic-tplink_cpe210-v2-squashfs-sysupgrade.bin](http: 22-10-27
When clicking on a link to a neighbors node the status page of that node will not load. It can be reached by its ip address. From Wireshark DNS query reports refused A ( name of node ). Rolled back to stable image DNS working okay now.
Kyle
The text was updated successfully, but these errors were encountered: