Why Sniffer shows CONNECT_REQ from Slave to Master?

[WowWow]

Not only myself but also other captured logs: It shows CONNECT_REQ from Slave to Master. Is it right?

[Hung Bui]

@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

[WowWow]

@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.

[Hung Bui]

@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.