Repository navigation
Conversation
Answer AAAA (and ANY) questions with one record per valid IPv6 address of the interface, add them next to the A record in answers, additional records and announcements, and re-announce when the IPv6 address count changes (SLAAC usually completes after DHCPv4). Join ff02::fb, listen dual stack and send every multicast message to both 224.0.0.251 and ff02::fb, each only when the interface has an address of that family. Without an IPv4 address no A or IPv4 PTR record is written. The new MDNS_IP6_RESPONDER (on with LWIP_IPV6) covers the responder only; the unfinished MDNS_IP6_SUPPORT query side stays off. See esp8266#9068
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With LWIP_IPV6 the responder only ever answered over IPv4 and never announced
AAAA records, so
<host>.localcould not be resolved to an IPv6 address.the interface; add them next to the A record in answers, additional records
and announcements.
after DHCPv4).
224.0.0.251 and ff02::fb, each only when the interface has an address of
that family. Without an IPv4 address no A or IPv4 PTR record is written.
The new
MDNS_IP6_RESPONDER(on withLWIP_IPV6) covers the responder only;the unfinished
MDNS_IP6_SUPPORTquery side stays off.Tested with ESPHome on 8 ESP8266 devices (core 3.1.2 + this patch) on a
dual-stack network for several days, and on one device with this branch
(master):
avahi-resolve -6 -n <host>.localreturns the IPv6 addresses,services are announced over IPv6, IPv4 resolution is unchanged.
Partially addresses #9068: the responder (AAAA answers and announcements over
IPv6) works, which covers resolving
<host>.localto the device's IPv6addresses; IPv6 service queries from the ESP side remain disabled.
Thanks @HeMan for the earlier investigation in #9068.