<?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>BLE Sniffer Update</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/28498/ble-sniffer-update</link><description>Hi Nordic, 
 Are there any plans to update the BLE Sniffer? 
 It would be great if all the op codes for logical link control could be added and to fix the malformed packets when sniffing an encrypted link</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 19 Dec 2017 09:33:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/28498/ble-sniffer-update" /><item><title>RE: BLE Sniffer Update</title><link>https://devzone.nordicsemi.com/thread/112762?ContentTypeID=1</link><pubDate>Tue, 19 Dec 2017 09:33:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:884665f0-bc80-4ba8-ab3b-fd6818525713</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;The new v2 sniffer beta1 is available for use, it supports some of the BT5 features like the new channel maps and some of the 4.x features like 2mbit mode. It still does not support data length extensions, which is targetted for beta2.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Sniffer Update</title><link>https://devzone.nordicsemi.com/thread/112763?ContentTypeID=1</link><pubDate>Tue, 19 Dec 2017 09:29:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b3951d2d-be64-4664-9660-2a88e99afc99</guid><dc:creator>viewtool</dc:creator><description>&lt;p&gt;Hollong Viewtool sniffer:
&lt;a href="https://www.amazon.com/ViewTool-Professional-Bluetooth-Protocol-Analyzer/dp/B074R9854R/ref=sr_1_fkmr0_2?ie=UTF8&amp;amp;qid=1513654458&amp;amp;sr=8-2-fkmr0&amp;amp;keywords=hollong+ble4.2"&gt;www.amazon.com/.../ref=sr_1_fkmr0_2&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;only $99 ,Support BLE 4.0/4.1/4.2 protocol analysis and interpret&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Sniffer Update</title><link>https://devzone.nordicsemi.com/thread/112761?ContentTypeID=1</link><pubDate>Wed, 29 Nov 2017 23:04:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d596a2b8-587f-4ee5-9a3e-aa534cc0c525</guid><dc:creator>goldwake</dc:creator><description>&lt;p&gt;Thanks David. It works. I had to do a little set up as described &lt;a href="https://devzone.nordicsemi.com/question/67447/wireshark-201-and-nrfsniffer/"&gt;here&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Sniffer Update</title><link>https://devzone.nordicsemi.com/thread/112760?ContentTypeID=1</link><pubDate>Fri, 24 Nov 2017 07:34:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2caa3668-69e1-4ade-a58a-fcc8c07d94ee</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;yes you can, Wireshark 2.4.1 and later fixed it.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Sniffer Update</title><link>https://devzone.nordicsemi.com/thread/112759?ContentTypeID=1</link><pubDate>Thu, 23 Nov 2017 19:40:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6269c314-3230-4e23-b931-37d15754a649</guid><dc:creator>goldwake</dc:creator><description>&lt;p&gt;v1.10.14. Can we use newer versions? the User guide specifies 1.10.x&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Sniffer Update</title><link>https://devzone.nordicsemi.com/thread/112758?ContentTypeID=1</link><pubDate>Thu, 23 Nov 2017 08:52:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f303581d-7a11-4ba9-804a-f849f6b0640e</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;What is the wireshark version that you are using ? Can you try the sniffer with Wireshark version 2.4.x and let us know about the opcodes that appear missing.
Malformed packets is an issue with the sniffer and that is still open at this point, we will attempt to fix it in the releases after the initial v2 release.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>