Analyzer for PCAP files
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
maride 29aba89b6a Replace ASCII tree drawing with Unicode symbols 2 days ago
analyze Get rid of LinkType-style branching: different LinkTypes may use the same Protocol modules. 2 days ago
common Replace ASCII tree drawing with Unicode symbols 2 days ago
output Do not print empty blocks 5 days ago
protocol Get rid of LinkType-style branching: different LinkTypes may use the same Protocol modules. 2 days ago
.drone.yml indentation 1 week ago
.gitignore Add .gitignore 1 week ago
CONTRIBUTORS.md added myself (emile) to the users list 1 week ago
LICENSE Add License 2 weeks ago
README.md added a benchmark section to the readme 1 week ago
analyzer_test.go basic testcase for the analyzer 1 week ago
file.go Move code out of src/ folder to comply to Golang standards (although it looks dirty) 1 week ago
go.mod go mod init 1 week ago
go.sum go mod init 1 week ago
main.go Get rid of LinkType-style branching: different LinkTypes may use the same Protocol modules. 2 days ago

README.md

pancap

Idea

If you get access to a PCAP file, for example during a CTF or captured on your own, you usually have the problem of overlooking all the relevant information to get a basic idea of the capture file. This gets worse if the capture file includes lots of white noise or irrelevant traffic - often included in the capture file to cloak interesting packets in a bunch of packets to YouTube, Reddit, Twitter and others.

pancap addresses this problem. With multiple submodules, it analyzes the given PCAP file and extracts useful information out of it. In many cases, this saves you a lot of time and can point you into the right direction.

Usage

Simply run

go get git.darknebu.la/maride/pancap

This will also build pancap and place it into your GOBIN directory - means you can directly execute it!

In any use case, you need to specify the file you want to analyze, simply handed over to pancap with the -file flag.

Example usage:

pancap -file ~/Schreibtisch/mitschnitt.pcapng

This will give you a result similar to this:

asciicast

Benchmarks

Parsing an nGB big pcap takes y seconds:

nGB y seconds
2 30

Contributions

… yes please! There are still a lot of modules missing. If you are brave enough, you can even implement another Link Type. Pancap currently only supports Ethernet (which, to be honest, fits most cases well), but USB might be interesting, too. Especially sniffed keyboard and mouse packets are hard to analyze by hand…