<?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 sniffer with BLE communication indicates bad MIC</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/52240/nrf-sniffer-with-ble-communication-indicates-bad-mic</link><description>Hi, 
 
 I use nrf sniffer to monitor BLE communication. After pairing with encryption, wireshark indicates Encrypted packet decrypted incorrectly (bad MIC). 
 I think there is no MIC data in BLE packet. Could you help to confirm and fix this issue? 
</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 18 Sep 2019 13:48:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/52240/nrf-sniffer-with-ble-communication-indicates-bad-mic" /><item><title>RE: nrf sniffer with BLE communication indicates bad MIC</title><link>https://devzone.nordicsemi.com/thread/210448?ContentTypeID=1</link><pubDate>Wed, 18 Sep 2019 13:48:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dc80e337-e081-40e3-9b23-b80a6157f6fd</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Unfortunately it seems Wireshark can&amp;#39;t support this, however for instance Ellisys and Frontline sniffer may (though they are much more expensive).&lt;/p&gt;
&lt;p&gt;Edit: It may be possible to set LTK in Wireshark also, can you try to follow the procedure to set OOB as described in the nRF sniffer user guide,&amp;nbsp;this&amp;nbsp;may work:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/struct_nrftools/struct/nrftools_nrfsniffer.html"&gt;https://infocenter.nordicsemi.com/topic/struct_nrftools/struct/nrftools_nrfsniffer.html&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf sniffer with BLE communication indicates bad MIC</title><link>https://devzone.nordicsemi.com/thread/210163?ContentTypeID=1</link><pubDate>Tue, 17 Sep 2019 14:00:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:890f3f1d-8320-404d-bfa4-8460790fece6</guid><dc:creator>Akram</dc:creator><description>&lt;p&gt;Hi Kenneth,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you for your reply. Could you advice how to configure Wireshark with LTK key?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf sniffer with BLE communication indicates bad MIC</title><link>https://devzone.nordicsemi.com/thread/210118?ContentTypeID=1</link><pubDate>Tue, 17 Sep 2019 12:21:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:424c72bf-321e-4a92-8f41-8c5a761e8d2b</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;If you are using LE secure connection (Diffie-Hellman) then it is not possible to decrypt the link. The only way would be if you can extract the LTK key from one of the peer devices.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;So you would need to modify the application firmware running on the nRF52. From my understanding the easiest may be to call pm_peer_data_bonding_load() to fetch LTK, this can for instance be done after&amp;nbsp; PM_EVT_PEER_DATA_UPDATE_SUCCEEDED event, and then output this on UART and then insert this into the sniffer trace manually.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>