<?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>Managing a BLE/Thread application with unknown IPv6 addresses</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/44384/managing-a-ble-thread-application-with-unknown-ipv6-addresses</link><description>Hello 
 I have 3 nodes, 2 Thread CoAP servers and 1 BLE/Thread Coap client. 
 Let&amp;#39;s call them THnode1, THnode2 and BLE_THnode0. 
 I do not know the IP addresses of any node, but I would like to send messages to a specific node with a BLE interface using</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 20 Mar 2019 07:59:48 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/44384/managing-a-ble-thread-application-with-unknown-ipv6-addresses" /><item><title>RE: Managing a BLE/Thread application with unknown IPv6 addresses</title><link>https://devzone.nordicsemi.com/thread/177229?ContentTypeID=1</link><pubDate>Wed, 20 Mar 2019 07:59:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7c454533-e42c-49d6-94d8-07f772c3de36</guid><dc:creator>Lukasz Duda</dc:creator><description>&lt;p&gt;Hello Simon,&lt;/p&gt;
&lt;p&gt;First of all, thank you for using nRF5 SDK for Thread and Zigbee!&lt;/p&gt;
&lt;p&gt;Thread protocol does not define any application layer and so it does not provide a way to discover addresses by embedded mechanisms.&lt;br /&gt;At the same time, Thread allows implementing any IPv6 based protocols on top.&lt;/p&gt;
&lt;p&gt;Unfortunately, in our SDK, we don&amp;#39;t provide an example of such a dedicated protocol e.g. DNS Server or mDNS.&lt;/p&gt;
&lt;p&gt;OpenThread API exposes UDP Socket API so you can try to implement or port existing DNS-like protocol (e.g. mDNS). Alternatively, you can check out our CoAP examples where we do proprietary address discovery based on CoAP queries (for provisioning purposes).&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Łukasz&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>