OpenThread
-
|
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 14 replies
-
|
The address you highlighted |
Beta Was this translation helpful? Give feedback.
-
|
below is the way of generating RLOC16, and I can't find the spec about it. BTW, the TMF coap playload can't be parsed by wirshark, and only display hex digits. It can be displayed with easily understanding way? |
Beta Was this translation helpful? Give feedback.
-
|
@wallaceL , the RLOC address format is described in section "5.2.2.1 Routing Locator (RLOC)" in Thread spec (Figure 5-1 shows the 16 bit format on how to combine "Router ID" and "Child ID"). |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your reply. in MleRouter::BecomeLeader set leaderId to 0, the issue will be reproduced 100%，any sub-device can't join the thread network. |
Beta Was this translation helpful? Give feedback.
-
|
@wallaceL , can you please share more details? I tested the scenario you mention and it works fine for me. Here is the leader node with rloc16 of > state
leader
Done
> rloc16
0000
DoneAnd here is another node (a FTD router) successfully attached to the same network: > state
router
Done
> router table
| ID | RLOC16 | Next Hop | Path Cost | LQ In | LQ Out | Age | Extended MAC | Link |
+----+--------+----------+-----------+-------+--------+-----+------------------+------+
| 0 | 0x0000 | 63 | 0 | 3 | 3 | 5 | be51f449f762e8b9 | 1 |
| 5 | 0x1400 | 63 | 0 | 0 | 0 | 0 | 96a411197b151011 | 0 |
Done
> leaderdata
Partition ID: 2042431421
Weighting: 64
Data Version: 188
Stable Data Version: 252
Leader Router ID: 0
DoneHere is the logs on new node when it sends CoAP/TMF "Address Solicit" message to "leader" (when it is trying to become router). We see it is using |
Beta Was this translation helpful? Give feedback.
-
|
I add one sub-device, and below is the log. OTBR I captured this scenario by wireshark The network key is |
Beta Was this translation helpful? Give feedback.
-
|
We also found the similar issue with MATTER running on top of it: |
Beta Was this translation helpful? Give feedback.
-
|
We're running the OTBR on OpenWRT + SSD20x platform. |
Beta Was this translation helpful? Give feedback.
-
|
@anzengSi Sub-device sends coap/TMF to query address, but the otbr doesn't response. From the log, I can't find any frames with coap, but get some errror info as below, maybe these frames are dropped. |
Beta Was this translation helpful? Give feedback.
-
|
@wallaceL you're not running the OTBR on the Pi + Ubuntu, right? |
Beta Was this translation helpful? Give feedback.
-
|
@anzengSi Yes |
Beta Was this translation helpful? Give feedback.
The address you highlighted
fd7d:6c51:bf4:82ad:0:ff:fe00:0/64is a valid address. It is a Routing Locator, where the last 16 bits encode the Router ID and Child ID. This would indicate that the device has Router and Child ID values both zero, which is valid. A Router ID can be zero and all Routers have a Child ID of zero.