-
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
minmdns fails to discover devices during discovery #9099
Comments
mspang
added a commit
to mspang/connectedhomeip
that referenced
this issue
Aug 18, 2021
- Don't skip the rest of the packet if it contains an irrelevant resource record. DNS packets can contain records other than those directly requested. - Don't terminate chip-tool commissioning if a device other than the commissionee is discovered. There is nothing preventing receiving OnAddressUpdateComplete for stale records and this will generally happening when doing tests in quick succession because stale records accumulate in the SRP server. fixes project-chip#9099
mspang
added a commit
to mspang/connectedhomeip
that referenced
this issue
Aug 18, 2021
- Don't skip the rest of the packet if it contains an irrelevant resource record. DNS packets can contain records other than those directly requested. - Don't terminate chip-tool commissioning if a device other than the commissionee is discovered. There is nothing preventing receiving OnAddressUpdateComplete for stale records and this will generally happen when doing tests in quick succession because stale records accumulate in the SRP server. fixes project-chip#9099
mspang
added a commit
that referenced
this issue
Aug 20, 2021
- Don't skip the rest of the packet if it contains an irrelevant resource record. DNS packets can contain records other than those directly requested. - Don't terminate chip-tool commissioning if a device other than the commissionee is discovered. There is nothing preventing receiving OnAddressUpdateComplete for stale records and this will generally happen when doing tests in quick succession because stale records accumulate in the SRP server. fixes #9099
sharadb-amazon
pushed a commit
to sharadb-amazon/connectedhomeip
that referenced
this issue
Aug 23, 2021
- Don't skip the rest of the packet if it contains an irrelevant resource record. DNS packets can contain records other than those directly requested. - Don't terminate chip-tool commissioning if a device other than the commissionee is discovered. There is nothing preventing receiving OnAddressUpdateComplete for stale records and this will generally happen when doing tests in quick succession because stale records accumulate in the SRP server. fixes project-chip#9099
Is this issue resolved? |
nikita-s-wrk
pushed a commit
to nikita-s-wrk/connectedhomeip
that referenced
this issue
Sep 23, 2021
- Don't skip the rest of the packet if it contains an irrelevant resource record. DNS packets can contain records other than those directly requested. - Don't terminate chip-tool commissioning if a device other than the commissionee is discovered. There is nothing preventing receiving OnAddressUpdateComplete for stale records and this will generally happen when doing tests in quick succession because stale records accumulate in the SRP server. fixes project-chip#9099
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Commissioning thread devices that advertise via SRP+mdnsresponder is generally failing to resolve the device near the end of the commissioning flow if the querier is using the minimal mDNS implementation.
The discovery failure occurs despite other mDNS implementations successfully processing the query response:
The text was updated successfully, but these errors were encountered: