Boris Zbarsky

We've been running into this in our testing as well, with esp32 devices. @shubhamdp @dhrishi

@shubhamdp See this part from the issue description: > It happens with a very low chance (

@ryan-ma Interesting. So this is a transient failure and the right thing to do is to try again (via MRP)? We have something like that already in`ExchangeMessageDispatch::SendMessage` for the ENOBUFS...

Could someone who is running into this try https://github.com/bzbarsky-apple/connectedhomeip/commit/8f5234159061319b5b0b7431a97ac0a4d641d931 and let me know whether that seems to help?

@ryan-ma Thank you for confirming that! It's good to know this actually fixes the problem in practice.

That chip-tool log seems to show a bunch of executions of that command, some interrupted via Ctrl-C, etc... But it does not show what commands were executed _before_ this command,...

> The approach here requires more discussion before such a wide-ranging PR. That is perfectly reasonable. What I am trying to accomplish is to make it very clear to an...

Looks like the server never responded to the Sigma1 message.... @phonnakasturi-apple Did we resolve the right IP for this server, do you know?

@phonnakasturi-apple Well, the resolved IP was fdb0:a47c:fc46:0:9d1:9a28:c383:3c7 and it was on interface en7. So checking whether `ping6 fdb0:a47c:fc46:0:9d1:9a28:c383:3c7` and `ping6 fdb0:a47c:fc46:0:9d1:9a28:c383:3c7%en7` work would be a good start. Assuming the thread...

@phonnakasturi-apple does `ping6 fdb0:a47c:fc46:0:6b96:a2f0:d434:1667%en7` or whatever the right interface is work? It sounds like there are some sort of networking issues here that should get sorted out in the specific...