-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Errors reading pcap files, both in cli and code #240
Comments
Also, it appears that the PIP installation process does not ensure the installation of the python emoji package:
Not shown as an error, but still, would think it would be installed if it's a dependency. |
For the issue mentioned, would you please kindly confirm if you're still able to obtain the extracted packet data despite the console outputs? This is likely an issue with verbose error logging we have in place. We're looking to clean it up soon. For CLI dependency, you can install the required packages thru |
Describe the bug
Just starting to investigate how to use your library. My goal is to explore network traffic captures for ML algorithm exploitation, I've done some work with other libraries, but having difficulty with their data structures, so I thought I'd give this one a shot.
For simplicity to ensure things are installed and functional, I ran the cli command against a sample pcap like so:
pcapkit-cli -f tree --verbose HomeLabDMZ.pcap
this produces expected output up to around the 206th packet then produces an error. As best I can tell, the error comes from the httpv1.py library on line 131, where the packet seems to have been incorrectly typed as HTTP, when the packet is actually an ACK from the HTTP Server to the Client for the previous HTTP DATA packet in the stream.System information
A clear and concise description of your system information.
Traceback stack
Expected behavior
I don't know what to expect, except that errors are unexpected.
Additional context
I have a simple python script which is the beginnings of some ML work, that exhibits the same behavior with the same pcap file as input on the
pcapkit.extract
method. There are more instances of this error happening on other packets that seem to follow the same pattern, though sometimes it appears the conversation is https, not http.The text was updated successfully, but these errors were encountered: