【nRF Sniffer for Bluetooth LE】AUX_SCAN_REQ cannot be displayed on Wireshark

Hello,

We don't have any examples that does extended scannable directed advertising, so I can't easily test this. Are you certain that the scanner actually sends the AUX_SCAN_REQ? Also, have you tried to select the device from the dropdown menu:

Best regards,

Vidar

Hello Vidar Bro,

Many thanks for your prompt response. 

user4240 said:

Are you certain that the scanner actually sends the AUX_SCAN_REQ?

yes, I can confirm that the scanner sends the AUX_SCAN_REQ as I tried to sniff the air packets with ellisys tool, the details as below:

also, the nRF connect app can also obtain the AUX_SCAN_RSP packets.

user4240 said:

Also, have you tried to select the device from the dropdown menu

I cannot find the device from here, but the windows showed me that the device is present. also, I tried to restart again, the results are the same, the details as below:

thanks.

Hello Vidar Bro,

Many thanks for your prompt response. 

user4240 said:

Are you certain that the scanner actually sends the AUX_SCAN_REQ?

yes, I can confirm that the scanner sends the AUX_SCAN_REQ as I tried to sniff the air packets with ellisys tool, the details as below:

also, the nRF connect app can also obtain the AUX_SCAN_RSP packets.

user4240 said:

Also, have you tried to select the device from the dropdown menu

I cannot find the device from here, but the windows showed me that the device is present. also, I tried to restart again, the results are the same, the details as below:

thanks.

Hello,

Please try to restart the capture if the device is not showing up in the device list. One of the developers here confirmed that the sniffer will not wait for the AUX_SCAN_REQ if you have not selected which advertiser to track first.

Best regards,

Vidar

Hello Vidar Bro,

yes, I tried to select the device from the dropdown menu after restarting several times, but I cannot find it from that, however, the device indeed is advertising. I can find it on the captured windows. it is very strange, but I can confirm that it works well when the event type change from scannable directed event to scannable undirected event.  it seems that it is a bug of nRF Bluetooth LE sniffer firmware, the device list may discard the device which is scannable directed event.

thanks.

Hello,

Do you have privacy enabled when you do directed advertising? In that case, you will need to provide the IRK as explained here: Sniffing advertisement packets involving a privacy-enabled Peripheral

Hello Vidar Bro,

no, as you can see above, I am using the public address, not RPA, both of them are public type

also, as I said above, I only change the event type from scannable directed event to scannable undirected event.. the device can be found from the device list at this moment

Hello,

Ok, it's starting to look like a possible bug. I will try to set up a test here and see if I can reproduce the issue.