Unzip the content of this file to your workspace. Inside the zip-file you will find another zip-file called SnifferAPI.zip. Working installation of SEGGER J-Link drivers (To flash the chip with the firmware)ĭownload the Sniffer API and firmware here: nRF Sniffer.Personally when I'm doing development I use my build only for reading capture files (except on the rare occasion I'm trying to fix something in the capture mechanism).Here is a small guide on how to build Wireshark with a BLE plugin under linux, with a small example on using this plugin with the Nordic Sniffer API. Unfortunately the only ways around this are to install what you've built (e.g., 'make install' or build a package and install it) or run as root (not a great idea-and if you're using a real plugin as opposed to a built-in dissector, your plugin won't get loaded while running as root from the build directory). Linux doesn't allow shell scripts to have capabilities nor be setuid so when you run it, it'll run as you and without the necessary capabilities. dumpcap isn't an binary executable, it's a (libtool) shell script. dumpcap = cap_net_admin,cap_net_raw+eipīut still my compiled wireshark/dumpcap cannot access eth0. usr/local/bin/dumpcap = cap_net_admin,cap_net_raw+eip configure -enable-dumpcap -enable-setcap-installĪnd set the capture properties to match the ubuntu package's dumpcap: I have tried various options with the configure script, eg: However, when Iīuild from source, my user account cannot capture on eth0. Installed and working properly from my user account and am able toĬapture packets on eth0 (using the wireshark group). I'm trying to build wireshark (1.10.6) from source on my Ubuntu 14.04

Wireshark ubuntu 14.04 install