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

trouble capturing using nrf_sniffer_2.0.0-beta-1_51296aa

Hello,

I'm unable to capture packets using the sniffer.  Here are details regarding my set-up:

System: Debian 9.4 with kernel 4.9.0-4-amd64 #1 SMP Debian 4.9.65-3 (2017-12-03) x86_64 GNU/Linux

Sniffer target: pca10040.

Wireshark version: 2.6.1 (built from source, with all default options, except --enable-setuid-install)

Segger J-Link version:  SEGGER J-Link Commander V6.16c (Compiled Jun 16 2017 18:16:23)

Observations and symptoms:

The target shows up as interface /dev/ttyACM0.  I can use minicom to verify that data is being received on that interface.  On the pca10040 target, LED1 is dark; LED2 is blinking quite fast and at a somewhat random cadence, probably indicating received packets; LED3 and LED4 are on solid.

I checked for a permissions problem.  Here are some things I checked:

saturn:~> l /dev/ttyACM0
crw-rw-rw- 1 root dialout 166, 0 Jul 6 10:48 /dev/ttyACM0
saturn:~> groups
ken dialout cdrom floppy audio dip video plugdev scanner bluetooth netdev plex wireshark eclipse
saturn:~>

So, it seems like permissions are OK.  Also, I can use minicom on that interface from a non-root account.  And, I have run a lot of other applications on the same target with no connectivity issues.

I installed the python script nrf_sniffer.py and the subdirectory SnifferAPI in the wireshark extcap directory as specified in the documentation:

saturn:/usr/local/lib/wireshark/extcap> l
total 436
-rwxr-xr-x 1 ken ken 20294 Jan 1 1980 nrf_sniffer.py
-rw-r--r-- 1 ken ken 43 Nov 23 2017 nrf_sniffer.bat
drwxr-sr-x 4 root staff 4096 Jul 3 12:05 ..
-rwxr-xr-x 1 root staff 198864 Jul 5 18:00 androiddump
-rwxr-xr-x 1 root staff 107648 Jul 5 18:00 randpktdump
-rwxr-xr-x 1 root staff 97168 Jul 5 18:00 udpdump
drwxr-sr-x 3 root staff 4096 Jul 5 18:00 .
drwxr-sr-x 2 ken ken 4096 Jul 6 10:20 SnifferAPI

When I start up wireshark, highlight the "nRF Sniffer: /dev/ttyACM0" interface, and then begin a capture, a window pops up immediately indicating "No packets captured."

Additionally, the following appears on the default console:

CaptureEvent [ 1 ]: 256 with session
CaptureEvent [ 2 ]: 1
CaptureEvent [ 257 ]: 2 with session
CaptureEvent [ 257 ]: 4 with session
CaptureEvent [ 2 ]: 8
CaptureEvent [ 2 ]: 16

Any ideas on what's going on or what to try next?

Thanks.

--ken

Related