Why Sniffer shows CONNECT_REQ from Slave to Master?

RE: Why Sniffer shows CONNECT_REQ from Slave to Master?

sidekick — Fri, 01 Jul 2016 13:04:58 GMT

I see the same behavior with Wireshark version: 1.12.11

RE: Why Sniffer shows CONNECT_REQ from Slave to Master?

Hung Bui — Mon, 18 May 2015 13:27:16 GMT

@Doug: thanks for the comment. Yes, we are looking into this and trying to find resource to work on an update. For now Wireshark v1.10 is recommended.

RE: Why Sniffer shows CONNECT_REQ from Slave to Master?

Doug — Sun, 10 May 2015 18:30:11 GMT

Take it easy, I was just trying to agree with the comment by Jan that it is very unlikely that this was a bug. That was my initial reaction too, but I finally decided it really was wrong. It happens that I lost my initial typing to an accidental page refresh, and when I wrote it the second time, I left out the starting clause where I explicitly agreed with Jan, and the whole paragraph ended up sounding a lot snootier than I intended. Sorry.

I came back just now to note that I rolled Wireshark back to 1.10.13 and it does work correctly.

Doug

RE: Why Sniffer shows CONNECT_REQ from Slave to Master?

endnode — Sun, 10 May 2015 18:08:45 GMT

(Well blaming someone for minor bug in the tool given free of charge is troublesome;) Surely every bug should be tracked and fixed ASAP. Just saying...)

RE: Why Sniffer shows CONNECT_REQ from Slave to Master?

Doug — Sun, 10 May 2015 17:58:51 GMT

Nordic: Please do give this issue some thought. It is not confidence inducing when the analysis tool is displaying incorrect data. My logs show slave->master for all SCAN_RSP and CONNECT_REQ transactions. Since I'm using the sniffer to help teach myself the details of the BLE protocol as well as debug a simple application, it's pretty confusing to find that "some" of what you are looking at is incorrectly displayed (or maybe it's incorrectly recorded by the hardware).

RE: Why Sniffer shows CONNECT_REQ from Slave to Master?

Hung Bui — Tue, 05 May 2015 08:32:33 GMT

@Wowow: Sorry that my answer might be not very clear. I meant it was completely wrong to display source of an advertising as "slave" beside what we already see that the direction was reversed on the CONN_REQ.

RE: Why Sniffer shows CONNECT_REQ from Slave to Master?

WowWow — Mon, 04 May 2015 14:53:55 GMT

@Hung Bui, I understood that there is some incompatibility issue with Wireshare v1.12.x. Let me check it again with Wireshark v1.10.

But it is hard to agree that the tool shows wrong direction due to no slave at advertising. I can see wrong direction again at SCAN_REQ although there is clear source and destination address.

RE: Why Sniffer shows CONNECT_REQ from Slave to Master?

Hung Bui — Mon, 04 May 2015 13:04:32 GMT

@Wowow: I just checked, it was an issue with Wireshark v1.12 where information on the Source and Destination is not correctly displayed. The way it showed the source is Slave with a advertising packet is wrong because there is no slave at broadcasting but advertiser.

The direction on the CONNECT_REQ is wrong, but if you check Bluetooth Low Energy Link Layer you can find the initiator address and advertising address was correctly parsed.

The nRFsniffer plugin for Wireshark haven't been tested &optimized to work with Wireshark from version 1.11. Our suggetion for now is to download and use Wireshark v1.10 which is more compatible with our Sniffer. On Wireshark v1.10 correct source and destination is showed.
You can download earlier version of wireshark here

RE: Why Sniffer shows CONNECT_REQ from Slave to Master?

endnode — Sun, 03 May 2015 09:43:33 GMT

Interesting, I see the same in my logs. It's obviously wrong from BLE point of view but when you go inside the data you see that this indication is only in metadata coming from Nordic Sniffer FW or underlying app so it could be a) easily corrected and b) it does not affect the true BLE data presented in "Bluetooth Low Energy Link Layer" and upper stack layers (if present). Let's see what Nordic folks think about it;).

RE: Why Sniffer shows CONNECT_REQ from Slave to Master?

WowWow — Sun, 03 May 2015 02:50:32 GMT

I've seen some other posts which are same directions.

RE: Why Sniffer shows CONNECT_REQ from Slave to Master?

endnode — Sat, 02 May 2015 20:18:00 GMT

Hi WowWow, this sounds very unlikely. Could you attach any example (image or raw trace from Wireshark)? Cheers Jan