<?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>nRFSniffer shows only Advertisement Indicators</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/18022/nrfsniffer-shows-only-advertisement-indicators</link><description>I&amp;#39;m trying to listen to a bluetooth low energy connection between a smart bracelet and my smartphone. In Wireshark 1.10.1 I only can see the Advertising Indicators. As soon as the bracelet is paired with the smartphone application, I can&amp;#39;t see any further</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 29 Nov 2016 14:59:04 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/18022/nrfsniffer-shows-only-advertisement-indicators" /><item><title>RE: nRFSniffer shows only Advertisement Indicators</title><link>https://devzone.nordicsemi.com/thread/69462?ContentTypeID=1</link><pubDate>Tue, 29 Nov 2016 14:59:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:47b4276d-0a06-441a-9a6b-e3068dcce560</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;It&amp;#39;s partly related to what I mentioned above, by default we customized the sniffer to catch Nordic advertising packets which by default sending advertising packet on channel 37 then 38 then 39 then on next advertising interval we will start with 37 again. (equal to pressing 7 then 8 then 9 when configuring)&lt;/p&gt;
&lt;p&gt;Device from other vendor may not use the same hopping scheme, and the option to press -h is to modify to match with the hopping scheme on those devices.&lt;/p&gt;
&lt;p&gt;You may want to play a little bit with the scheme to find the one match with your device.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRFSniffer shows only Advertisement Indicators</title><link>https://devzone.nordicsemi.com/thread/69460?ContentTypeID=1</link><pubDate>Tue, 29 Nov 2016 12:11:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:baec9676-4311-4e55-9534-12ffff16cf97</guid><dc:creator>fatalkernelpanic</dc:creator><description>&lt;p&gt;Finally, it works! This is how I did it:
Make both bracelets advertise themself (both are not connected to the android app). Then I started Wireshark (&amp;quot;w&amp;quot;) out of the sniffer application. I can see the advertisments of both devices. Next, I selected device 0 and paired this device with tha android application. After the pairing/connection was successful, I couldn&amp;#39;t see any further data in wireshark. Then, I just tried the parameter &amp;quot;h&amp;quot;, which means &amp;quot;Define new adv hop sequence&amp;quot;. I have tried values from &amp;quot;7&amp;quot; to &amp;quot;9&amp;quot; which stands for channel 37 to 39. At the end, I set it to channel 37 again. After that procedure, I can see the full communication between smartphone and bracelet. I don&amp;#39;t exactly know what I did there, but it works. If you know what the adv hop sequence means, could you explain me what I did there? Thank you!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRFSniffer shows only Advertisement Indicators</title><link>https://devzone.nordicsemi.com/thread/69461?ContentTypeID=1</link><pubDate>Tue, 29 Nov 2016 11:58:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:06735b13-92e7-4ff0-97e2-3916e6da029e</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Could you attach a sniffer trace ?&lt;/p&gt;
&lt;p&gt;It could be that the connect request to establish connection  is not captured by the sniffer. Note that the sniffer is made to capture traffic with Nordic chip (on at least one peer) it may not work with BLE communication from other vendors.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRFSniffer shows only Advertisement Indicators</title><link>https://devzone.nordicsemi.com/thread/69454?ContentTypeID=1</link><pubDate>Tue, 29 Nov 2016 10:42:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:30cb3cec-3ba0-4c0c-84b9-eb34761f26d2</guid><dc:creator>fatalkernelpanic</dc:creator><description>&lt;p&gt;Hi, thank you for your support. I have to bracelets, and both of them are shown in wireshark when I have no device selected. If I select a bracelet, I can only see the advertisements of the selected device in wireshark. The advertisements of the other bracelet aren&amp;#39;t shown anymore.
I already have the latest FTDI version.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRFSniffer shows only Advertisement Indicators</title><link>https://devzone.nordicsemi.com/thread/69463?ContentTypeID=1</link><pubDate>Tue, 29 Nov 2016 08:42:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b7a775ef-05b7-4d8f-af93-afe4ceefe415</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Could you try to test with 2 devices advertising (make sure you see both of them in Wireshark) and when you press select one device, would you still see the other device in Wireshark ? This is to check if it&amp;#39;s actually following that device or simply receive no command from PC.&lt;/p&gt;
&lt;p&gt;Could you try to update the latest version of FTDI chip as telling &lt;a href="https://learn.adafruit.com/introducing-the-adafruit-bluefruit-le-sniffer/introduction"&gt;here&lt;/a&gt; also ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRFSniffer shows only Advertisement Indicators</title><link>https://devzone.nordicsemi.com/thread/69459?ContentTypeID=1</link><pubDate>Mon, 28 Nov 2016 17:21:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4beb9b2e-1a94-44c7-9ac7-00f9846c97e5</guid><dc:creator>F800</dc:creator><description>&lt;p&gt;I have the same issue and confirm that (in my case) I see the data while the peripheral is advertising but as soon as they CONNECT, the wireshark displays no further data until I DISCONNECT.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRFSniffer shows only Advertisement Indicators</title><link>https://devzone.nordicsemi.com/thread/69458?ContentTypeID=1</link><pubDate>Mon, 28 Nov 2016 16:21:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b469c1d4-c245-4c8e-a681-f243a961368a</guid><dc:creator>fatalkernelpanic</dc:creator><description>&lt;p&gt;I have a smart bracelet (Juboury Fitness Tracker) which needs an app (Zeroner) to establish a bluetooth connection. The plain android bluetooth manager can&amp;#39;t handle out a connection. Because the app isn&amp;#39;t opensource, I can&amp;#39;t say exactly what it does to setup a connection.
If I start the sniffer application and press the sync button on the bracelet, it immediately shows up in the device list. Then, I select this device (typing in the device index) and start wireshark by pressing &amp;quot;w&amp;quot;. In Wireshark, I can see a lot of packets coming in, they&amp;#39;re all of the type &amp;quot;ADV_IND&amp;quot;.
Then I start the app &amp;quot;Zeroner&amp;quot; on my smartphone and do a device scan. In Wireshark, the ADV_IND packets are now coming even more frequently than before. When the bracelet was found, I click on it to build a connection. As soon as the connection between the app and bracelet is established, I don&amp;#39;t receive any further packet.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRFSniffer shows only Advertisement Indicators</title><link>https://devzone.nordicsemi.com/thread/69457?ContentTypeID=1</link><pubDate>Mon, 28 Nov 2016 16:05:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cab87725-3012-4a76-83d5-98d9afcc5569</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;It&amp;#39;s more important how the UART data is transferred to the PC, in our case (the Nordic sniffer using Nordic dongle) we use the Segger Jlink chip to work as FTDI chip. I haven&amp;#39;t tested with the Adafruit sniffer.&lt;/p&gt;
&lt;p&gt;Could you explain a little bit more on &amp;quot;As soon as the bracelet is paired with the smartphone application, I can&amp;#39;t see any further log entries in wireshark (but I know that there IS data exchange between bracelet and smartphone).&amp;quot;&lt;/p&gt;
&lt;p&gt;You meant paired or connected ? If the two device don&amp;#39;t pair but just connect can you see anything ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRFSniffer shows only Advertisement Indicators</title><link>https://devzone.nordicsemi.com/thread/69456?ContentTypeID=1</link><pubDate>Mon, 28 Nov 2016 15:58:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:165d93ae-87b7-42f5-abec-0a3e54be12f6</guid><dc:creator>fatalkernelpanic</dc:creator><description>&lt;p&gt;Thanks for your answer. I&amp;#39;m using a Bluefruit LE Sniffer from Adafruit. The firmware was pre-installed, but I did a reflash using a STLink/V2 adapter. I do also have a Jlink adapter available, but I didn&amp;#39;t use it as the flashing proccess with the STLink/V2 was successful.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRFSniffer shows only Advertisement Indicators</title><link>https://devzone.nordicsemi.com/thread/69455?ContentTypeID=1</link><pubDate>Mon, 28 Nov 2016 15:36:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8be1a73d-90c4-412b-89c0-71fac6c2f405</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Could you let us know which hardware you are using and which Jlink version is on your PC ?&lt;/p&gt;
&lt;p&gt;We got to this issue after Segger update their Jlink driver.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>