<?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 using Wireshark, BLE logs</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/75591/nrf-sniffer-using-wireshark-ble-logs</link><description>Device Name : nRF52840-DK PCA10056 
 I have 4 questions listed below, the reason is Instead of creating multiple ticket/case we can follow up using the same ticket to avoid unnecessary confusion. 
 1) What is the best method to sniff BLE packets using</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 26 May 2021 12:21:57 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/75591/nrf-sniffer-using-wireshark-ble-logs" /><item><title>RE: nRF Sniffer using Wireshark, BLE logs</title><link>https://devzone.nordicsemi.com/thread/311784?ContentTypeID=1</link><pubDate>Wed, 26 May 2021 12:21:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3c4aa91a-881d-4b63-b499-8a06c0adc6ef</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;Pranesh,&lt;/p&gt;
[quote user=""]1) What is the best method to sniff BLE packets using DK ?[/quote]
&lt;p&gt;If you want to use the DK as the sniffer HW, then the only option is the &lt;a href="https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Sniffer-for-Bluetooth-LE"&gt;nRF Sniffer&lt;/a&gt;. This is&amp;nbsp;often good enough, but not the same as a professional sniffer (such as an Ellisys or Frontline device).&lt;/p&gt;
[quote user=""]2) I&amp;#39;ve tried collecting logs using Wireshark but I could not see advertising name parameter why ?[/quote]
&lt;p&gt;Including the name in the advertising packet is optional. As this is missing here, it is&amp;nbsp;probably either part of the scan response packet, or that the name is not advertised at all.&lt;/p&gt;
[quote user=""]&lt;span&gt;3) I&amp;#39;ve tried collecting logs using Wireshark but I could not see &lt;strong&gt;ATT transaction&lt;/strong&gt; why (or)&lt;/span&gt;&amp;nbsp;Wireshark has capability to capture ATT Protocol ?[/quote]
&lt;p&gt;Yes, ATT packets are supported by Wireshark. See &lt;a href="https://infocenter.nordicsemi.com/topic/ug_sniffer_ble/UG/sniffer_ble/inspecting_data.html"&gt;Inspecting captured data&lt;/a&gt;. It does not give you the same level of presentation as you get from professional tools though.&lt;/p&gt;
[quote user=""]4)&amp;nbsp;Can we capture logs using Frontline FTS tool or Ellisys tool?&amp;nbsp;[/quote]
&lt;p&gt;Then you will need to use their HW.&amp;nbsp;For instance Ellisys Bluetooth Explorer is an excellent&amp;nbsp;sniffer.&lt;/p&gt;
&lt;p&gt;Br,&lt;/p&gt;
&lt;p&gt;Einar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>