<?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>Disconnect IPv6 with Peripheral?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/5532/disconnect-ipv6-with-peripheral</link><description>I&amp;#39;m using the nrf51822 with the IoT softdevice and SDK as an IPv6/6LoWPAN peripheral and Linux with a BLE dongle in the central role. Basically, I have everything working such that: 
 echo &amp;quot;connect 00:AA:BB:XX:YY:ZZ 1&amp;quot; &amp;gt; /sys/kernel/debug/bluetooth/6lowpan_control</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 11 Feb 2015 08:50:17 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/5532/disconnect-ipv6-with-peripheral" /><item><title>RE: Disconnect IPv6 with Peripheral?</title><link>https://devzone.nordicsemi.com/thread/19347?ContentTypeID=1</link><pubDate>Wed, 11 Feb 2015 08:50:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7182a301-07d6-466b-9e95-b7e975fa1d7f</guid><dc:creator>Krishna Shingala</dc:creator><description>&lt;p&gt;Hi Brad,&lt;/p&gt;
&lt;p&gt;ble_ipsp_handle_t is defined in ble_ipsp.h and consists of connection handle and L2CAP channel id. This header is available to you. And you are right the API ble_ipsp_disconnect is designed for disconnection of L2CAP channel with out disconnecting the BLE link.&lt;/p&gt;
&lt;p&gt;However, since 6lowpan module registers the callback with IPSP module you do not have information of what the right value for p_handle should be which are notified when the  (L2CAP)connection is established. And this is a short coming in our API today. We hope to improve it future releases. Thank you for bringing this to our notice!&lt;/p&gt;
&lt;p&gt;In the meanwhile, you achieve a disconnection by disconnecting the BLE link instead of just the L2CAP link. this can be done by calling sd_ble_gap_disconnect. This requires connection handle for the BLE link and can be obtained when BLE_GAP_EVT_CONNECTED is notified.&lt;/p&gt;
&lt;p&gt;Hope this helps!&lt;/p&gt;
&lt;p&gt;Regards,
Krishna&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>