You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chip-device-ctrl resolve hangs on the Mac with all Thread based devices. To reproduce it:
1 - commission a BLE device to CHIP Thread network
2 - call close-ble
3 - call resolve with appropriate fabricId and nodeId parameters
Result: the call never returns, the tool must be force quit.
The explanation is:
src/platform/Darwin/MdnsImpl.cpp calls DNSServiceGetAddrInfo with 0 flags parameter which means no timeout, and kDNSServiceProtocol_IPv4 protocol parameter which restricts search to IPv4 only. In the case of Thread devices this is impossible to succeed since by definition all Thread devices are on IPv6 network.
Proposed Solution
In src/platform/Darwin/MdnsImpl.cpp call DNSServiceGetAddrInfo with combined kDNSServiceProtocol_IPv4 | kDNSServiceProtocol_IPv6 protocol parameter, then everything works.
The text was updated successfully, but these errors were encountered:
Problem
chip-device-ctrl resolve hangs on the Mac with all Thread based devices. To reproduce it:
1 - commission a BLE device to CHIP Thread network
2 - call close-ble
3 - call resolve with appropriate fabricId and nodeId parameters
Result: the call never returns, the tool must be force quit.
The explanation is:
src/platform/Darwin/MdnsImpl.cpp calls DNSServiceGetAddrInfo with 0 flags parameter which means no timeout, and kDNSServiceProtocol_IPv4 protocol parameter which restricts search to IPv4 only. In the case of Thread devices this is impossible to succeed since by definition all Thread devices are on IPv6 network.
Proposed Solution
In src/platform/Darwin/MdnsImpl.cpp call DNSServiceGetAddrInfo with combined kDNSServiceProtocol_IPv4 | kDNSServiceProtocol_IPv6 protocol parameter, then everything works.
The text was updated successfully, but these errors were encountered: