<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Thread cli</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/62785/thread-cli</link><description>Does commands 
 &amp;gt;Thead down and 
 &amp;gt;Ifconfig down 
 Commands are equivalent to power failure reset of node in mesh network</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 15 Jul 2020 15:07:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/62785/thread-cli" /><item><title>RE: Thread cli</title><link>https://devzone.nordicsemi.com/thread/260195?ContentTypeID=1</link><pubDate>Wed, 15 Jul 2020 15:07:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3a7a94c1-91bf-4734-9fdd-c3503d6b3aed</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;The point of the commissioning procedure is for the device to obtain the masterkey from an existing network device to allow the new node to attach to the network using the obtained masterkey.&lt;/p&gt;
&lt;p&gt;By adding the eui64 of the device to the commissioner, only the device with this identified can be commissioned to the network. It is also possible to start the commissioner with a * to allow any devices to be commissioned. The &amp;quot;J01NME&amp;quot; that is used in the tutorial is the shared secret that is entered on both commissioner and joiner. This prevents other devices from spoofing the eui64 of the device to become commissioned into the network, as it will not know the shared secret.&lt;/p&gt;
&lt;p&gt;The network data is stored in flash after commissioning, you do not need to perform the commissioning after every reset.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thread cli</title><link>https://devzone.nordicsemi.com/thread/257711?ContentTypeID=1</link><pubDate>Wed, 01 Jul 2020 07:01:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9088a8ef-a27d-4789-b012-9ac9514f6689</guid><dc:creator>anguru</dc:creator><description>&lt;p&gt;Any reply&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thread cli</title><link>https://devzone.nordicsemi.com/thread/257215?ContentTypeID=1</link><pubDate>Sat, 27 Jun 2020 03:26:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8d14e51f-0453-401f-85ab-994b99a292a9</guid><dc:creator>anguru</dc:creator><description>&lt;p&gt;the commands needed to commission the network as mentioned in above tutorial is shown below&lt;pre class="ui-code" data-mode="text"&gt;## FTD Joiner ##
----------------

&amp;gt; eui64
2f57d222545271f1
Done



## FTD Commissioner ##
----------------------

&amp;gt; commissioner start
Done
&amp;gt; commissioner joiner add 2f57d222545271f1 J01NME
Done



## FTD Joiner ##
----------------

&amp;gt; scan
| J | Network Name     | Extended PAN     | PAN  | MAC Address      | Ch | dBm | LQI |
+---+------------------+------------------+------+------------------+----+-----+-----+
| 1 | OpenThread-c0de  | c0de7ab5c0de7ab5 | c0de | 1ed687a9cb9d4b1d | 11 | -45 |  48 |


## FTD Joiner ##
----------------

&amp;gt; ifconfig up
Done
&amp;gt; joiner start J01NME
Done

## FTD Joiner ##
----------------

&amp;gt;
Join success


## FTD Joiner ##
----------------

&amp;gt; thread start
Done
&amp;gt; state
child
Done
&amp;gt; rloc16
0c02
Done

## FTD Joiner ##
----------------

&amp;gt; ipaddr
fdc0:de7a:b5c0:0:0:ff:fe00:c02         # Routing Locator (RLOC)
fe80:0:0:0:e4cd:d2d9:3249:a243         # Link-Local Address (LLA)
fdc0:de7a:b5c0:0:3e2e:66e:9d41:ebcd    # Mesh-Local EID (ML-EID)



## FTD Commissioner ##
----------------------

&amp;gt; router table
| ID | RLOC16 | Next Hop | Path Cost | LQ In | LQ Out | Age | Extended MAC     |
+----+--------+----------+-----------+-------+--------+-----+------------------+
|  3 | 0x0c00 |        3 |         0 |     0 |      0 |  50 | 1ed687a9cb9d4b1d |

&amp;gt; child table
| ID  | RLOC16 | Timeout    | Age        | LQ In | C_VN |R|S|D|N| Extended MAC     |
+-----+--------+------------+------------+-------+------+-+-+-+-+------------------+
|   1 | 0x0c01 |        240 |         25 |     3 |   89 |1|1|1|1| 1ae529b3a638943b |
|   2 | 0x0c02 |        240 |         15 |     3 |   44 |1|1|1|1| e6cdd2d93249a243 |
Done
&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thread cli</title><link>https://devzone.nordicsemi.com/thread/257213?ContentTypeID=1</link><pubDate>Sat, 27 Jun 2020 03:16:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:136c8829-eae4-49c5-bf53-4dff3859be68</guid><dc:creator>anguru</dc:creator><description>&lt;p&gt;I followed this tutorial&amp;nbsp;&lt;a href="https://codelabs.developers.google.com/codelabs/openthread-hardware/#8"&gt;https://codelabs.developers.google.com/codelabs/openthread-hardware/#8&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;in which commissioning&amp;nbsp; the FTD joiner using eui64 command doesn&amp;#39;t need to have same master key,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I&amp;nbsp;repeatedly asked the same question and received the same answer,&lt;/p&gt;
&lt;p&gt;It would be better if someone says&amp;nbsp;exactly what happens after reset , if i commission the&amp;nbsp; mesh as mentioned in above tutorial using eui64 command&lt;/p&gt;
&lt;p&gt;The reason is due to covid , I just theoretically studied how to develop mesh using openthead cli&amp;nbsp; to interface 30 nodes, I can&amp;#39;t implement practically to see the results (Can&amp;#39;t access the hardware as far now)&amp;nbsp;and also time to complete the project is very less,&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thread cli</title><link>https://devzone.nordicsemi.com/thread/256233?ContentTypeID=1</link><pubDate>Mon, 22 Jun 2020 14:14:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a7c155bd-8d8e-443a-b6bc-ce976eb0786e</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;The OpenThread stack stores persistent network data automatically in flash. You should not need to recommission the device after a power failure/reboot. However, you need to make sure that the firmware does not use the default masterkey and on boot (most of our examples use autocommissioning and use default masterkey from OpenThread).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thread cli</title><link>https://devzone.nordicsemi.com/thread/256112?ContentTypeID=1</link><pubDate>Mon, 22 Jun 2020 08:00:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ea033fee-d4b1-4539-b340-eb10b9636b1a</guid><dc:creator>anguru</dc:creator><description>&lt;p&gt;I am using eui64 commands to comission the mesh node, if power failure occurs at a node , when the node restarts , is it necessary to commission the node again or will it connect to mesh automatically??&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thread cli</title><link>https://devzone.nordicsemi.com/thread/255909?ContentTypeID=1</link><pubDate>Fri, 19 Jun 2020 09:00:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0752f5b1-7beb-424f-9740-b7c1867298f7</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;These commands will take down the Thread and IPv6 interfaces, so for the network, it may appear similar to a power failure of the device.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>