update lists
This commit is contained in:
@@ -1,20 +1,16 @@
|
||||
<h2 id="introduction">Introduction</h2>
|
||||
<p><a href="https://github.com/sindresorhus/awesome"><img
|
||||
src="https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg"
|
||||
alt="Awesome" /></a> <a
|
||||
href="https://travis-ci.org/caesar0301/awesome-pcaptools"><img
|
||||
src="https://travis-ci.org/caesar0301/awesome-pcaptools.svg"
|
||||
alt="Build Status" /></a></p>
|
||||
alt="Awesome" /></a></p>
|
||||
<p>This project does not contain any source code or files. I just want
|
||||
to make a list of tools to process pcap files in research of network
|
||||
traffic. For more awesome lists, see
|
||||
https://github.com/sindresorhus/awesome</p>
|
||||
<p><strong>License</strong>: Apache License v2.</p>
|
||||
<p><strong>License</strong>: CC0 1.0 Universal (CC0 1.0).</p>
|
||||
<blockquote>
|
||||
<ul>
|
||||
<li><a href="#linuxcmds">Linux commands</a></li>
|
||||
<li><a href="#capture">Traffic Capture</a></li>
|
||||
<li><a href="#wrapper">Wrapper Libraries for libpcap/WinPcap</a></li>
|
||||
<li><a href="#analysis">Traffic Analysis/Inspection</a></li>
|
||||
<li><a href="#dnstools">DNS Utilities</a></li>
|
||||
<li><a href="#fileextraction">File Extraction</a></li>
|
||||
@@ -27,30 +23,32 @@ https://github.com/sindresorhus/awesome</p>
|
||||
nload that shows the traffic load over all the network interfaces on the
|
||||
system. The output also consists of a graph and a section with packet
|
||||
level details. <a
|
||||
href="http://www.binarytides.com/blog/wp-content/uploads/2014/03%20/bmon-%20640x480.png">Screenshot</a></p></li>
|
||||
href="https://www.binarytides.com/blog/wp-content/uploads/2014/03/bmon-640x480.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Bwm-ng</strong>: (Bandwidth Monitor Next Generation) is
|
||||
another very simple real time network load monitor that reports a
|
||||
summary of the speed at which data is being transferred in and out of
|
||||
all available network interfaces on the system. <a
|
||||
href="">Screenshot</a></p></li>
|
||||
href="https://a.fsdn.com/con/app/proj/bwmng/screenshots/10965.jpg/245/183/1">Screenshot</a></p></li>
|
||||
<li><p><strong>CBM</strong>: (Color Bandwidth Meter) A tiny little
|
||||
simple bandwidth monitor that displays the traffic volume through
|
||||
network interfaces. No further options, just the traffic stats are
|
||||
display and updated in realtime. <a
|
||||
href="http://www.binarytides.com/blog%20/wp-content/uploads/2014/03/cbm.png">Screenshot</a></p></li>
|
||||
href="https://www.binarytides.com/blog/wp-content/uploads/2014/03/cbm.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Collectl</strong>: reports system statistics in a style
|
||||
that is similar to dstat, and like dstat it is gathers statistics about
|
||||
that is similar to dstat, and like dstat it gathers statistics about
|
||||
various different system resources like cpu, memory, network etc. Over
|
||||
here is a simple example of how to use it to report network
|
||||
usage/bandwidth. <a href="">Screenshot</a></p></li>
|
||||
usage/bandwidth. <a
|
||||
href="https://www.cse.wustl.edu/~jain/cse567-08/ftp/hw/collectl.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Dstat</strong>: is a versatile tool (written in python)
|
||||
that can monitor different system statistics and report them in a batch
|
||||
style mode or log the data to a csv or similar file. This example shows
|
||||
how to use dstat to report network bandwidth <a
|
||||
href="">Screenshot</a></p></li>
|
||||
href="https://www.tecmint.com/wp-content/uploads/2016/09/Dstat-Linux-Monitoring.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Ifstat</strong>: reports the network bandwidth in a batch
|
||||
style mode. The output is in a format that is easy to log and parse
|
||||
using other programs or utilities. <a href="">Screenshot</a></p></li>
|
||||
using other programs or utilities. <a
|
||||
href="https://community.linuxmint.com/img/screenshots/ifstat.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Iftop</strong>: measures the data flowing through
|
||||
individual socket connections, and it works in a manner that is
|
||||
different from Nload. Iftop uses the pcap library to capture the packets
|
||||
@@ -61,79 +59,84 @@ name/id involved in the particular socket connection. But being based on
|
||||
the pcap library, iftop is able to filter the traffic and report
|
||||
bandwidth usage over selected host connections as specified by the
|
||||
filter. <a
|
||||
href="http://www.binarytides.com/blog/wp-content/uploads/2014/03/iftop.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Iptraf</strong>: is an interactive and colorful IP Lan
|
||||
href="https://www.binarytides.com/blog/wp-content/uploads/2014/03/iftop.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Iptraf-ng</strong>: is an interactive and colorful IP Lan
|
||||
monitor. It shows individual connections and the amount of data flowing
|
||||
between the hosts. <a
|
||||
href="http://www.binarytides.com/blog/wp-content/uploads/2014/03/iptraf.png">Screenshot</a></p></li>
|
||||
between the hosts. A maintained fork of the defunct iptraf. <a
|
||||
href="https://wiki.ipfire.org/addons/iptraf-ng/iptraf-ng_monitor.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Jnettop</strong>: <a
|
||||
href="http://jnettop.kubs.info/wiki/">Jnettop</a> is a traffic
|
||||
visualiser, which captures traffic going through the host it is running
|
||||
from and displays streams sorted by bandwidth they use. <a
|
||||
href="http://jnettop.kubs.info/wiki/?binary=internal%3A%2F%2F76195466cc3bca92f8de7b404e240844.gif">Screenshot</a></p></li>
|
||||
href="https://sourceforge.net/projects/jnettop/">Jnettop</a> is a
|
||||
traffic visualiser, which captures traffic going through the host it is
|
||||
running from and displays streams sorted by bandwidth they use. <a
|
||||
href="https://web.archive.org/web/20130509072433if_/http://jnettop.kubs.info/wiki/?binary=internal%3A%2F%2F76195466cc3bca92f8de7b404e240844.gif">Screenshot</a></p></li>
|
||||
<li><p><strong>Nethogs</strong>: is a small ‘net top’ tool that shows
|
||||
the bandwidth used by individual processes and sorts the list putting
|
||||
the most intensive processes on top. In the event of a sudden bandwidth
|
||||
spike, quickly open nethogs and find the process responsible. Nethogs
|
||||
reports the PID, user and the path of the program. <a
|
||||
href="http://www.binarytides.com/blog/wp-content/uploads/2014/03/nethogs.png">Screenshot</a></p></li>
|
||||
href="https://www.binarytides.com/blog/wp-content/uploads/2014/03/nethogs.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Netload</strong>: displays a small report on the current
|
||||
traffic load, and the total number of bytes transferred since the
|
||||
program start. No more features are there. Its part of the netdiag. <a
|
||||
href="http://www.binarytides.com/blog/wp-content/uploads/2014/03/netload.png">Screenshot</a></p></li>
|
||||
href="https://www.binarytides.com/blog/wp-content/uploads/2014/03/netload.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Netwatch</strong>: is part of the netdiag collection of
|
||||
tools, and it too displays the connections between local host and other
|
||||
remote hosts, and the speed at which data is transferring on each
|
||||
connection. <a
|
||||
href="http://www.binarytides.com/blog/wp-content/uploads/2014/03/netwatch.png">Screenshot</a></p></li>
|
||||
href="https://www.binarytides.com/blog/wp-content/uploads/2014/03/netwatch.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Nload</strong>: is a commandline tool that allows users
|
||||
to monitor the incoming and outgoing traffic separately. It also draws
|
||||
outa graph to indicate the same, the scale of which can be adjusted.
|
||||
Easy and simple to use, and does not support many options. <a
|
||||
href="http://www.binarytides.com/blog/wp-content/uploads/2014/03/nload.png">Screenshot</a></p></li>
|
||||
href="https://www.binarytides.com/blog/wp-content/uploads/2014/03/nload.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Pktstat</strong>: displays all the active connections in
|
||||
real time, and the speed at which data is being transferred through
|
||||
them. It also displays the type of the connection, i.e. tcp or udp and
|
||||
also details about http requests if involved. <a
|
||||
href="http://www.binarytides.com/blog/wp-content/uploads/2014/03/pktstat.png">Screenshot</a></p></li>
|
||||
href="https://www.binarytides.com/blog/wp-content/uploads/2014/03/pktstat.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Slurm</strong>: is ‘yet’ another network load monitor
|
||||
that shows device statistics along with an ascii graph. It supports 3
|
||||
different styles of graphs each of which can be activated using the c, s
|
||||
and l keys. Simple in features, slurm does not display any further
|
||||
details about the network load. <a
|
||||
href="http://www.binarytides.com/blog/wp-content/uploads/2014/03/slurm.png">Screenshot</a></p></li>
|
||||
href="https://www.binarytides.com/blog/wp-content/uploads/2014/03/slurm.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Speedometer</strong>: Another small and simple tool that
|
||||
just draws out good looking graphs of incoming and outgoing traffic
|
||||
through a given interface. <a
|
||||
href="http://www.binarytides.com/blog/wp-content/uploads/2014/03/speedometer.png">Screenshot</a></p></li>
|
||||
href="https://www.binarytides.com/blog/wp-content/uploads/2014/03/speedometer.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Tcptrack</strong>: is similar to iftop, and uses the pcap
|
||||
library to capture packets and calculate various statistics like the
|
||||
bandwidth used in each connection. It also supports the standard pcap
|
||||
filters that can be used to monitor specific connections. <a
|
||||
href="http://www.binarytides.com/blog%20/wp-content/uploads/2014/03/tcptrack.png">Screenshot</a></p></li>
|
||||
href="https://www.binarytides.com/blog/wp-content/uploads/2014/03/tcptrack.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Trafshow</strong>: reports the current active
|
||||
connections, their protocol and the data transfer speed on each
|
||||
connection. It can filter out connections using pcap type filters. <a
|
||||
href="http://www.binarytides.com/blog/wp-content/uploads/2014/03/trafshow.png">Screenshot</a></p></li>
|
||||
href="https://www.binarytides.com/blog/wp-content/uploads/2014/03/trafshow.png">Screenshot</a></p></li>
|
||||
<li><p><strong>Vnstat</strong>: is bit different from most of the other
|
||||
tools. It actually runs a background service/daemon and keeps recording
|
||||
the size of data transfer all the time. Next it can be used to generate
|
||||
a report of the history of network usage. <a
|
||||
href="">Screenshot</a></p></li>
|
||||
href="https://www.howtoforge.com/images/vnstat/big/vnstat9.png">Screenshot</a></p></li>
|
||||
</ul>
|
||||
<h2 id="traffic-capture">Traffic Capture<a name="capture"></a></h2>
|
||||
<ul>
|
||||
<li><p><a href="http://www.tcpdump.org/">Libpcap/Tcpdump</a>: The
|
||||
<li><p><a href="https://www.tcpdump.org/">Libpcap/Tcpdump</a>: The
|
||||
official site of tcpdump, a powerful command-line packet analyzer; and
|
||||
libpcap, a portable C/C++ library for network traffic capture.</p></li>
|
||||
<li><p><a href="http://ngrep.sourceforge.net/">Ngrep</a>: strives to
|
||||
<li><p><a href="https://github.com/deepfence/PacketStreamer">Deepfence
|
||||
PacketStreamer</a>: High-performance remote packet capture and
|
||||
collection tool, distributed tcpdump for cloud native
|
||||
environments.</p></li>
|
||||
<li><p><a href="https://github.com/jpr5/ngrep/">Ngrep</a>: strives to
|
||||
provide most of GNU grep’s common features, applying them to the network
|
||||
layer. ngrep is a pcap-aware tool that will allow you to specify
|
||||
extended regular or hexadecimal expressions to match against data
|
||||
payloads of packets. It currently recognizes TCP, UDP and ICMP across
|
||||
Ethernet, PPP, SLIP, FDDI, Token Ring and null interfaces, and
|
||||
understands bpf filter logic in the same fashion as more common packet
|
||||
sniffing tools, such as tcpdump and snoop.</p></li>
|
||||
sniffing tools, such as tcpdump and snoop. <a
|
||||
href="https://www.cyberciti.biz/media/new/cms/2012/12/ngrep.png">Screenshot</a></p></li>
|
||||
<li><p><a
|
||||
href="https://github.com/ruedigergad/clj-net-pcap">clj-net-pcap</a>:
|
||||
<code>clj-net-pcap</code> is a packet capturing library for Clojure.
|
||||
@@ -141,30 +144,47 @@ clj-net-pcap uses jNetPcap and adds convenience functionality around
|
||||
jNetPcap for easing the usability. A <a
|
||||
href="http://ieeexplore.ieee.org/xpl/articleDetails.jsp?tp=&arnumber=6903107">paper
|
||||
on clj-net-pcap</a> was published in scope of COMPSACW 2014.</p></li>
|
||||
<li><p><a href="http://jnetpcap.com">jNetPcap</a>: jNetPcap is a packet
|
||||
capturing library for Java that is available for Linux and Windows.
|
||||
jNetPcap leverages libpcap respectively WinPcap and employs the Java
|
||||
Native Interface (JNI) for using the functionality provided by
|
||||
<li><p><a
|
||||
href="https://sourceforge.net/projects/jnetpcap/">jNetPcap</a>: jNetPcap
|
||||
is a packet capturing library for Java that is available for Linux and
|
||||
Windows. jNetPcap leverages libpcap respectively WinPcap and employs the
|
||||
Java Native Interface (JNI) for using the functionality provided by
|
||||
libpcap/WinPcap.</p></li>
|
||||
<li><p><a href="http://www.ntop.org/products/n2disk/">n2disk</a>
|
||||
<li><p><a href="https://arkime.com/">Arkime</a> Arkime (formerly Moloch)
|
||||
is a large scale, open source, indexed packet capture and search
|
||||
tool.</p></li>
|
||||
<li><p><a
|
||||
href="https://www.ntop.org/products/traffic-recording-replay/n2disk/">n2disk</a>
|
||||
(Commercial): A multi-Gigabit network traffic recorder with indexing
|
||||
capabilities. n2disk is a network traffic recorder application. With
|
||||
n2disk you can capture full- sized network packets at multi-Gigabit rate
|
||||
(above 10 Gigabit/s on adequate hardware) from a live network interface,
|
||||
and write them into files without any packet loss.</p></li>
|
||||
<li><p><a href="http://www.openfpc.org/">OpenFPC</a>: OpenFPC is a set
|
||||
of scripts that combine to provide a lightweight full-packet network
|
||||
traffic recorder & buffering tool. Its design goal is to allow
|
||||
non-expert users to deploy a distributed network traffic recorder on
|
||||
COTS hardware while integrating into existing alert and log
|
||||
tools.</p></li>
|
||||
<li><p><a href="http://www.ntop.org/products/pf_ring/">PF_RING</a>:
|
||||
<li><p><a href="https://github.com/Netis/packet-agent">Netis Packet
|
||||
Agent</a>: It is a remote data capture utility through GRE tunnel, which
|
||||
makes you easily capture packets from an NIC interface, encapsulate them
|
||||
with GRE and send them to a remote machine for monitoring and
|
||||
analysis.</p></li>
|
||||
<li><p><a href="https://github.com/leonward/OpenFPC">OpenFPC</a>:
|
||||
OpenFPC is a set of scripts that combine to provide a lightweight
|
||||
full-packet network traffic recorder & buffering tool. Its design
|
||||
goal is to allow non-expert users to deploy a distributed network
|
||||
traffic recorder on COTS hardware while integrating into existing alert
|
||||
and log tools.</p></li>
|
||||
<li><p><a href="https://github.com/emanuele-f/PCAPdroid">PCAPdroid</a>:
|
||||
PCAPdroid is an Android app which lets you monitor and export the
|
||||
network traffic of your device without root. Traffic can be dumped in
|
||||
the PCAP format to be analyzed with popular tools like Wireshark, even
|
||||
in real time. The built-in traffic monitor lets you detect suspicious
|
||||
connections made by user and system apps.</p></li>
|
||||
<li><p><a
|
||||
href="https://www.ntop.org/products/packet-capture/pf_ring/">PF_RING</a>:
|
||||
PF_RING is a new type of network socket that dramatically improves the
|
||||
packet capture speed. Available for Linux kernels 2.6.32 and newer. No
|
||||
need to patch the kernel. PF_RING-aware drivers for increased packet
|
||||
capture acceleration.</p></li>
|
||||
<li><p><a
|
||||
href="http://www.csl.sony.co.jp/person/kjc/kjc/software.html#ttt">TTT</a>:
|
||||
href="https://www2.sonycsl.co.jp/person/kjc/kjc/software.html#ttt">TTT</a>:
|
||||
(Tele Traffic Tapper) is yet another descendant of tcpdump but it is
|
||||
capable of real-time, graphical, and remote traffic-monitoring. ttt
|
||||
won’t replace tcpdump, rather, it helps you find out what to look into
|
||||
@@ -176,113 +196,27 @@ a reliable piece of software, quite solid and able to generate flow
|
||||
records from pcap. This is very nice for indexing huge pcap or even
|
||||
doing packet capture. The recent version can even extract payloads and
|
||||
put in the flow records.</p></li>
|
||||
</ul>
|
||||
<h2 id="wrapper-libraries-for-libpcapwinpcap">Wrapper Libraries for
|
||||
libpcap/WinPcap<a name="wrapper"></a></h2>
|
||||
<ul>
|
||||
<li>C++
|
||||
<ul>
|
||||
<li><a href="https://github.com/mfontanini/libtins">libtins</a>: libtins
|
||||
is a high-level, multiplatform C++ network packet sniffing and crafting
|
||||
library.</li>
|
||||
<li><a href="https://github.com/pellegre/libcrafter">libcrafter</a>: A
|
||||
high level C++ network packet sniffing and crafting library.</li>
|
||||
</ul></li>
|
||||
<li>C#
|
||||
<ul>
|
||||
<li><a href="https://github.com/chmorgan/sharppcap">sharppcap</a>: Fully
|
||||
managed, cross platform (Windows, Mac, Linux) .NET library for capturing
|
||||
packets</li>
|
||||
<li><a href="https://github.com/PcapDotNet/Pcap.Net">Pcap.Net</a>: .NET
|
||||
wrapper for WinPcap written in C++/CLI and C#, which features almost all
|
||||
WinPcap features’ and includes a packet interpretation framework.<br />
|
||||
</li>
|
||||
</ul></li>
|
||||
<li>Go
|
||||
<ul>
|
||||
<li><a href="https://github.com/akrennmair/gopcap">Gopcap</a>: A simple
|
||||
wrapper around libpcap for the Go programming language</li>
|
||||
<li><a href="https://github.com/google/gopacket">GoPacket</a>: Provides
|
||||
packet processing capabilities for Go by google. Originally forked from
|
||||
the gopcap project written by Andreas Krennmair</li>
|
||||
</ul></li>
|
||||
<li>Haskell
|
||||
<ul>
|
||||
<li><a href="http://hackage.haskell.org/package/pcap">pcap</a>: A
|
||||
system-independent interface for user-level packet capture<br />
|
||||
</li>
|
||||
</ul></li>
|
||||
<li>Java
|
||||
<ul>
|
||||
<li><a href="http://jpcap.sourceforge.net/">jpcap</a>: a network packet
|
||||
capture library for applications written in Java.</li>
|
||||
<li><a href="http://jnetpcap.com/">JNetPcap</a>: A Java wrapper for
|
||||
nearly all libpcap library native calls</li>
|
||||
<li><a href="https://github.com/kaitoy/pcap4j">pcap4j</a>: A Java
|
||||
library for capturing, crafting, and sending packets.</li>
|
||||
</ul></li>
|
||||
<li>Perl
|
||||
<ul>
|
||||
<li><a
|
||||
href="http://search.cpan.org/~saper/Net-Pcap/Pcap.pm">Net::Pcap</a>:
|
||||
Interface to pcap(3) LBL packet capture library<br />
|
||||
</li>
|
||||
</ul></li>
|
||||
<li>Python
|
||||
<ul>
|
||||
<li><a href="https://github.com/secdev/scapy">Scapy</a> - Python-based
|
||||
interactive packet manipulation program & library</li>
|
||||
<li><a href="https://github.com/phaethon/scapy">Scapy for Pythong3</a> -
|
||||
Network packet and pcap file
|
||||
crafting/sniffing/manipulation/visualization security tool (based on
|
||||
scapy) with python3 compatibility</li>
|
||||
<li><a href="https://github.com/CoreSecurity/pcapy">Pcapy</a>: Pcapy is
|
||||
a Python extension module that interfaces with the libpcap packet
|
||||
capture library.</li>
|
||||
<li><a
|
||||
href="http://sourceforge.net/projects/pylibpcap/">python-libpcap</a>:
|
||||
Python module for the libpcap packet capture library, based on the
|
||||
original python libpcap module by Aaron Rhodes.</li>
|
||||
<li><a href="https://github.com/dugsong/pypcap">pypcap</a>: a simplified
|
||||
object-oriented Python wrapper for libpcap - the current tcpdump.org
|
||||
version, and the WinPcap port for Windows.</li>
|
||||
<li><a href="https://github.com/kbandla/dpkt">dpkt</a>: fast, simple
|
||||
packet creation / parsing, with definitions for the basic TCP/IP
|
||||
protocols<br />
|
||||
</li>
|
||||
</ul></li>
|
||||
<li>Ruby
|
||||
<ul>
|
||||
<li><a href="https://github.com/pcaprub/pcaprub">pcaprub</a>: libpcap
|
||||
bindings for ruby</li>
|
||||
<li><a href="https://github.com/ahobson/ruby-pcap">ruby-pcap</a>:
|
||||
ruby-pcap is a ruby extension to LBL libpcap (Packet Capture
|
||||
library)</li>
|
||||
<li><a href="https://github.com/packetfu/packetfu">PacketFu</a>: a
|
||||
mid-level packet manipulation library for Ruby for reading and writing
|
||||
packets to an interface or to a libpcap-formatted file.</li>
|
||||
<li><a href="https://github.com/trema/pio">pio</a>: Pio is a ruby gem to
|
||||
easily parse (including pcap files) and generate network packets.<br />
|
||||
</li>
|
||||
</ul></li>
|
||||
<li>Rust
|
||||
<ul>
|
||||
<li><a href="https://github.com/ebfull/pcap">pcap</a>: Rust language
|
||||
pcap library.<br />
|
||||
</li>
|
||||
</ul></li>
|
||||
<li>Tcl
|
||||
<ul>
|
||||
<li><a href="http://tclpcap.sourceforge.net/">Tclpcap</a>: tclpcap is a
|
||||
Tcl extension that provides access to the Pcap packet capture
|
||||
library.</li>
|
||||
<li><a href="http://monkey.org/~jose/software/tcap/">Tcap</a>: Tcl pcap
|
||||
interface</li>
|
||||
</ul></li>
|
||||
<li><p><a href="https://github.com/dotpcap/sharppcap">sharppcap</a>:
|
||||
Fully managed, cross platform (Windows, Mac, Linux) .NET library for
|
||||
capturing packets from live and file based devices. A realiable and
|
||||
robust wrapper of libpcap and npcap.</p></li>
|
||||
</ul>
|
||||
<h2 id="traffic-analysisinspection">Traffic
|
||||
Analysis/Inspection<a name="analysis"></a></h2>
|
||||
<ul>
|
||||
<li><p><a href="https://www.brimsecurity.com/">Brim</a>: Brim blends
|
||||
together the richness of Zeek logs with the details of packets. It’s the
|
||||
best of both worlds. While Zeek logs can answer most all of your
|
||||
questions quickly, you still have fast access to packets when you need
|
||||
to drill down into the details. Wireshark is always just a click
|
||||
away.</p></li>
|
||||
<li><p><a
|
||||
href="https://github.com/odedshimon/BruteShark">BruteShark</a>: Is an
|
||||
open-source, cross-platform network forensic analysis tool with many
|
||||
features. It includes: password extracting, displaying a visual network
|
||||
map, reconstruct TCP sessions, extract hashes of encrypted passwords and
|
||||
even convert them to a Hashcat format in order to perform an offline
|
||||
Brute Force attack.</p></li>
|
||||
<li><p><a href="https://bitbucket.org/camp0/aiengine">AIEngine</a>: is a
|
||||
next generation interactive/programmable packet inspection engine with
|
||||
capabilities of learning without any human intervention, NIDS
|
||||
@@ -290,40 +224,38 @@ functionality, DNS domain classification, network collector and many
|
||||
others. AIEngine also helps network/security professionals to identify
|
||||
traffic and develop signatures for use them on NIDS, Firewalls, Traffic
|
||||
classifiers and so on.</p></li>
|
||||
<li><p><a href="http://bro-ids.org/">Bro</a>: is an open-source,
|
||||
Unix-based Network Intrusion Detection System (NIDS) that passively
|
||||
monitors network traffic and looks for suspicious activity. Bro detects
|
||||
intrusions by first parsing network traffic to extract its application-
|
||||
level semantics and then executing event-oriented analyzers that compare
|
||||
the activity with patterns deemed troublesome. Its analysis includes
|
||||
detection of specific attacks (including those defined by signatures,
|
||||
but also those defined in terms of events) and unusual activities (e.g.,
|
||||
certain hosts connecting to certain services, or patterns of failed
|
||||
connection attempts).</p></li>
|
||||
<li><p><a href="https://github.com/MITRECND/chopshop">Chopshop</a> is a
|
||||
<li><p><a href="http://www.capanalysis.net/ca/">CapAnalysis</a> -
|
||||
CapAnalysis is a web visual tool for information security specialists,
|
||||
system administrators and everyone who needs to analyze large amounts of
|
||||
captured network traffic. A live web demo is <a
|
||||
href="http://pcap.capanalysis.net/">available</a> for testing.</p></li>
|
||||
<li><p><a href="https://github.com/omriher/CapTipper">CapTipper</a>:
|
||||
Malicious HTTP traffic explorer</p></li>
|
||||
<li><p><a href="https://github.com/MITRECND/chopshop">Chopshop</a>: is a
|
||||
MITRE developed framework to aid analysts in the creation and execution
|
||||
of pynids based decoders and detectors of APT tradecraft.</p></li>
|
||||
<li><p><a
|
||||
href="http://www.caida.org/tools/measurement/coralreef/">CoralReef</a>:
|
||||
href="https://www.caida.org/tools/measurement/coralreef/">CoralReef</a>:
|
||||
is a software suite developed by CAIDA to analyze data collected by
|
||||
passive Internet traffic monitors. It provides a programming library
|
||||
libcoral, similar to libpcap with extensions for ATM and other network
|
||||
types, which is available from both C and Perl.</p></li>
|
||||
<li><p><a href="http://dpdk.org/">DPDK</a>: is a set of libraries and
|
||||
drivers for fast packet processing. It was designed to run on any
|
||||
<li><p><a href="https://www.dpdk.org/">DPDK</a>: is a set of libraries
|
||||
and drivers for fast packet processing. It was designed to run on any
|
||||
processors. The first supported CPU was Intel x86 and it is now extended
|
||||
to IBM Power 8, EZchip TILE-Gx and ARM. It runs mostly in Linux
|
||||
userland. A FreeBSD port is available for a subset of DPDK
|
||||
features.</p></li>
|
||||
<li><p><a href="http://code.google.com/p/dpkt/">DPKT</a>: Python packet
|
||||
<li><p><a href="https://github.com/kbandla/dpkt">DPKT</a>: Python packet
|
||||
creation/parsing library.</p></li>
|
||||
<li><p><a href="https://bitbucket.org/nathanj/ecap/wiki">ECap</a>:
|
||||
<li><p><a
|
||||
href="https://web.archive.org/web/20170715080351/https://bitbucket.org/nathanj/ecap/wiki/Home">ECap</a>:
|
||||
(External Capture) is a distributed network sniffer with a web front-
|
||||
end. Ecap was written many years ago in 2005, but a post on the
|
||||
tcpdump-workers mailing list requested a similar application… so here it
|
||||
is. It would be fun to update it and work on it again if there’s any
|
||||
interest.</p></li>
|
||||
<li><p><a href="http://etherape.sourceforge.net/">EtherApe</a>: is a
|
||||
<li><p><a href="https://etherape.sourceforge.io/">EtherApe</a>: is a
|
||||
graphical network monitor for Unix modeled after etherman. Featuring
|
||||
link layer, ip and TCP modes, it displays network activity graphically.
|
||||
Hosts and links change in size with traffic. Color coded protocols
|
||||
@@ -335,8 +267,7 @@ href="https://github.com/caesar0301/http-sniffer">HttpSniffer</a>: A
|
||||
multi-threading tool to sniff TCP flow statistics and embedded HTTP
|
||||
headers from PCAP file. Each TCP flow carrying HTTP is exported to text
|
||||
file in JSON format.</p></li>
|
||||
<li><p><a
|
||||
href="http://www.read.seas.harvard.edu/~kohler/ipsumdump/">Ipsumdump</a>:
|
||||
<li><p><a href="https://github.com/kohler/ipsumdump">Ipsumdump</a>:
|
||||
summarizes TCP/IP dump files into a self-describing ASCII format easily
|
||||
readable by humans and programs. Ipsumdump can read packets from network
|
||||
interfaces, from tcpdump files, and from existing ipsumdump files. It
|
||||
@@ -344,22 +275,28 @@ will transparently uncompress tcpdump or ipsumdump files when necessary.
|
||||
It can randomly sample traffic, filter traffic based on its contents,
|
||||
anonymize IP addresses, and sort packets from multiple dumps by
|
||||
timestamp. Also, it can optionally create a tcpdump file containing
|
||||
actual packet data. It’s also convinient to work with CLICK as a
|
||||
actual packet data. It’s also convenient to work with CLICK as a
|
||||
inserted module.</p></li>
|
||||
<li><p><a href="http://ita.ee.lbl.gov/">ITA</a>: The Internet Traffic
|
||||
Archive is a moderated repository to support widespread access to traces
|
||||
of Internet network traffic, sponsored by ACM SIGCOMM. The traces can be
|
||||
used to study network dynamics, usage characteristics, and growth
|
||||
patterns, as well as providing the grist for trace- driven simulations.
|
||||
The archive is also open to programs for reducing raw trace data to more
|
||||
manageable forms, for generating synthetic traces, and for analyzing
|
||||
traces.</p></li>
|
||||
<li><p><a href="http://code.google.com/p/libcrafter/">Libcrafter</a>: is
|
||||
a high level library for C++ designed to make easier the creation and
|
||||
<li><p><a
|
||||
href="https://web.archive.org/web/20181016104652/http://ita.ee.lbl.gov/html/traces.html">ITA</a>:
|
||||
The Internet Traffic Archive is a moderated repository to support
|
||||
widespread access to traces of Internet network traffic, sponsored by
|
||||
ACM SIGCOMM. The traces can be used to study network dynamics, usage
|
||||
characteristics, and growth patterns, as well as providing the grist for
|
||||
trace- driven simulations. The archive is also open to programs for
|
||||
reducing raw trace data to more manageable forms, for generating
|
||||
synthetic traces, and for analyzing traces.</p></li>
|
||||
<li><p><a href="https://github.com/cisco/joy">Joy</a>: joy is a traffic
|
||||
analysis and parsing tool that was developed. In part to assist in
|
||||
classifying encrypted traffic streams, such as HTTPS traffic. It is able
|
||||
to parse pcap files into usable json files that contain details on the
|
||||
capture statistics and features.</p></li>
|
||||
<li><p><a href="https://github.com/pellegre/libcrafter">Libcrafter</a>:
|
||||
is a high level library for C++ designed to make easier the creation and
|
||||
decoding of network packets. It is able to craft or decode packets of
|
||||
most common network protocols, send them on the wire, capture them and
|
||||
match requests and replies.</p></li>
|
||||
<li><p><a href="http://libnet.sourceforge.net/">Libnet</a>: is a
|
||||
<li><p><a href="https://github.com/libnet/libnet">Libnet</a>: is a
|
||||
collection of routines to help with the construction and handling of
|
||||
network packets. It provides a portable framework for low-level network
|
||||
packet shaping, handling and injection. Libnet features portable packet
|
||||
@@ -374,18 +311,18 @@ Libnids offers IP defragmentation, TCP stream assembly and TCP port scan
|
||||
detection. The most valuable feature of libnids is reliability. A number
|
||||
of tests were conducted, which proved that libnids predicts behaviour of
|
||||
protected Linux hosts as closely as possible.</p></li>
|
||||
<li><p><a href="http://netsniff-ng.org/">Multitail</a>: now has a
|
||||
colorscheme included for monitoring the tcpdump output. It can also
|
||||
filter, convert timestamps to timestrings and much more.
|
||||
http://www.vanheusden.com/multitail]: * Netsniff-ng]: Netsniff-ng is a
|
||||
toolkit of free Linux networking utilities, a Swiss army knife for your
|
||||
daily Linux network plumbing if you will. <a
|
||||
href="www.github.com/borkmann/netsniff-ng">GitHub</a>.</p></li>
|
||||
<li><p><a href="https://www.vanheusden.com/multitail/">Multitail</a>:
|
||||
now has a colorscheme included for monitoring the tcpdump output. It can
|
||||
also filter, convert timestamps to timestrings and much more.</p></li>
|
||||
<li><p><a
|
||||
href="https://www.github.com/borkmann/netsniff-ng">Netsniff-ng</a>:
|
||||
Netsniff-ng is a toolkit of free Linux networking utilities, a Swiss
|
||||
army knife for your daily Linux network plumbing if you will.</p></li>
|
||||
<li><p><a href="http://netdude.sourceforge.net/">NetDude</a>: (NETwork
|
||||
DUmp data Displayer and Editor). From their webpage, “it is a GUI-based
|
||||
tool that allows you to make detailed changes to packets in tcpdump
|
||||
tracefiles.”</p></li>
|
||||
<li><p><a href="http://www.netexpect.org/">Network Expect</a>: is a
|
||||
<li><p><a href="https://www.netexpect.org/">Network Expect</a>: is a
|
||||
framework that allows to easily build tools that can interact with
|
||||
network traffic. Following a script, traffic can be injected into the
|
||||
network, and decisions can be taken, and acted upon, based on received
|
||||
@@ -394,20 +331,61 @@ high-level control structures to direct the interaction with the
|
||||
network. Network Expect uses libpcap for packet capture and libwireshark
|
||||
(from the Wireshark project) for packet dissection tasks. (GPL,
|
||||
BSD/Linux/OSX).</p></li>
|
||||
<li><p><a href="https://github.com/nfstream/nfstream">NFStream</a>: is a
|
||||
Python framework providing fast, flexible, and expressive data
|
||||
structures designed to make working with online or offline network data
|
||||
both easy and intuitive. It aims to be the fundamental high-level
|
||||
building block for doing practical, real world network data analysis in
|
||||
Python. Additionally, it has the broader goal of becoming a common
|
||||
network data analytics framework for researchers providing data
|
||||
reproducibility across experiments.</p></li>
|
||||
<li><p><a href="http://www.ntop.org/">Ntop</a>: Ntop is a network
|
||||
traffic probe that shows the network usage, similar to what the popular
|
||||
top Unix command does. ntop is based on libpcap and it has been written
|
||||
in a portable way in order to virtually run on every Unix platform and
|
||||
on Win32 as well.</p></li>
|
||||
<li><p><a href="http://www.ntop.org/products/ntop/">Ntopng</a>: Ntopng
|
||||
is the next generation version of the original ntop, a network traffic
|
||||
probe that shows the network usage, similar to what the popular top Unix
|
||||
command does. ntop is based on libpcap and it has been written in a
|
||||
portable way in order to virtually run on every Unix platform, MacOSX
|
||||
and on Win32 as well.</p></li>
|
||||
<li><p><a
|
||||
href="https://www.ntop.org/products/traffic-analysis/ntop/">Ntopng</a>:
|
||||
Ntopng is the next generation version of the original ntop, a network
|
||||
traffic probe that shows the network usage, similar to what the popular
|
||||
top Unix command does. ntop is based on libpcap and it has been written
|
||||
in a portable way in order to virtually run on every Unix platform,
|
||||
MacOSX and on Win32 as well.</p></li>
|
||||
<li><p><a href="https://ostinato.org/">Ostinato</a>: Ostinato is a
|
||||
versatile packet crafter, pcap editor/player and traffic generator with
|
||||
an intuitive GUI. Add-ons include high-speed 10/25/40G traffic
|
||||
generation and scripting/ automation Python APIs. Works on all platforms
|
||||
- Windows, MacOS, Linux and the labbing platforms - CML, EVE-NG and
|
||||
GNS3.</p></li>
|
||||
<li><p><a href="https://github.com/ddddddO/packemon">packemon</a>:
|
||||
Packet monster (っ‘-’)╮=͟͟͞͞◒ ヽ( ’-’ヽ) TUI tool for sending packets of
|
||||
arbitrary input and monitoring packets on any network interfaces
|
||||
(default: eth0).</p></li>
|
||||
<li><p><a href="https://github.com/dotse/PacketQ">PacketQ</a>: A tool
|
||||
that provides a basic SQL-frontend to PCAP-files. Outputs JSON, CSV and
|
||||
XML and includes a build-in webserver with JSON-api and a nice looking
|
||||
AJAX GUI.</p></li>
|
||||
<li><p><a href="https://github.com/andrewf/pcap2har">Pcap2har</a>: A
|
||||
program to convert .pcap network capture files to HTTP Archive files
|
||||
using library dpkt.</p></li>
|
||||
<li><p><a
|
||||
href="https://github.com/seladb/PcapPlusPlus">PcapPlusPlus</a>:
|
||||
PcapPlusPlus a multiplatform C++ network sniffing and packet parsing and
|
||||
manipulation framework. It’s meant to be lightweight, efficient and easy
|
||||
to use. It’s a C++ wrapper for popular engines like libpcap, WinPcap,
|
||||
DPDK and PF_RING. It also contains parsing and edit capabilities for
|
||||
many protocols including Ethernet, IPv4, IPv6, ARP, VLAN, MPLS, PPPoE,
|
||||
GRE, TCP, UDP, ICMP, DNS as well as layer 7 protocols like HTTP and
|
||||
SSL/TLS</p></li>
|
||||
<li><p><a
|
||||
href="https://github.com/nokia/pcaptoparquet">pcaptoparquet</a>:
|
||||
pcaptoparquet is a Python package designed for converting PCAP or PCAPNG
|
||||
files to structured data formats, primarily Apache Parquet. The tool
|
||||
focuses on network traffic analysis by extracting, decoding, and
|
||||
transforming packet data into queryable datasets suitable for analysis
|
||||
and visualization. The tool supports both command-line and programmatic
|
||||
interfaces, enabling integration into various network analysis
|
||||
workflows.</p></li>
|
||||
<li><p><a href="https://github.com/caesar0301/pkt2flow">pkt2flow</a>: A
|
||||
simple utility to classify packets into flows. It’s so simple that only
|
||||
one task is aimed to finish. For Deep Packet Inspection or flow
|
||||
@@ -417,14 +395,16 @@ tcpslice, tcpsplit, but all these tools try to either decrease the trace
|
||||
volume (under requirement) or resemble the packets into flow payloads
|
||||
(over requirement). I have not found a simple tool to classify the
|
||||
packets into flows without further processing.</p></li>
|
||||
<li><p><a href="http://kiminewt.github.io/pyshark/">pyshark</a>: A
|
||||
<li><p><a href="https://github.com/CIRCL/potiron">potiron</a>:
|
||||
Normalizes, indexes, enriches and visualizes network captures.</p></li>
|
||||
<li><p><a href="https://kiminewt.github.io/pyshark/">pyshark</a>: A
|
||||
Python wrapper for tshark, allowing python packet parsing using
|
||||
wireshark dissectors. There are quite a few python packet parsing
|
||||
modules, this one is different because it doesn’t actually parse any
|
||||
packets, it simply uses tshark’s (wireshark command-line utility)
|
||||
ability to export XMLs to use its parsing.</p></li>
|
||||
<li><p><a
|
||||
href="http://ita.ee.lbl.gov/html/contrib/sanitize.html">Sanitize</a>:
|
||||
href="https://web.archive.org/web/20190210101529/http://ita.ee.lbl.gov/html/contrib/sanitize.html">Sanitize</a>:
|
||||
Sanitize is a collection of five Bourne shell scripts for reducing
|
||||
tcpdump traces in order to address security and privacy concerns, by
|
||||
renumbering hosts and stripping out packet contents. Each script takes
|
||||
@@ -444,16 +424,24 @@ VOIP decoding on WEP encrypted channel, …), etc.</p></li>
|
||||
<li><p><a
|
||||
href="http://www.thedumbterminal.co.uk/software/sniff.html">Sniff</a>:
|
||||
Makes output from the tcpdump program easier to read and parse.</p></li>
|
||||
<li><p><a href="http://www.snort.org/">Snort</a>: Snort is an open
|
||||
<li><p><a href="https://www.snort.org/">Snort</a>: Snort is an open
|
||||
source network intrusion prevention and detection system (IDS/IPS)
|
||||
developed by Sourcefire, now owned by Cisco. Combining the benefits of
|
||||
signature, protocol and anomaly- based inspection, Snort is the most
|
||||
widely deployed IDS/IPS technology worldwide. With millions of downloads
|
||||
and approximately 500,000 registered users, Snort has become the de
|
||||
facto standard for IPS.</p></li>
|
||||
<li><p><a href="http://code.google.com/p/socket-sentry">Socket
|
||||
<li><p><a href="https://github.com/rhasselbaum/socket-sentry">Socket
|
||||
Sentry</a>: Socket Sentry is a real-time network traffic monitor for KDE
|
||||
Plasma in the same spirit as tools like iftop and netstat.</p></li>
|
||||
<li><p><a href="https://squey.org">Squey</a>: Interactive visualization
|
||||
software designed to explore large PCAPs to detect anomalies / weak
|
||||
signals.</p></li>
|
||||
<li><p><a href="https://suricata-ids.org">Suricata</a>: Suricata is a
|
||||
free and open source, mature, fast and robust network threat detection
|
||||
engine. The Suricata engine is capable of real time intrusion detection
|
||||
(IDS), inline intrusion prevention (IPS), network security monitoring
|
||||
(NSM) and offline pcap processing.</p></li>
|
||||
<li><p><a
|
||||
href="http://ita.ee.lbl.gov/html/contrib/tcp-reduce.html">TCP-Reduce</a>:
|
||||
TCP-Reduce is a collection of Bourne shell scripts for reducing tcpdump
|
||||
@@ -482,7 +470,9 @@ analysis or debugging. A program like ‘tcpdump’ shows a summary of
|
||||
packets seen on the wire, but usually doesn’t store the data that’s
|
||||
actually being transmitted. In contrast, tcpflow reconstructs the actual
|
||||
data streams and stores each flow in a separate file for later analysis.
|
||||
<a href="http://www.circlemud.org/jelson/software/tcpflow/">Original
|
||||
Yet, optionally, it can isolate pcap flows per tcp flow for granularized
|
||||
inspection. <a
|
||||
href="http://www.circlemud.org/jelson/software/tcpflow/">Original
|
||||
link</a>.</p></li>
|
||||
<li><p><a
|
||||
href="http://ita.ee.lbl.gov/html/contrib/tracelook.html">Tcplook</a>:
|
||||
@@ -490,34 +480,31 @@ Tracelook is an Tcl/TK program for graphically viewing the contents of
|
||||
trace files created using the -w argument to tcpdump. Tracelook should
|
||||
look at all protocols, but presently only looks at TCP connections. The
|
||||
program is slow and uses system resources prodigiously.</p></li>
|
||||
<li><p><a href="http://tcpreplay.synfin.net/">Tcpreplay</a>: Replays a
|
||||
pcap file on an interface using libnet.</p></li>
|
||||
<li><p><a href="ftp://ftp.ee.lbl.gov/tcpslice.tar.gz">Tcpslice</a>:
|
||||
<li><p><a href="https://github.com/appneta/tcpreplay">Tcpreplay</a>:
|
||||
Replays a pcap file on an interface using libnet.</p></li>
|
||||
<li><p><a href="https://github.com/pyke369/tcpsplice">Tcpslice</a>:
|
||||
Tcpslice is a tool for extracting portions of packet trace files
|
||||
generated using tcpdump’s -w flag. It can combine multiple trace files,
|
||||
and/or extract portions of one or more traces based on time. <a
|
||||
href="ftp://ftp.ee.lbl.gov/tcpslice.tar.gz">From the tcpdump CVS
|
||||
server</a>.</p></li>
|
||||
<li><p><a
|
||||
href="http://www.icir.org/mallman/software/tcpsplit/">Tcpsplit</a>: A
|
||||
and/or extract portions of one or more traces based on time.</p></li>
|
||||
<li><p><a href="https://github.com/pmcgleenon/tcpsplit">Tcpsplit</a>: A
|
||||
tool to break a single libpcap packet trace into some number of sub-
|
||||
traces, breaking the trace along TCP connection boundaries so that a TCP
|
||||
connection doesn’t end up split across two sub-traces. This is useful
|
||||
for making large trace files tractable for in- depth analysis and for
|
||||
subsetting a trace for developing analysis on only part of a
|
||||
trace.</p></li>
|
||||
<li><p><a href="http://www.frenchfries.net/paul/tcpstat/">Tcpstat</a>:
|
||||
<li><p><a href="https://frenchfries.net/paul/tcpstat/">Tcpstat</a>:
|
||||
Tcpstat reports certain network interface statistics much like vmstat
|
||||
does for system statistics. tcpstat gets its information by either
|
||||
monitoring a specific interface, or by reading previously saved tcpdump
|
||||
data from a file.</p></li>
|
||||
<li><p><a href="http://tcptrace.org/index.html">Tcptrace</a>: A tool
|
||||
<li><p><a href="https://github.com/blitz/tcptrace">Tcptrace</a>: A tool
|
||||
written by Shawn Ostermann at Ohio University, for analysis of TCP dump
|
||||
files. It can take as input the files produced by several popular
|
||||
packet- capture programs, including tcpdump, snoop, etherpeek, HP Net
|
||||
Metrix, and WinDump. tcptrace can produce several different types of
|
||||
output containing information on each connection seen, such as elapsed
|
||||
time, bytes and segments sent and recieved, retransmissions, round trip
|
||||
time, bytes and segments sent and received, retransmissions, round trip
|
||||
times, window advertisements, throughput, and more. It can also produce
|
||||
a number of graphs for further analysis.</p></li>
|
||||
<li><p><a href="https://www.tracewrangler.com/">TraceWrangler</a>:
|
||||
@@ -532,53 +519,68 @@ data while being easy to use.</p></li>
|
||||
sniffer able to provide several insight on the traffic patterns at both
|
||||
the network and transport levels with a tremendous set of flow
|
||||
features.</p></li>
|
||||
<li><p><a href="http://research.wand.net.nz/">WAND</a>: A wonderful
|
||||
<li><p><a href="https://research.wand.net.nz/">WAND</a>: A wonderful
|
||||
collection of tools built on libtrace to process network traffic, which
|
||||
is from The University of Waikato. I love this project!</p></li>
|
||||
<li><p><a href="http://www.tcpdump.org/wpcap.html">WinPcap</a>: An
|
||||
extract of a message from Guy Harris on state of WinPcap and
|
||||
WinDump.</p></li>
|
||||
<li><p><a
|
||||
href="http://www.sniffer.com/products/sniffer-basic/default.asp?A=2">Sniffer</a>:
|
||||
The Sniffer product family covers different fields of application
|
||||
(Distributed, Portable and Wireless Environment). Sniffer solutions
|
||||
monitor, troubleshoot, analyze, report on, and proactively manage
|
||||
network performance. They ensure peak performance throughout the
|
||||
enterprise infrastructure, across all LAN, WAN and high-speed
|
||||
topologies, from 10/100 Ethernet to the latest high-speed Asynchronous
|
||||
ATM, Gigabit, and Packet-over-SONET (PoS) backbones.</p></li>
|
||||
<li><p><a href="http://wiki.wireshark.org/Tools">Wireshark suit</a>: The
|
||||
well-konwn tool suit to support packet analyzer and protocol decoder. It
|
||||
also includes a few practical tools and scripts to support most of the
|
||||
common usage.</p></li>
|
||||
<li><p><a href="https://www.winpcap.org/">WinPcap</a>: An extract of a
|
||||
message from Guy Harris on state of WinPcap and WinDump.</p></li>
|
||||
<li><p><a href="https://wireedit.com/">WireEdit</a>: WireEdit is a free
|
||||
desktop WYSIWYG editor for network packets. It allows editing any stack
|
||||
layer as “rich text” without having any knowledge of packets syntax and
|
||||
encoding rules. The input and output file format is Pcap.</p></li>
|
||||
<li><p><a href="https://wiki.wireshark.org/Tools">Wireshark suit</a>:
|
||||
The well-known tool suit to support packet analyzer and protocol
|
||||
decoder. It also includes a few practical tools and scripts to support
|
||||
most of the common usage.</p></li>
|
||||
<li><p><a href="http://www.xplot.org/">Xplot</a>: The program xplot was
|
||||
written in the late 1980s to support the analysis of TCP packet
|
||||
traces.</p></li>
|
||||
<li><p><a href="https://github.com/kevthehermit/YaraPcap">yaraPcap</a>:
|
||||
Process HTTP Pcaps With YARA</p></li>
|
||||
<li><p><a
|
||||
href="https://github.com/MITRECND/yaraprocessor">yaraprocessor</a>: With
|
||||
yaraprocessor YARA can be run against individual packet payloads as well
|
||||
as a concatenation of some or all of the payloads. It was originally
|
||||
written for use in Chopshop, but can also be used without it.</p></li>
|
||||
<li><p><a href="https://zeek.org/">Zeek</a>: (formerly Bro) is an open
|
||||
source software platform that provides compact, high-fidelity
|
||||
transaction logs, file content, and fully customized output to analysts,
|
||||
from the smallest home office to the largest, fastest research and
|
||||
commercial networks. From the FAQ: “Zeek provides a comprehensive
|
||||
platform for network traffic analysis, with a particular focus on
|
||||
semantic security monitoring at scale. While often compared to classic
|
||||
intrusion detection/prevention systems, Zeek takes a quite different
|
||||
approach by providing users with a flexible framework that facilitates
|
||||
customized, in-depth monitoring far beyond the capabilities of
|
||||
traditional systems. With initial versions already in operational
|
||||
deployment during the mid ’90s, Zeek finds itself grounded in more than
|
||||
20 years of research. For more information, see the Zeek Overview and
|
||||
our promotional document, Why Choose Zeek?.”</p></li>
|
||||
</ul>
|
||||
<h2 id="dns-utilities">DNS Utilities <a name="dnstools"></a></h2>
|
||||
<ul>
|
||||
<li><p><a
|
||||
href="https://doc.powerdns.com/md/manpages/dnsgram.1/">dnsgram</a>:
|
||||
href="https://doc.powerdns.com/authoritative/manpages/dnsgram.1.html">dnsgram</a>:
|
||||
dnsgram is a debugging tool for intermittent resolver failures. it takes
|
||||
one or more input PCAP files and generates statistics on 5 second
|
||||
segments allowing the study of intermittent resolver issues.</p></li>
|
||||
<li><p><a
|
||||
href="https://doc.powerdns.com/md/manpages/dnsreplay.1/">dnsreplay</a>:
|
||||
href="https://doc.powerdns.com/authoritative/manpages/dnsreplay.1.html">dnsreplay</a>:
|
||||
Dnsreplay takes recorded questions and answers and replays them to the
|
||||
specified nameserver and reporting afterwards which percentage of
|
||||
answers matched, were worse or better. Then compares the answers and
|
||||
some other metrics with the actual ones with those found in the
|
||||
dumpfile.</p></li>
|
||||
<li><p><a
|
||||
href="https://doc.powerdns.com/md/manpages/dnsscan.1/">dnsscan</a>:
|
||||
href="https://doc.powerdns.com/authoritative/manpages/dnsscan.1.html">dnsscan</a>:
|
||||
dnsscan takes one or more INFILEs in PCAP format and generates a list of
|
||||
the number of queries per query type.</p></li>
|
||||
<li><p><a
|
||||
href="https://doc.powerdns.com/md/manpages/dnsscope.1/">dnsscope</a>:
|
||||
href="https://doc.powerdns.com/authoritative/manpages/dnsscope.1.html">dnsscope</a>:
|
||||
dnsscope takes an input PCAP and generates some simple statistics
|
||||
outputs these to console.</p></li>
|
||||
<li><p><a
|
||||
href="https://doc.powerdns.com/md/manpages/dnswasher.1/">dnswasher</a>:
|
||||
href="https://doc.powerdns.com/authoritative/manpages/dnswasher.1.html">dnswasher</a>:
|
||||
dnswasher takes an input file in PCAP format and writes out a PCAP file,
|
||||
while obfuscating end-user IP addresses. This is useful to share data
|
||||
with third parties while attempting to protect the privacy of your
|
||||
@@ -587,7 +589,8 @@ users.</p></li>
|
||||
<h2 id="file-extraction">File
|
||||
Extraction<a name="fileextraction"></a></h2>
|
||||
<ul>
|
||||
<li><p><a href="http://chaosreader.sourceforge.net/">Chaosreader</a>: A
|
||||
<li><p><a
|
||||
href="https://github.com/brendangregg/Chaosreader">Chaosreader</a>: A
|
||||
freeware tool to trace TCP/UDP/… sessions and fetch application data
|
||||
from snoop or tcpdump logs. This is a type of “any-snarf” program, as it
|
||||
will fetch telnet sessions, FTP files, HTTP transfers (HTML, GIF, JPEG,
|
||||
@@ -596,7 +599,7 @@ html index file is created that links to all the session details,
|
||||
including realtime replay programs for telnet, rlogin, IRC, X11 and VNC
|
||||
sessions; and reports such as image reports and HTTP GET/POST content
|
||||
reports.</p></li>
|
||||
<li><p><a href="http://www.monkey.org/~dugsong/dsniff/">Dsniff</a>:
|
||||
<li><p><a href="https://www.monkey.org/~dugsong/dsniff/">Dsniff</a>:
|
||||
Dsniff is a collection of tools for network auditing and penetration
|
||||
testing. dsniff, filesnarf, mailsnarf, msgsnarf, urlsnarf, and webspy
|
||||
passively monitor a network for interesting data (passwords, e-mail,
|
||||
@@ -605,8 +608,8 @@ of network traffic normally unavailable to an attacker (e.g, due to
|
||||
layer-2 switching). sshmitm and webmitm implement active
|
||||
monkey-in-the-middle attacks against redirected SSH and HTTPS sessions
|
||||
by exploiting weak bindings in ad-hoc PKI.</p></li>
|
||||
<li><p><a href="http://foremost.sourceforge.net/">Foremost</a>: is a
|
||||
console program to recover files based on their headers, footers, and
|
||||
<li><p><a href="https://github.com/jonstewart/foremost">Foremost</a>: is
|
||||
a console program to recover files based on their headers, footers, and
|
||||
internal data structures. This process is commonly referred to as data
|
||||
carving. Foremost can work on image files, such as those generated by
|
||||
dd, Safeback, Encase, etc, or directly on a drive. The headers and
|
||||
@@ -614,13 +617,13 @@ footers can be specified by a configuration file or you can use command
|
||||
line switches to specify built-in file types. These built-in types look
|
||||
at the data structures of a given file format allowing for a more
|
||||
reliable and faster recovery.</p></li>
|
||||
<li><p><a href="http://justniffer.sourceforge.net/">Justniffer</a>:
|
||||
<li><p><a href="https://onotelli.github.io/justniffer/">Justniffer</a>:
|
||||
Justniffer is a network protocol analyzer that captures network traffic
|
||||
and produces logs in a customized way, can emulate Apache web server log
|
||||
files, track response times and extract all “intercepted” files from the
|
||||
HTTP traffic.</p></li>
|
||||
<li><p><a
|
||||
href="http://www.netresec.com/?page=NetworkMiner">NetworkMiner</a>:
|
||||
href="https://www.netresec.com/index.ashx?page=NetworkMiner">NetworkMiner</a>:
|
||||
NetworkMiner is a Network Forensic Analysis Tool (NFAT) for Windows (but
|
||||
also works in Linux / Mac OS X / FreeBSD). NetworkMiner can be used as a
|
||||
passive network sniffer/packet capturing tool in order to detect
|
||||
@@ -628,7 +631,15 @@ operating systems, sessions, hostnames, open ports etc. without putting
|
||||
any traffic on the network. NetworkMiner can also parse PCAP files for
|
||||
off-line analysis and to regenerate/ reassemble transmitted files and
|
||||
certificates from PCAP files.</p></li>
|
||||
<li><p><a href="http://www.snort.org/">Snort</a>: is an open source
|
||||
<li><p><a href="https://github.com/vikwin/pcapfex">pcapfex</a> - Packet
|
||||
CAPture Forensic Evidence eXtractor (pcapfex) is a tool that finds and
|
||||
extracts files from packet capture files. Its power lies in its ease of
|
||||
use. Just provide it a pcap file, and it will try to extract all of the
|
||||
files. It is an extensible platform, so additional file types to
|
||||
recognize and extract can be added easily.</p></li>
|
||||
<li><p><a href="https://github.com/sleuthkit/scalpel">scalpel</a>:
|
||||
Scalpel is an open source data carving tool.</p></li>
|
||||
<li><p><a href="https://www.snort.org/">Snort</a>: is an open source
|
||||
network intrusion prevention and detection system (IDS/IPS) developed by
|
||||
Sourcefire, now owned by Cisco. Combining the benefits of signature,
|
||||
protocol and anomaly- based inspection, Snort is the most widely
|
||||
@@ -655,17 +666,37 @@ is released under the GNU General Public License and with some scripts
|
||||
under Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported
|
||||
(CC BY-NC-SA 3.0) License.</p></li>
|
||||
</ul>
|
||||
<h2 id="usb">USB</h2>
|
||||
<h3 id="capture-tools">Capture tools</h3>
|
||||
<ul>
|
||||
<li><a
|
||||
href="https://www.kernel.org/doc/Documentation/usb/usbmon.txt">usbmon</a>
|
||||
- a subsystem of Linux kernel to capture usb packets.</li>
|
||||
<li><a href="https://github.com/desowin/usbpcap">USBPcap</a> - a
|
||||
solution for Windows.</li>
|
||||
</ul>
|
||||
<h3 id="analysis">Analysis</h3>
|
||||
<ul>
|
||||
<li><a
|
||||
href="https://github.com/KOLANICH/USBPcapOdinDumper">USBPcapOdinDumper</a>
|
||||
- transforms .pcap files with <code>usbmon</code> and
|
||||
<code>USBPcap</code> frames format of captures from flashing an Android
|
||||
phone with Odin or <a
|
||||
href="https://gitlab.com/BenjaminDobell/Heimdall">Heimdall</a> into a
|
||||
set of files with frames payload. Useful for reverse-engineering. Has a
|
||||
modular architecture easily transformable for other applications
|
||||
formats.</li>
|
||||
</ul>
|
||||
<h2 id="related-projects">Related Projects<a name="others"></a></h2>
|
||||
<ul>
|
||||
<li><p><a href="http://www.tcpdump.org/other/bpfext42.tar.Z">BPF for
|
||||
<li><p><a href="https://www.tcpdump.org/other/bpfext42.tar.Z">BPF for
|
||||
Ultrix</a>: A distribution of BPF for Ultrix 4.2, with both source code
|
||||
and binary modules.</p></li>
|
||||
<li><p><a
|
||||
href="http://www.cs.berkeley.edu/~abegel/sigcomm99/bpf+.ps">BPF+</a>:
|
||||
<li><p><a href="https://andrewbegel.com/papers/bpf.pdf">BPF+</a>:
|
||||
Exploiting Global Data-flow Optimization in a Generalized Packet Filter
|
||||
Architecture By Andrew Begel, Steven McCanne, and Susan Graham.</p></li>
|
||||
<li><p><a
|
||||
href="http://ita.ee.lbl.gov/html/contrib/fft_fgn_c.html">FFT-FGN-C</a>:
|
||||
href="ftp://ita.ee.lbl.gov/html/contrib/fft_fgn_c.html">FFT-FGN-C</a>:
|
||||
is a program for synthesizing a type of self-similar process known as
|
||||
fractional Gaussian noise. The program is fast but approximate.
|
||||
Fractional Gaussian noise is only one type of self-similar process. When
|
||||
@@ -686,7 +717,7 @@ to natively read PCAP files. Also features a Hive
|
||||
Serializer/Deserializer (SerDe) to query PCAPs using SQL like
|
||||
commands.</p></li>
|
||||
<li><p><a
|
||||
href="http://www.sonycsl.co.jp/person/kjc/papers/freenix2000/">Traffic
|
||||
href="https://www2.sonycsl.co.jp/person/kjc/papers/freenix2000/">Traffic
|
||||
Data Repository at the WIDE Project</a>: It becomes increasingly
|
||||
important for both network researchers and operators to know the trend
|
||||
of network traffic and to find anomaly in their network traffic. This
|
||||
@@ -698,9 +729,20 @@ open to the public. We review the issues on user privacy, and then, the
|
||||
tools used to build the WIDE traffic repository. We will report the
|
||||
current status and findings in the early stage of our IPv6
|
||||
deployment.</p></li>
|
||||
<li><p><a href="ftp://ftp.ee.lbl.gov/papers/bpf-usenix93.ps.Z">Usenix93
|
||||
Paper on BPF</a>: The libpcap interface supports a filtering mechanism
|
||||
based on the architecture in the BSD packet filter. BPF is described in
|
||||
the 1993 Winter Usenix paper “The BSD Packet Filter: A New Architecture
|
||||
for User-level Packet Capture”.</p></li>
|
||||
<li><p><a
|
||||
href="https://www.tcpdump.org/papers/bpf-usenix93.pdf">Usenix93 Paper on
|
||||
BPF</a>: The libpcap interface supports a filtering mechanism based on
|
||||
the architecture in the BSD packet filter. BPF is described in the 1993
|
||||
Winter Usenix paper “The BSD Packet Filter: A New Architecture for
|
||||
User-level Packet Capture”.</p></li>
|
||||
</ul>
|
||||
<h2 id="contributors">Contributors</h2>
|
||||
<p>Thank you all contributors ❤</p>
|
||||
<p><a
|
||||
href="https://github.com/caesar0301/awesome-pcaptools/graphs/contributors"><img
|
||||
src="https://contrib.rocks/image?repo=caesar0301/awesome-pcaptools"
|
||||
title="awesome-pcaptools contributors"
|
||||
alt="awesome-pcaptools contributors" /></a></p>
|
||||
<p><a
|
||||
href="https://github.com/caesar0301/awesome-pcaptools">pcaptools.md
|
||||
Github</a></p>
|
||||
|
||||
Reference in New Issue
Block a user