Skip to content
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

support processing packet capture .pcap, pcapng files #255

Open
jtmoon79 opened this issue Mar 19, 2024 · 0 comments
Open

support processing packet capture .pcap, pcapng files #255

jtmoon79 opened this issue Mar 19, 2024 · 0 comments
Labels
difficult A difficult problem; a major coding effort or difficult algorithm to perfect enhancement New feature or request file parser P1 important

Comments

@jtmoon79
Copy link
Owner

jtmoon79 commented Mar 19, 2024

Support parsing packet capture .pcap and .pcapng

Support parsing packet capture files. There are Rust-based packet capture file parsers

Assuming pcap_parser works as well as I hope, a difficult part is deciding what to print from each packet. As a start, the most minimal information would be datetimestamp, frame source, frame destination. From there, the printing logic branches in many directions depending upon the packet content and the ability of pcap_parser to parse worthwhile data from it without panicking.

@jtmoon79 jtmoon79 added enhancement New feature or request P1 important difficult A difficult problem; a major coding effort or difficult algorithm to perfect file parser labels Mar 19, 2024
@jtmoon79 jtmoon79 changed the title support for pcap/pcapng support processing pcap/pcapng files Mar 19, 2024
@jtmoon79 jtmoon79 changed the title support processing pcap/pcapng files support processing packet capture .pcap, pcapng files May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficult A difficult problem; a major coding effort or difficult algorithm to perfect enhancement New feature or request file parser P1 important
Projects
None yet
Development

No branches or pull requests

1 participant