Decrypting BLE traffic from sniffer with CLI captured datahttps://devzone.nordicsemi.com/f/nordic-q-a/122798/decrypting-ble-traffic-from-sniffer-with-cli-captured-dataI&#39;m trying to use &#39;nrfutil ble-sniffer sniff --follow &quot;${target} public&quot; --port ${device} --output-pcap-file ${output} --coded --timeout 5000 --log-level info --log-output stdout --json&#39; in a script to split up automated testing captures, where targeten-USTelligent Community 13Thu, 09 Oct 2025 21:53:06 GMTRE: Decrypting BLE traffic from sniffer with CLI captured datahttps://devzone.nordicsemi.com/thread/551046?ContentTypeID=1Thu, 09 Oct 2025 21:53:06 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f35c7787-6ca7-49bb-96ca-d903f47a26b4JonathanCrockett<p>Can I get an update from your wireshark people on if there is a way to accomplish this? I&#39;d like to be able to capture and decode snippets of BLE conversations.</p><div style="clear:both;"></div>RE: Decrypting BLE traffic from sniffer with CLI captured datahttps://devzone.nordicsemi.com/thread/541869?ContentTypeID=1Wed, 09 Jul 2025 06:59:46 GMT137ad170-7792-4731-bb38-c0d22fbe4515:327084b5-bb94-4418-924a-73ea9bf6c9afSusheel Nuguru<p>I am not an expert in this but it seems like when you run that command, it just spits raw Link-Layer frames into your PCAP. Once the BLE link goes encrypted, you’re looking at ciphertext—there’s no built-in hook for <code>nrfutil</code> to drop in your Long Term Key (LTK). That’s why nothing you do afterward in Wireshark seems to stick. The people with wireshark expertise are away on summer vacation and unfortunately we need to wait until they come back after two weeks to be able get their insights and see if there is any other way to do this.</p><div style="clear:both;"></div>