<?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>nrf SDK IOT MQTT Publisher example, can&amp;#39;t ping from bt0 and interface go down</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/44801/nrf-sdk-iot-mqtt-publisher-example-can-t-ping-from-bt0-and-interface-go-down</link><description>Hi, I&amp;#39;m trying to do the iot mqtt publisher example with the nRF5_SDK_15.3.0_59ac345, a nrf52840 and a Raspberry Pi 3 B+ as a gateway but I got some problems : 
 After the connection with the nrf52840 (echo &amp;quot;connect 00:7E:3E:C4:C6:8C 1&amp;quot; &amp;gt; /sys/kernel</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 01 Jul 2020 14:58:57 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/44801/nrf-sdk-iot-mqtt-publisher-example-can-t-ping-from-bt0-and-interface-go-down" /><item><title>RE: nrf SDK IOT MQTT Publisher example, can't ping from bt0 and interface go down</title><link>https://devzone.nordicsemi.com/thread/257909?ContentTypeID=1</link><pubDate>Wed, 01 Jul 2020 14:58:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9ff5e147-357b-4399-b772-2ec859d422bd</guid><dc:creator>Moritz</dc:creator><description>&lt;p&gt;Hi!&lt;/p&gt;
&lt;p&gt;Did you solve the disconnection problem? If yes, could you explain how?&lt;br /&gt;I have the same problem with with a different iot example from the sdk.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf SDK IOT MQTT Publisher example, can't ping from bt0 and interface go down</title><link>https://devzone.nordicsemi.com/thread/175997?ContentTypeID=1</link><pubDate>Wed, 13 Mar 2019 15:29:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2b1c4f1d-d741-475d-8798-aeb8174f9a96</guid><dc:creator>Miafiaj</dc:creator><description>&lt;p&gt;I&amp;#39;ve succeeded into connecting the card to the broker on the RaspberryPi but the interface bt0 still disconnects even if I spam the publication to avoid timeout :&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/pastedimage1552490880802v1.png" alt=" " /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf SDK IOT MQTT Publisher example, can't ping from bt0 and interface go down</title><link>https://devzone.nordicsemi.com/thread/175957?ContentTypeID=1</link><pubDate>Wed, 13 Mar 2019 13:39:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8a933947-0676-41a2-aad4-7d99320d0fef</guid><dc:creator>Miafiaj</dc:creator><description>&lt;p&gt;Thank you very much for your quick answer and for the information about multiple connections. I used a second card because I didn&amp;#39;t succeed to use the example with the first one, but using multiple cards was my objective for later.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve set&amp;nbsp;the variable to 0 and I can now ping my card from bt0 but stil get &amp;quot;Address unreachable&amp;quot; for&amp;nbsp; pinging anything else. And bt0 still disconnect after some time, do you know where this come from ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf SDK IOT MQTT Publisher example, can't ping from bt0 and interface go down</title><link>https://devzone.nordicsemi.com/thread/175893?ContentTypeID=1</link><pubDate>Wed, 13 Mar 2019 11:22:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a3be2c5d-d898-4bb4-9376-702526df4d36</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Since you are running a kernel that is newer than v4.12, you should set this define to &amp;#39;0&amp;#39; (its default set to &amp;#39;1&amp;#39;):&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;// &amp;lt;/e&amp;gt;

// &amp;lt;q&amp;gt; BLE_6LOWPAN_LEGACY_MODE  - Enable legacy mode of IID derivation from Bluetooth Device Address and Link Layer address size determination. The legacy mode is not compatible with the RFC7668 sepcification. For the Linux Kernel versions higher or equal to 4.12 this define has to be set to 0, otherwise to 1.
 

#ifndef BLE_6LOWPAN_LEGACY_MODE
#define BLE_6LOWPAN_LEGACY_MODE 0
#endif&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Do note that there&amp;#39;s an issue with the bluetooth_6lowpan kernel module, where it only allows one connection:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/34042/multi-connection-of-ble-6lowpan-border-router/131313#131313"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/34042/multi-connection-of-ble-6lowpan-border-router/131313#131313&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>