-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Linux impl of mDNS is not setting interfaceId on browse/resolve callback #8232
Comments
Does this end up breaking use of devices that have an ipv6 link local address with a Linux controller? |
Yes it does, the interfaceId is required for addressing link-local ipv6 addresses and callbacks don't return it for such addresses. |
The issue is correct and this can break IPv6 in practice. Depending on the network stack, if you use a LL address and there's only one interface (the case for most of the devices implemented here if I'm not mistaken), it will probably work even without the scope set. But yeah, the interface should be set. If you throw that patch up as a PR, I'm sure it'll get approved. |
Without this resolving something to a link-local IP won't work right. Fixes project-chip#8232
Without this resolving something to a link-local IP won't work right. Fixes project-chip#8232
Without this resolving something to a link-local IP won't work right. Fixes project-chip#8232
Without this resolving something to a link-local IP won't work right. Fixes #8232 Co-authored-by: Abdul Samad <[email protected]>
…t-chip#9484) Without this resolving something to a link-local IP won't work right. Fixes project-chip#8232 Co-authored-by: Abdul Samad <[email protected]>
Problem
Linux platform implementation of
chip::Mdns
is not setting interfaceId for browse/resolve callbacks once retrieved from avahi service browse/resolve.Proposed Solution
MdnsAvahi::HandleBrowse
andMdnsAvahi::HandleResolve
need to set interfaceId inMdnsService
structure before returning the services to browse callback.The text was updated successfully, but these errors were encountered: