-
Notifications
You must be signed in to change notification settings - Fork 13.3k
IPv6 DNS servers are not received correctly #5561
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
Comments
I have investigated this problem and created a LwIP patch which fixes it: https://savannah.nongnu.org/patch/index.php?9737 The problem was due to the IP address structure containing the DNS server address not being marked as an IPv6 address which is why the sample output DNS address of 32.1.4.112 equates to the first 32-bits of my DNS server address: 2001:0470. Rebuilding lwip2 by running:
Results in the following output:
I presume to fix this my change will need reviewed and merged upstream before rebuilding and updating in this project which is why I raised this as an Issue rather than a PR. |
Ah thanks alot !
If you want to see your patches applied sooner, please do PRs also in lwip2 |
OK. Think I understand the workflow better now. Will look at doing this tomorrow. |
Fixed in d-a-v/esp82xx-nonos-linklayer#23 |
Basic Infos
Platform
Settings in IDE
Problem Description
I am testing the IPv6.ino sample on my home network which has both IPv4 DHCP and IPv6 DHCPv6 support. Both DHCP protocols deliver DNS server addresses to clients. The IPv6.ino sample fails to resolve the two domains as the DNS server address used is gibberish. Occasionally DHCPv4 wins the race condition within the stack and the IP address is the network IPv4 DNS server. As my DNS server is dual-stacked it is able to resolve all domains.
MCVE Sketch
ESP8266WiFi | IPv6 example
I have deleted the line below for clarity in the output:
Debug Messages
Broken DNS IPv6 address (it should be 2001:470:XXXX:2b6::3)
Working IPv4 DNS server address:
The text was updated successfully, but these errors were encountered: