OpenThread
The SED is no longer in the child table of a Parent, the Parent still respond Data Request(802.15.4) with ACK(802.15.4). Is this behavior as expected? #8407
-
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
|
Yes, this is expected. IEEE 802.15.4 ACKs are generated at the MAC layer without any input from higher layers. If a child wants to validate that it is still in its parent's child table, it needs to have a protocol exchange at a higher layer - for example, something that involves exchanging IPv6 datagrams. |
Beta Was this translation helpful? Give feedback.
-
|
As Jonathan said, yes, expected behavior. You can check "Child Supervision" feature in OT as a mechansim related to this. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your prompt response. I get it. Rx-off-when-idle Children SHOULD also periodically resynchronize by sending a Child Update Request to their Parent, then it can know if the Parent had timed out and attempt to reattach. By the way, ask a question about the Wireshark tool. Whether the Wireshark can parse the TLVs of Thread Management Framework(61631 port)? How to configure it? |
Beta Was this translation helpful? Give feedback.
-
Right-click on a packet, select "Decode As..." and select "CoAP-TMF". |
Beta Was this translation helpful? Give feedback.
Yes, this is expected. IEEE 802.15.4 ACKs are generated at the MAC layer without any input from higher layers.
If a child wants to validate that it is still in its parent's child table, it needs to have a protocol exchange at a higher layer - for example, something that involves exchanging IPv6 datagrams.