Not only myself but also other captured logs: It shows CONNECT_REQ from Slave to Master. Is it right?
Not only myself but also other captured logs: It shows CONNECT_REQ from Slave to Master. Is it right?
@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.
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).
(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...)
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
@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.