Problems in Thread commssioning

565 views
Skip to first unread message

Rohith R

unread,
Jun 3, 2021, 8:46:36 AM6/3/21
to openthread-users
i have created s thread network using EFR32MG12 as RCP and Beagle Bone as Border Router(Platform is Silicon Lab WSDK). While performing commissioning i have some issues

1.While using the external commissioning via Thread Commissioning App, we have to type the admin password. what is this admin password? i know it is the commissioner credentials, ie., passphrase. how did we obtain this passphrase? is it the name of our external commissioning device.. please help me to find the admin password
2. While commissioning using CLI commands, after join success, i typed state (befor i have used the thread start cli commands)CLI command to  know the state, but it shows detached. What will be the reason? how do i join the n/w?

anyone please help me to find the answer for these questions and clarify my doubts in Thread commissioning

Gabe Kassel

unread,
Jun 3, 2021, 10:42:44 AM6/3/21
to Rohith R, openthread-users
1. This is the human-readable commissioning credential. The CC is turned into the PSKc through a hashing function with the network name and extended PAN ID. You can go from a CC to PSKc using the PSKc -p cli command or using the PSKc generator script linked below. 

2. Believe this is expected. The device won’t be attached to the network until you type thread start and it goes through the MLE process of actually attaching. What happens if you type thread start at that point then state again a few seconds later? It should become a child. 



--
You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/7a1d2989-9cf2-418c-8b9a-b916997f7debn%40googlegroups.com.
--
_______

Gabe Kassel
Technology Strategist | Office of the CTO

m 770.490.0431
e  ga...@eero.com

Rohith R

unread,
Jun 3, 2021, 11:46:01 AM6/3/21
to openthread-users
1. i have go through the link.
> pskc 67c0c203aa0b042bfb5381c47aef4d9e 
Done 
> pskc -p 123456 
Done
now my doubt is that form now onwards the admin password is 123456?
or we have to use this 123456 to connect our mobile phone(external commissioner) to Thread Border Router
2. After joining success i have typed thread start then checked the state, it again shows detached. what will be the reason? how it become a child/router?

Gabe Kassel

unread,
Jun 3, 2021, 12:03:32 PM6/3/21
to Rohith R, openthread-users
  1. 123456 is indeed the commissioning credential. I'm assuming you're running pskc -p on the border router. You'll also want to make sure the resulting pskc is actually showing up in the active dataset.
  2. Are you going through the joining process on the joiner and seeing "Success" before calling thread start?


_______

Gabe Kassel
Technology Strategist | Office of the CTO

m 770.490.0431
e  ga...@eero.com

Sent via Superhuman


To unsubscribe from this group and stop receiving emails from it, send an email to openthread-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/1e4c0b54-d77d-425c-8d9e-75ac724cfa17n%40googlegroups.com.

Rohith R

unread,
Jun 4, 2021, 1:53:02 AM6/4/21
to openthread-users
1.When using the Thread Commissioning App for the commissioning it takes more (5-10 minutes) to add the device. What will be the reason for this delay?
2.while commissioning with the Thread Commissioning App  the product is added. But in the joiner console after join success it shows  the state as detached. Please find the attached screenshot. Anyone please tell me the  reason for this problem and how can i solve this?

Child.png

Jonathan Hui

unread,
Jun 4, 2021, 3:59:44 PM6/4/21
to Rohith R, openthread-users
On Thu, Jun 3, 2021 at 10:53 PM Rohith R <rohith...@gmail.com> wrote:
1.When using the Thread Commissioning App for the commissioning it takes more (5-10 minutes) to add the device. What will be the reason for this delay?

Which Thread Commissioning App are you using? Note that the OpenThread project includes a commissioner app project as well: https://github.com/openthread/ot-commissioner
 
2.while commissioning with the Thread Commissioning App  the product is added. But in the joiner console after join success it shows  the state as detached. Please find the attached screenshot. Anyone please tell me the  reason for this problem and how can i solve this?

After "Join success", can you check to see if the Active Operational Dataset on the joiner matches that on OTBR? You can use the dataset active command to output the Active Operational Dataset.

--
Jonathan Hui

Rohith R

unread,
Jun 4, 2021, 10:20:12 PM6/4/21
to openthread-users
1.I am using the Thread Group Sample Commissioning Application for Android OS (Thread Commissioning App) Version 1.01.11
My android version s 11
2.Sir do you mean, i have to type dataset commit active after join success? or simply the dataset cli command?  then try thread start and check the state?

Jonathan Hui

unread,
Jun 4, 2021, 10:40:56 PM6/4/21
to Rohith R, openthread-users
On Fri, Jun 4, 2021 at 7:20 PM Rohith R <rohith...@gmail.com> wrote:
1.I am using the Thread Group Sample Commissioning Application for Android OS (Thread Commissioning App) Version 1.01.11
My android version s 11

Can you try using the ot-commissioner app?
 
2.Sir do you mean, i have to type dataset commit active after join success? or simply the dataset cli command?  then try thread start and check the state?

I'm simply asking you to verify if the Active Operational Dataset is the same between the two nodes using the dataset active CLI command.

BTW, you have asked the same question in many different locations (various GitHub issues in different repos in addition to here). Please keep the discussion in one place.

--
Jonathan Hui

Rohith R

unread,
Jun 5, 2021, 4:09:40 AM6/5/21
to openthread-users
Sir, I have verified the Active Operational dataset ,it is the same b/w the toe nodes. Still the state is showing as detached. Please find the  attached screenshots for your reference
childtable.png
childdataset.png
Leaderdatset.png

Jonathan Hui

unread,
Jun 5, 2021, 11:38:27 AM6/5/21
to Rohith R, openthread-users
Thanks for confirming that the Active Operational Dataset matches.

It's not yet obvious why your device is not attaching. Can you also provide the OpenThread logs and a packet sniffer capture for greater visibility?

--
Jonathan Hui



--
You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/9a5aeed1-d8be-428f-b751-3a1ab595405dn%40googlegroups.com.

Rohith R

unread,
Jun 6, 2021, 8:43:02 AM6/6/21
to Jonathan Hui, openthread-users
Sir when i check the extended pan id from the joiner console it is different from the ext pan id in the active dataset

Jonathan Hui

unread,
Jun 7, 2021, 1:17:49 AM6/7/21
to Rohith R, openthread-users
The Extended PAN ID is not used when attaching to the network. The only attribute absolutely required in the master key. The channel and PAN ID parameters can be helpful if they are known. As a result, the joiner code only sets master key, channel, and PAN ID as part of commissioning.

--
Jonathan Hui


Rohith R

unread,
Jun 7, 2021, 1:39:24 AM6/7/21
to openthread-users
Sir this is the Network analyzer data. Please find the  attached documents
packtSniffer.png

Jonathan Hui

unread,
Jun 7, 2021, 1:46:47 AM6/7/21
to Rohith R, Sébastien Parent-Charette, openthread-users
In the future, can you provide the .isd file so that we can view the full trace?

One thing strange I see in the screenshot is that the MLE Parent Request message is not being displayed, which is what causes neighboring routers to send a MLE Parent Response message.

@Sébastien Parent-Charette , do you have any ideas on what may be going on?

--
Jonathan Hui



Rohith R

unread,
Jun 7, 2021, 2:38:15 AM6/7/21
to openthread-users
Dear Sir,
Please find the attached .isd file and the image of initial response

initialResponse.png
ThreadNetworkRouting.isd

Jonathan Hui

unread,
Jun 7, 2021, 4:30:11 PM6/7/21
to Rohith R, openthread-users
Can you provide the network key so that we can decrypt the packets in the trace?

Also, can you provide the git commit ID you used for the OpenThread Border Router and ot-cli-ftd devices?

--
Jonathan Hui



To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/6598d942-09a4-45de-acc9-252c58b8621cn%40googlegroups.com.

Jonathan Hui

unread,
Jun 8, 2021, 12:33:50 AM6/8/21
to Rohith R, openthread-users
I just submitted a fix for a very similar issue to yours - see openthread/ot-br-posix#881 and the associated email thread.

Can you pull the latest code and see if that resolves your issue as well?

--
Jonathan Hui


Rohith R

unread,
Jun 9, 2021, 12:49:32 AM6/9/21
to openthread-users
Thank You sir. Now the  problem is solved. I can attach the device as child/router to the thread network. But now the problem is that External Thread Commissioning is not supported because while scanning Thread Commissioning App do not show any Border Routers, as the border routers are active

Jonathan Hui

unread,
Jun 9, 2021, 12:52:23 AM6/9/21
to Rohith R, openthread-users
The Thread Commissioning App on Play store has a known bug with mDNS. You can try to work around by opening another Android app that uses mDNS in the background.

Alternatively, you can try to use the ot-commissioner Android app.

--
Jonathan Hui



To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/b13ce8cc-be6d-46a5-a6b6-af979b72b97en%40googlegroups.com.

Rohith R

unread,
Jun 9, 2021, 1:55:27 AM6/9/21
to openthread-users
1. when i built the code using  ./script/build $platform -DBOARD=$board  i got the device listed in the thread commisioning app , But later I enabled the Flags for Additional features as mentioned in the manual by running  ./script/build efr32mg12 -DBOARD=brd4161a -DOT_COMMISSIONER=ON -DOT_JOINER=ON -DOT_DHCP6_CLIENT=ON -DOT_DHCP6_SERVER=ON
then its not listing in the thread commisioner app. Is it because of any flags to be set for this external commisioning function.

2.  I also downloaded the app you mentioned above but no luck.

Jonathan Hui

unread,
Jun 9, 2021, 2:37:22 AM6/9/21
to Rohith R, openthread-users
On Tue, Jun 8, 2021 at 10:55 PM Rohith R <rohith...@gmail.com> wrote:
1. when i built the code using  ./script/build $platform -DBOARD=$board  i got the device listed in the thread commisioning app , But later I enabled the Flags for Additional features as mentioned in the manual by running  ./script/build efr32mg12 -DBOARD=brd4161a -DOT_COMMISSIONER=ON -DOT_JOINER=ON -DOT_DHCP6_CLIENT=ON -DOT_DHCP6_SERVER=ON
then its not listing in the thread commisioner app. Is it because of any flags to be set for this external commisioning function.

This is for building the RCP? This should have no effect on mDNS.

Is it possible for you to try setting up a border router using Raspberry Pi?

--
Jonathan Hui

Rohith R

unread,
Jun 9, 2021, 1:13:13 PM6/9/21
to openthread-users
Thank you so much sir. I have solved all the problems. External commissioning has successfully obtained.

one of my  doubts  is that 
1.My device's eui64 is  000b57fffe315b69. It means that MAC address is 010b57315b69, which is constant. And the extended address (Extended MAC) is c6a5183790f760ce.
How the  extended MAC address is obtained in this manner?

Jonathan Hui

unread,
Jun 9, 2021, 1:53:04 PM6/9/21
to Rohith R, openthread-users
Great to hear that you resolved your issue. Can you explain what the issue was and how you fixed it?

Regarding the question about EUI-64 and Extended Address:
  • The EUI-64 is factory assigned.
  • The Extended Address before a Thread device is commissioned is the SHA-256 of the EUI-64.
  • The Extended Address after a Thread device is commissioned is chosen at random.
For clarity, Thread does not really use the term "MAC address" since IEEE 802.15.4 has both Extended and Short addresses.

--
Jonathan Hui



--
You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.

Rohith R

unread,
Jun 10, 2021, 10:01:28 AM6/10/21
to openthread-users
Sir i have not done anything in special. i have taken the code (ot-rcp, ot-cli-ftd, ot-cli-mtd) from Github as per your advice and burn  it on the devices and set the flags  ./script/build efr32mg12 -DBOARD=brd4161a -DOT_COMMISSIONER=ON -DOT_JOINER=ON -DOT_DHCP6_CLIENT=ON -DOT_DHCP6_SERVER=ON.  Some times the Thread Network is not showing the Commissioner App and sometimes it show.  The  ot-commissioner Android app  in the Github is not showing the active Thread network Still i have facing  some issues also

1. After attaching two devices to Thread Network as Router and Child. After power off the devices and again switched on the devices states are disable, even though they have the dataset. Its not  good for real time application (or product). Please tell me sir what correction I have to make for the device's states to remain router and child  after switched off and switched on .

2. from Open  Thread Documents and other articles I have find that in a thread  n/w  32Routers,1Leadr and each router can have 511Child. So in thread n/w we can have max of 16385 devices. Can we have 16385devices in a single thread n/w practically?
3. ipaddr  of a router/Child is as follows

 fdbe:719a:23c4:b077:c396:5bd5:2fa7:c2
 fdd0:2abf:334d:9cd7:0:ff:fe00:2001
fdd0:2abf:334d:9cd7:503f:b5ba:fb97:28aa
fe80:0:0:0:88e2:6ff6:7462:5a53

I know the 2nd one is RLOC, 3rd is  ML-EID and last one is Link Local Address.  Sir what is the first ip address and what is its significance

Hoping the answer for all my doubts

Rohith R

Jonathan Hui

unread,
Jun 10, 2021, 10:47:02 AM6/10/21
to Rohith R, openthread-users
On Thu, Jun 10, 2021 at 7:01 AM Rohith R <rohith...@gmail.com> wrote:

1. After attaching two devices to Thread Network as Router and Child. After power off the devices and again switched on the devices states are disable, even though they have the dataset. Its not  good for real time application (or product). Please tell me sir what correction I have to make for the device's states to remain router and child  after switched off and switched on .

Yes, the example apps do not automatically reattach to the network. You can update the code to automatically enable the network interface and start Thread after boot.

2. from Open  Thread Documents and other articles I have find that in a thread  n/w  32Routers,1Leadr and each router can have 511Child. So in thread n/w we can have max of 16385 devices. Can we have 16385devices in a single thread n/w practically?

The leader is a router, so the maximum is really 31 routers in addition to the leader.

Thread protocol does support up to 511 children per router, but that is subject to resource constraints on the router (memory available for child table and message buffering) as well as channel utilization (all devices must share the same RF channel). It largely depends on how much communication each child performs.
 
3. ipaddr  of a router/Child is as follows

 fdbe:719a:23c4:b077:c396:5bd5:2fa7:c2
 fdd0:2abf:334d:9cd7:0:ff:fe00:2001
fdd0:2abf:334d:9cd7:503f:b5ba:fb97:28aa
fe80:0:0:0:88e2:6ff6:7462:5a53

I know the 2nd one is RLOC, 3rd is  ML-EID and last one is Link Local Address.  Sir what is the first ip address and what is its significance

The first address is a routable IPv6 address that may be used for communicating with devices external to the Thread network.

--
Jonathan Hui

Rohith R

unread,
Jun 10, 2021, 11:24:14 AM6/10/21
to openthread-users
3.The first address is a routable IPv6 address that may be used for communicating with devices external to the Thread network.

But sir i found that you have used this address for communication within the thread network for UDP in one of the discussions

Jonathan Hui

unread,
Jun 10, 2021, 2:21:17 PM6/10/21
to Rohith R, openthread-users
IPv6 addresses with larger scopes may also be used to communicate in smaller scopes. For example, you can use a global-scoped IPv6 address to communicate with other devices on the same mesh. However, you cannot use mesh-local-scoped IPv6 addresses to communicate with devices outside the Thread mesh.

--
Jonathan Hui



--
You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/0fd2ad0d-1e9b-4764-b3c2-a32377dd9256n%40googlegroups.com.
Reply all
Reply to author
Forward
Message has been deleted
0 new messages