<?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>Unable to sniff LE Secure Connections in debug mode using nRF52840 Dongle</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/99432/unable-to-sniff-le-secure-connections-in-debug-mode-using-nrf52840-dongle</link><description>Test bed setup 
 
 Master device - RPI4 Model B Rev 1.2, raspbian/ debian version 11 (bullseye) 
 Slave device - Custom Bluetooth 5.2 device with BLE application running 
 Sniffer device - nrf52840 dongle with sniffer_nrf52840dongle_nrf52840_4.1.1 firmware</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 08 May 2023 12:37:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/99432/unable-to-sniff-le-secure-connections-in-debug-mode-using-nrf52840-dongle" /><item><title>RE: Unable to sniff LE Secure Connections in debug mode using nRF52840 Dongle</title><link>https://devzone.nordicsemi.com/thread/424276?ContentTypeID=1</link><pubDate>Mon, 08 May 2023 12:37:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:65a733cd-21ac-40f2-866e-64626c0ea94e</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The nRF sniffer will automatically be able to&amp;nbsp;decrypt&amp;nbsp;packets after listening on on a&amp;nbsp;LESC&amp;nbsp;pairing&amp;nbsp;procedure if one or both of the peers use the debug key and the sniffer was able to sniff all the relevant packets during the pairing procedure (see &lt;a href="https://infocenter.nordicsemi.com/topic/ug_sniffer_ble/UG/sniffer_ble/action_paired.html"&gt;Sniffing the pairing procedure of a connection&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;I see from the sniffer trace that the debug key is not used in #3735 (as this is not the debug public key&amp;nbsp;you can see in your snippet from the spec or&amp;nbsp;as &lt;a href="https://github.com/nrfconnect/sdk-zephyr/blob/4b5d5aa9ca8c414338f91f0c27f0e8426d2a6da0/subsys/bluetooth/host/ecc.c#L24"&gt;debug_public_key in ecc.c&lt;/a&gt;), but the commands you show seems to indicate that it should be in use (it is listed under &amp;quot;current settings&amp;quot;). I do not immediately see what could be the cause of this, but&amp;nbsp;perhaps you can bypass the issue by testing with debug keys on the nRF side? This is done by building with &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.3.0/kconfig/index.html#CONFIG_BT_USE_DEBUG_KEYS"&gt;CONFIG_BT_USE_DEBUG_KEYS&lt;/a&gt;&lt;code&gt;=y&lt;/code&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>