This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Wireshark BLE Sniffer is not showing any packets during or after Peripheral connect

I start the sniff and see packets from all advertising peripherals in the area.
I select my peripheral in the Device dropdown list.
Then I see a string of "ADV_IND" packets from my device only.
I have no Capture or Display filter active.
All well and good.

Then I enable my Central device and start the connect.
-> They connect without any trouble and start streaming data.
However all I see in Wireshark is a single "CONNECT_IND" packet. Nothing else.

--> I don't see any other packets!
Does anyone have any guesses as to what I'm doing wrong?
Driver/firmware/software versions perhaps?

Setup:

- Mac (Catalina)

- nRF51822 v2 (with Driver = Silicon Labs: CP210x Macintosh OS VCP Driver v6)
(note: dongle came preprogrammed from Adafruit, April 6, 2021)

- Wireshark v 3.4.4 (and Python v3.9.4)

- nRF_sniffer_for_bluetooth_le_3.1.0

Thank you in advance for any suggestions.

Parents
  • Hi

    Indeed, that was noted in the setup, but it wasn't clear to me whether you used it as the Sniffer device or the peripheral/central in your setup. Thank you for clarifying that. The reason I'm asking is because the nRF51 for instance, does not support larger MTU sizes like what was introduced in Bluetooth 5.0, and if so would have issues following a connection where the MTU size wasn't supported (for instance).

    Can you show me a sniffer trace with some details on this? 

    The J-Link firmware should be updated because the communication from the DK goes over UART (the OB-Segger/JLink on the nRF51 DK). 

    The links I provided were provided because you don't receive (some) packets in Wireshark, or appears unstable. We're also currently investigating the nRFSniffer on the Catalina OS, as we've had one other customer having issues with it as well, and I have updated our internal ticket with your report as well.

    The best suggestion we have taking the "pressed for time" into consideration would be to test if you can see the same behavior on a Windows computer for instance, or if you have an nRF52 DK available, use that as a sniffing device.

    Best regards,

    Simon

Reply
  • Hi

    Indeed, that was noted in the setup, but it wasn't clear to me whether you used it as the Sniffer device or the peripheral/central in your setup. Thank you for clarifying that. The reason I'm asking is because the nRF51 for instance, does not support larger MTU sizes like what was introduced in Bluetooth 5.0, and if so would have issues following a connection where the MTU size wasn't supported (for instance).

    Can you show me a sniffer trace with some details on this? 

    The J-Link firmware should be updated because the communication from the DK goes over UART (the OB-Segger/JLink on the nRF51 DK). 

    The links I provided were provided because you don't receive (some) packets in Wireshark, or appears unstable. We're also currently investigating the nRFSniffer on the Catalina OS, as we've had one other customer having issues with it as well, and I have updated our internal ticket with your report as well.

    The best suggestion we have taking the "pressed for time" into consideration would be to test if you can see the same behavior on a Windows computer for instance, or if you have an nRF52 DK available, use that as a sniffing device.

    Best regards,

    Simon

Children
No Data
Related