<?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>nRF52DK as sniffer</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/84218/nrf52dk-as-sniffer</link><description>Hello, I&amp;#39;m trying to use the nRF52DK development kit as a Bluetooth sniffer. after following your &amp;quot;nRF_Sniffer_UG_v2.2.pdf&amp;quot; guide, all I see in Wireshark are advertising messages of the peripheral device. I&amp;#39;m using: 
 Wireshark 3.6.1 
 sniffer_nrf52dk_nrf52832_4</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 31 Jan 2022 13:00:59 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/84218/nrf52dk-as-sniffer" /><item><title>RE: nRF52DK as sniffer</title><link>https://devzone.nordicsemi.com/thread/350426?ContentTypeID=1</link><pubDate>Mon, 31 Jan 2022 13:00:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3322127e-59b2-45bd-82eb-4553dcb86330</guid><dc:creator>Karl Ylvisaker</dc:creator><description>&lt;p&gt;Great, I am happy to hear that!&lt;br /&gt;&lt;br /&gt;Please do not hesitate to open another ticket if you encounter any issues or questions in the future.&lt;br /&gt;&lt;br /&gt;Good luck with your development!&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Karl&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52DK as sniffer</title><link>https://devzone.nordicsemi.com/thread/350423?ContentTypeID=1</link><pubDate>Mon, 31 Jan 2022 12:56:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c2782da0-2b42-4a0c-bb74-c48bc649ce19</guid><dc:creator>oee</dc:creator><description>&lt;p&gt;Hi, after reinstalling wireshark and jlink, and burning&amp;nbsp;sniffer_nrf52dk_nrf52832_7cc811f.hex to the board the sniffer works as expected.&lt;br /&gt;thanks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52DK as sniffer</title><link>https://devzone.nordicsemi.com/thread/350359?ContentTypeID=1</link><pubDate>Mon, 31 Jan 2022 08:34:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d5b42e78-36a5-4842-b278-4f06894c2781</guid><dc:creator>Karl Ylvisaker</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
[quote user=""]all I see in Wireshark are advertising messages of the peripheral device.[/quote]
&lt;p&gt;Could you confirm that you have chosen the device you would like to follow in the wireshark drop-down menu shown in the included image?&lt;br /&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/3364.wiresharkSourceDevice.PNG" /&gt;&lt;br /&gt;The default here is &amp;quot;all advertising devices&amp;quot; and it means that the sniffer will not follow into any connections.&lt;br /&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/ug_sniffer_ble/UG/sniffer_ble/sniffing_actions.html"&gt;The User Guide details the most common scenarios here&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Furthermore, can you also confirm whether or not the devices use bonding for their connection, so that they might already be bonded to each other? Are you testing this on a windows or OS X machine - which version are you using?&lt;br /&gt;Lastly, it would be great if you could include the sniffer trace of any unexpected behavior that you observe, so that I may take a look.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Karl&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>