https://devzone.nordicsemi.com/f/nordic-q-a/89445/could-nrf-sniffer-detect-and-follow-zephyr-ncs-appsHi there, I am wondering could the nRF sniffer follow a connection of two nRF Connect SDK built applications? What I got is like the following: After some searching in the DevZone, I followed their advice but still got into this &quot;bad MIC&quot; caseen-USTelligent Community 13Sun, 03 Jul 2022 05:06:38 GMThttps://devzone.nordicsemi.com/thread/375210?ContentTypeID=1Sun, 03 Jul 2022 05:06:38 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0a4601dc-64e2-4779-ae0d-ae19a8c73321EthanJia<p>Hi Einar,</p> <p>Thanks! I figured out what is the problem here.</p> <p>Appreciate it a lot!</p> <p>Best regards :-)</p> <p>Ethan</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/374728?ContentTypeID=1Wed, 29 Jun 2022 12:02:45 GMT137ad170-7792-4731-bb38-c0d22fbe4515:799c3c39-7b07-4d61-8e40-1abbc61c9bacEinar Thorsrud<p>Hi Ethan,</p> <p>The nRF Sniffer sniffs Bluetooth communication with is standardized, so it does not matter which SDK the firmware is built with, and it can also be used to sniff traffic between non-Nordic devices.</p> <p>As you get&nbsp;bad MIC that indicates that the packets are encrypted. The nRF Sniffer (like most other Bluetooth sniffers) can decrypt encrypted traffic if the pairing was done using legacy pairing, and the sniffer received the pairing packets, as then it will also have the key. However, if the sniffer did not receive the packets, or if pairing is done using LE Secure Connections (using a Diffie–Hellman key exchange), the sniffer is not able to decrypt the packets as it has no way of knowing the key.</p> <p>Einar</p><div style="clear:both;"></div>