Comments (9)
e-rk
commented on May 25, 2024
Hi,
It appears that Wireshark 2.9 sends its version as an additional command line parameter to let the extcap utility adapt its behaviour to different Wireshark versions, which is a bit unfortunate in this case.
I'll let you know once a fix is up.
from nrf-sniffer-for-802.15.4.
IanAber
commented on May 25, 2024
Thanks. Would that explain the crash of Wireshark when stopping capture?
I tried to run with 2.6.6 but could not even get it to start capturing. With 2.9 it starts but I cannot stop it without Wireshark crashing. I am running on Mac OX X Mohave with one of the nRF52840 Dongles set up as the sniffer.
Ian Abercrombie
[email protected] <mailto:[email protected]>
Phone: +1 (352) 281-6286
www.CedarTechnology.com <http://www.cedartechnology.com/>
… On Jan 24, 2019, at 4:22 PM, RaKu ***@***.***> wrote:
Hi,
It appears that Wireshark 2.9 sends its version as an additional command line parameter to let the extcap utility adapt its behaviour to different Wireshark versions, which is a bit unfortunate in this case.
I'll let you know once a fix is up.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#11 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEDZnO3T2_mocTS0USWRLZSSWKsjyPJ_ks5vGiQLgaJpZM4aPGOl>.
from nrf-sniffer-for-802.15.4.
e-rk
commented on May 25, 2024
Now that I think of it the unrecognized argument is pretty harmless in this case.
Unfortunately I have no idea why Wireshark crashes after capture on Mac and I have no way to verify it myself. If you run Wireshark from the terminal do you see any error logs when trying to stop the capture? I think this problem should be reported to Wireshark developers.
About the ZigBee broadcasts, do you have correct decryption keys set up? The sniffer does no data processing of sniffed packets so I suspect that it is a matter of changing the correct preferences in Wireshark. I am not familiar with ZigBee, so I can't help here either. Sorry.
from nrf-sniffer-for-802.15.4.
IanAber
commented on May 25, 2024
I found that running Wireshark as an administrator (using sudo wireshark from a terminal window) fixes the EINTR errors so it must be a permissions thing. My problem now is that as soon as I stop capture Wireshark crashes with a segmentation fault. I have posted a question on the Wireshark site and the admin asked where I got the Python script. I sent him the link to the Github site for NordicPlayground. I am fairly sure he is going to tell me it is a problem with the external capture piece so I imagine I am going to have to debug this bit myself.
Is it possible to get the sniffer to output directly into a terminal window or something outside of Wireshark so I can test out the capture and try feeding the resulting data info Wireshark as a file? I connected a terminal to the USB serial port and it looks like it should respond to some AT type commands. Do you know what I can send to get it to dump stuff out, if that is possible?
Ian Abercrombie
[email protected] <mailto:[email protected]>
Phone: +1 (352) 281-6286
www.CedarTechnology.com <http://www.cedartechnology.com/>
… On Jan 25, 2019, at 4:29 AM, RaKu ***@***.***> wrote:
Now that I think of it the unrecognized argument is pretty harmless in this case.
Unfortunately I have no idea why Wireshark crashes after capture on Mac and I have no way to verify it myself. If you run Wireshark from the terminal do you see any error logs when trying to stop the capture? I think this problem should be reported to Wireshark developers.
About the ZigBee broadcasts, do you have correct decryption keys set up? The sniffer does no data processing of sniffed packets so I suspect that it is a matter of changing the correct preferences in Wireshark. I am not familiar with ZigBee, so I can't help here either. Sorry.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#11 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEDZnJzYdkWLhodwXFNeJT8Zo-E85S-oks5vGs6RgaJpZM4aPGOl>.
from nrf-sniffer-for-802.15.4.
e-rk
commented on May 25, 2024
If you are in the repository root, you can install the module using the command:
python -m easy_install .
You might need root privileges for that.
Then the nrf802154_sniffer module can be imported into other python scripts. It exposes the Nrf802154Sniffer class. All you need to do is to call extcap_capture and give it the file name, serial port and channel as arguments. This should start dumping data to given file. To stop the capture call stop_sig_handler().
from nrf-sniffer-for-802.15.4.
stig-bjorlykke
commented on May 25, 2024
The crash on stop capture is Wireshark bug 14631.
from nrf-sniffer-for-802.15.4.
IanAber
commented on May 25, 2024
I managed to get past the Wireshark crash issue by downloading the source and recoiling Wireshark from scratch. Like everything els I have done recently it was not a smooth operation as the instructions didn’t cover all the requirements and the build scripts failed. I found the missing libraries and installed them and now Wireshark is recording packets correctly without blowing up when I stop the capture.
The next problem on the ridiculously steep learning curve to figuring this out, is how to get Wireshark to capture anything other than broadcast packets. What do I need to tell Wireshark to get all Zigbee packets to show up?
I have a Samsung Smartthings hub which s connected to a half a dozen Zigbee devices. One of these devices is a power outlet and I can turn it on and off via my iPhone app. This must be sending Zigbee packets to the socket but they do not show up in Wireshark. Neither do any of the network pulse checking packets that are being sent to confirm availability. All I see is Broadcast packets…
"34","2400.930382","","Broadcast","IEEE 802.15.4","8","Beacon Request”
What do I need to be able to see all communication from hub to device and back?
I really appreciate your help and feel guilty that I have been unable to work it out myself.
Ian Abercrombie
[email protected] <mailto:[email protected]>
Phone: +1 (352) 281-6286
www.CedarTechnology.com <http://www.cedartechnology.com/>
… On Jan 25, 2019, at 1:22 PM, Stig Bjørlykke ***@***.***> wrote:
The crash on stop capture is Wireshark bug 14631 <https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14631>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#11 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEDZnLRsOjvzTPNnfEOqzcb4wJeByko7ks5vG0tQgaJpZM4aPGOl>.
from nrf-sniffer-for-802.15.4.
IanAber
commented on May 25, 2024
Version 3.0.3 gets past the Wireshark crash issue.
from nrf-sniffer-for-802.15.4.
stig-bjorlykke
commented on May 25, 2024
@IanAber Good. I have closed Wireshark bug 14631 .
from nrf-sniffer-for-802.15.4.
Related Issues (20)
- USB device not recognised HOT 8
- LED indicators need to be described in readme.md HOT 1
- Remove DFU Trigger Library from the firmware HOT 5
- nRF52840-DK not recognized HOT 1
- Missing packets using the nRF52840 Dongle HOT 1
- Channel always goes to 11 after a reset in Wireshark with no way to change. HOT 3
- Could not Capture from multiple hardware interfaces on Windows HOT 1
- [question] 802.15.4 capabilities HOT 3
- Segfault on capture start Wireshark 3.2.0 HOT 2
- Q: Is the source code for the hex files available? HOT 14
- nRF52840 DONGLE DFU ZIP HOT 7
- FreeBSD umodem detect baudrate HOT 5
- Startup time is too long when start capturing packets HOT 2
- sniffer not support xiaomi phone's BLE packet HOT 1
- Firmware for other devkits, PCA10100
- Linux, Python, error after channel switching HOT 1
- nRF5340 DK support? HOT 1
- nRF52840 support for tshark? HOT 2
- nrf802154_sniffer.py doesn't exit on macOS when the capture is stopped HOT 8
- Cannot capture on a custom board with external JLINK! HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nrf-sniffer-for-802.15.4.