<?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>How to use Wireshark capture connection packets AND broadcast packets</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/8415/how-to-use-wireshark-capture-connection-packets-and-broadcast-packets</link><description>I want to capture connection packets between BLE Master and Slave
(this part is easy) but also capture any advertisement send out by slave
at the same time. 
 Our BLE peripheral received data from Central device and forward out
as broadcast packet</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 29 Jul 2015 09:11:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/8415/how-to-use-wireshark-capture-connection-packets-and-broadcast-packets" /><item><title>RE: How to use Wireshark capture connection packets AND broadcast packets</title><link>https://devzone.nordicsemi.com/thread/30572?ContentTypeID=1</link><pubDate>Wed, 29 Jul 2015 09:11:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b0441a7a-b249-4f5b-a933-a0214b9436b7</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;@Jeffrey Tang: I also don&amp;#39;t have any other suggestion than using 2 instance of the sniffer (with 2 dongle). Our sniffer currently when following a connection won&amp;#39;t be able to capture other advertising packet. I don&amp;#39;t know much about our plan in the future version of the sniffer.&lt;/p&gt;
&lt;p&gt;But what you can do is to sync them using a advertising packet from the peripheral before it enters connection mode (Set time reference). Both 2 sniffers should be able to capture this packet. And then you can maybe merge the two traces together base on this relative timing.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to use Wireshark capture connection packets AND broadcast packets</title><link>https://devzone.nordicsemi.com/thread/30571?ContentTypeID=1</link><pubDate>Wed, 29 Jul 2015 00:31:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a6ccb598-b6b8-42d2-9c3e-e44fffada455</guid><dc:creator>Jeffrey Tang</dc:creator><description>&lt;p&gt;two sniffers are not sync to each other, so still cannot figure out the interval between a packet A received on sniffer #1 and another packet B received on sniffer #2.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to use Wireshark capture connection packets AND broadcast packets</title><link>https://devzone.nordicsemi.com/thread/30570?ContentTypeID=1</link><pubDate>Tue, 28 Jul 2015 20:52:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ad2122ca-6b3d-4dc0-9023-9109d2b56834</guid><dc:creator>syntroniks</dc:creator><description>&lt;p&gt;Perhaps you could obtain a second sniffer dongle and run 2 instances of the sniffer, instructing one not to follow connection packets. This may or may not require two instances of wireshark.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>