Tennessee Carmel-Veilleux
Tennessee Carmel-Veilleux
This is likely an mDNS issue on IPv6 or an issue with the DUT not properly using MLD protocol to join multicast groups in its IPv6 middleware, and the access...
In the above comment: Left side is 1.0 branch (https://github.com/project-chip/connectedhomeip/blob/v1.0-branch/src/credentials/examples/DeviceAttestationCredsExample.cpp), right side is master (https://github.com/project-chip/connectedhomeip/blob/master/src/credentials/examples/DeviceAttestationCredsExample.cpp#L82)
I have also seen large numbers of IPv6 NA (Neighbour Announcement) around failure, not just mDNS. Packet capture **at the Wi-Fi level on the link used by ESP-32** is rquired...
We can emulate it by iterating over all fabrics and then doing the ReadXXX, if we know it's a non-fabric-filtered read
The payload pointer may be outside the pbuf depending how it's allocated. You'd have to trace the path for incoming packets
Tentatively setting V1.0 tag since this is part of many 1.0 test cases that cannot be tested due to lack of method to control commissioning flows through YAML
Removing deferral: many test cases still not doable.
Overall: this is the largest cause of needless reports, and fixing this will have a big impact on reducing congestion for large fan-outs of lighting commands.
This is critical for proper error handling by commissioners