-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows support for live capture #2
Comments
That nRF thing has it's own software and firmware. Sure you can pipe things to wireshark on windows too. Still leaves the question of how to read from serial into a file. I'm sure it's possible on windows. You can port it If you want. I just don't have any intentions to do so at the moment. |
Sorry didn't mean to close this issue. |
The nRF Sniffer is not using any files, it is not needed. When packet arrives it is send over UART to the PC (some kind of simple serialization is used - named SLIP, wihile it is not SLIP... ). The python script running on PC is deserializing a captured packet and pushes it to named pipe. |
I think this is a cool project (I am working on a similar one to detect MAC addresses in the proximity to control things). |
@SensorsIot you might want to open a new issue for this. I had the same error one or two times. |
Could have python write to wiresharks stdin itself instead of using a file as a middle man. (Using subprocess.communicate) |
Update* p = subprocess.Popen(cmd, stdout=subprocess.PIPE, shell=True) |
@spacehuhn i'm guessing you know by know allready, but just incase anyone missed it his gist also has a fix for the malformed packet i also have some ideas how do improve this using tcmenu for filtering packets. |
https://wiki.wireshark.org/CaptureSetup/Pipes
Maybe this mechanism could make this project to work in real time and on MS Windows. Anyway I saw this work for nRF sniffer.
https://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF-Sniffer
The text was updated successfully, but these errors were encountered: