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
In a functionality of commissioner , the MGMT_PANID_QUERY.qry and MGMT_PANID_CONFLICT.ans messages exchange determines whether a PAN ID is in use. The expected transaction process is outlined in diagram 1. However, the actual transaction process, shown in diagram 2, reveals that the border router retransmits the same MGMT_PANID_CONFLICT.ans message three times due to the lack of a successful acknowledgment (ACK) message from the commissioner.
reproduce method:
start a border router
start a ot-commissioner
> config set pskc 445f2b5ca6f2a93a55ce570a70efeecb
config set pskc 445f2b5ca6f2a93a55ce570a70efeecb
[done]
> start 192.168.9.2 49154
start 192.168.9.2 49154
[done]
> panid query 0xFFFF 0x1234 fda7:4266:2337:da23:0:ff:fe00:fc00
panid query 0xFFFF 0x1234 fda7:4266:2337:da23:0:ff:fe00:fc00
[done]
The RC is the source port of CoAP ACK is different with the dest port of CoAP Answer. Referring to the spec 10.9:
the *4 port could be a ephemeral value from the Thread device side, but it is required that the outgoing response from the commissioner side needs to use it as the dest port and MM: (61631) is used as the source port.
In a functionality of commissioner , the
MGMT_PANID_QUERY.qry
andMGMT_PANID_CONFLICT.ans
messages exchange determines whether a PAN ID is in use. The expected transaction process is outlined in diagram 1. However, the actual transaction process, shown in diagram 2, reveals that the border router retransmits the sameMGMT_PANID_CONFLICT.ans
message three times due to the lack of a successful acknowledgment (ACK) message from the commissioner.reproduce method:
The text was updated successfully, but these errors were encountered: