Simon Lin

> Are you hitting it with a UART/USB case? Recently we have this issue using SPI. > I know you said this is most likely a host side issue I...

@romacdon Some questions: - Do you have a reliable way to reproduce this issue? - Currently otbr-agent is using `SPINEL_RESET_STACK`. Could you try using `SPINEL_RESET_PLATFORM` and see if the issue...

@edmont do you experience the same issue on Nordic boards?

@superwhd Thanks for revealing and reproducing this issue. I guess maybe the ping request is handled by both OpenThread and Linux Kernel, causing duplicate ping responses.

> While the logging doesn't have to be the same buffer, it is possible. When it happens the code gets in a loop. That's a good point. I guess one...

I think we have already implemented this feature in `MlrManager::Reregister`, which can be triggered when BBR sequence number changes.

> > I think we have already implemented this feature in `MlrManager::Reregister`, which can be triggered when BBR sequence number changes. > > Hi @simonlingoogle , In the original logic,...

> For the scenario related in this PR, when BBR restarted, some definitions with BBR sequence number updating is related in `5.21.4.2`, the spec just defined `Any change of the...

> Okay, I know what you mean, should we decrease the default reregisteration Delay(which default value is 1200, it seems to large)? Agree that 1200s is too large for typical...

> The default 1200s seems not defined by spec. Per spec 5.21.3.3, the Reregistration Delay value is vendor-specific, the range is (1 - 0.5 * MLR_Timeout) in seconds. Thanks for...