net: dns: Join mDNS multicast group for resolving #86617
Conversation
This file contains 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
rlubos
previously approved these changes
Mar 4, 2025
If mDNS resolver is enabled but mDNS responder is not, then mDNS multicast address group is not joined. This would prevent the mDNS resolver to receive the responses. Fix this by joining the mDNS multicast group if mDNS responder is not enabled (because the responder will join the group itself). Fixes zephyrproject-rtos#86477 Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
Make sure that if mDNS resolver is enabled, we join the mDNS multicast group so that query responses can be received. Signed-off-by: Jukka Rissanen <jukka.rissanen@nordicsemi.no>
jukkar
force-pushed
the
fix/86477/mdns-join-mcast-group-missing
branch
from
f3f8342 to
3590514
Compare
|
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.
If mDNS resolver is enabled but mDNS responder is not, then mDNS multicast address group is not joined. This would prevent the mDNS resolver to receive the responses. Fix this by joining the mDNS multicast group if mDNS responder is not enabled (because the responder will join the group itself).
Fixes #86477