Repository navigation
[pull] master from home-assistant:master - #415
Merged
Merged
Conversation
…ces (#4794) * openthread_border_router: Fix upstream DNS resolution for Thread devices Since add-on 2.12.0 (OTBR bump to b041fa52, which pulled in OpenThread d88b63d19 / openthread/openthread#10864) the upstream DNS resolver binds its UDP sockets to the infrastructure interface via SO_BINDTODEVICE. The add-on runs with host networking, and the nameserver in /etc/resolv.conf is the Supervisor DNS (172.30.32.3), which is only reachable through the hassio bridge. With the socket bound, the kernel routes the query out the physical interface via the default route instead, where it goes unanswered: upstream DNS queries from Thread devices, and with them NAT64/DNS64 name resolution (device cloud connectivity, MQTT broker hostnames, ...), time out. Disable the binding via OPENTHREAD_POSIX_CONFIG_UPSTREAM_DNS_BIND_TO_INFRA_NETIF in the project config header so upstream queries follow the host routing table again, as they did before 2.12.0. A behavioral fix has been proposed upstream (openthread/openthread#13545); this define can be dropped once it is merged and picked up. Notes from debugging, for future reference: - Networks whose router advertises RDNSS in router advertisements are NOT affected on recent add-on versions: since OpenThread #11342 (March 2025) the resolver also queries RDNSS-discovered servers, which are on-link on the infrastructure interface and work despite the binding. This masked the regression and made it appear environment-dependent. IPv4-only networks (no RDNSS) are always affected. - `ot-ctl dns resolve4` on the border router itself is not a valid test for this path: in our testing such queries never reached the BR's own DNS-SD server, independent of this bug. Test from an actual Thread device (or a TREL-connected OpenThread CLI node). Fixes #3947 * Update openthread_border_router/CHANGELOG.md Co-authored-by: Jan Čermák <sairon@users.noreply.github.com> --------- Co-authored-by: Jan Čermák <sairon@users.noreply.github.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )