nRF Sniffer not capturing packets after connection

I'm new to nRF Sniffer.  Just installed it and the installation seemed to go as expected.  I see my device in the device list when it is advertising.  After I select the device I can still see advertisement packets.  However, when the peripheral is connected to, then I no longer see any packets.  There is communication going on though.  Is there something that must be done to see the packets after the connection is made?

I'm using:

* nRF Sniffer 4.1.1

* nRF52840 Dongle (nRF6929 V 1.0.0 2018.22)

* M1 MacBook Pro Ventura 13.2.1

* Wireshark 4.0.3

Parents Reply Children
  • Correct, I can see advertising packets after filtering.  But when I connect I just see a single CONNECT_IND in wire shark and that's it.

    I believe I followed everything in the nRF sniffers documentation.

    This is the /tmp/logs/log.txt output:

    01-Mar-2023 17:04:43 (-0600) INFO: Software version: 4.1.1

    01-Mar-2023 17:04:43 (-0600) INFO: sniffer started

    01-Mar-2023 17:04:43 (-0600) INFO: starting scan

    01-Mar-2023 17:04:43 (-0600) INFO: Scan flags: 0b11

    01-Mar-2023 17:04:43 (-0600) INFO: Sent TK to sniffer: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]

    01-Mar-2023 17:04:43 (-0600) INFO: scanning started

    01-Mar-2023 17:04:43 (-0600) INFO: defaults written

    01-Mar-2023 17:04:43 (-0600) INFO: control loop

    01-Mar-2023 17:04:43 (-0600) INFO: Firmware version 4.1.1

    01-Mar-2023 17:04:43 (-0600) INFO: Firmware timestamp 35287739 reference: Mar 01 2023 17:04:43.619431 CST

    01-Mar-2023 17:09:55 (-0600) INFO: Clearing

    01-Mar-2023 17:11:32 (-0600) INFO: follow_device: [b'225', b' 187', b' 34', b' 69', b' 21', b' 200', b' 1']

    01-Mar-2023 17:11:32 (-0600) INFO: Sniffing device 14 - """"

    01-Mar-2023 17:11:32 (-0600) INFO: Follow flags: 0b0

    01-Mar-2023 17:11:33 (-0600) INFO: Following e1:bb:22:45:15:c8  random 

  • It started working.  Not totally sure why.  But I did install ChmodBPF.  From what it said, I assumed that was only needed to capture packets in the OS.  But maybe that is needed for the BLE sniffer also?

Related