Wireshark Crash when Capture starts
Clem- opened this issue · 6 comments
I've flashed my nRF52840dk board with JFlashLite on macOS Mojave.
After copying nrf802154_sniffer.py in extcap directory of Wireshark 2.6.4, and modifying its first line with #!/usr/local/bin/python the "nRF 802.15.4 sniffer" interface appears in Wireshark.
Under interface options, I've selected Device=/dev/cu.usbmodem and let Channel=11.
Unfortunately, Wireshark crashes when starting the capture.
Do you get a stack dump from the Wireshark crash? I believe this is a Wireshark issue and you should create a bug report in the Wireshark Bug Database.
Do you know why you need to use /usr/local/bin/python? The version shipped with macOS Mojave should work.
Indeed, I noticed the Wireshark issue that you commented in May 18'. Unfortunately, the issue isn't solved yet.
Still, it is mentioned in the RF Sniffer README doc that the software was tested with macOS Mojave and Wireshark 2.6.4. Is it possible to specify the version of Python and pySerial that were used for the testing?
I had to use another Python interpreter path because the nRF802154 external capture wasn't appearing in Wireshark's list.
Thanks
I am getting the same result. I have tried it on two different Mac machines both running Mohave. Both behave the same way. As soon as you start a trace Wireshark dies. The version of Wireshark is 2.6.6 which is the current 'stable' release. I have not been able to locate a copy of 2.6.4 which is what is listed as having been tested.
Unlike Clem I did not need to alter the nrf802154_sniffer.py file to get the nRF52840 to show up.
I have had a lot of trouble with python and pyserial before. Is there any way to verify that the setup of Python and the nrf802154_sniffer.py is working correctly independent of Wireshark?
I just downloaded the development release of Wireshark 2.9.0 and replace my 2.6.6 copy. The nRF52840 dongle is now sniffing Zigbee packets. I guess the problem is with Wireshark somewhere.
Wireshark is close to the version 3.0 release. Are any of you able to test the latest RC version to verify that the crash issue is fixed?