pcap-broker
is a tool to capture network traffic and make this available to one or more clients via PCAP-over-IP.
PCAP-over-IP can be useful in situations where low latency is a priority, for example during Attack and Defend CTFs. More information on PCAP-over-IP can be found here:
pcap-broker
supports the following features:
- Distributing packet data to one or more PCAP-over-IP clients
- Execute a command to capture traffic, usually
tcpdump
(expects stdout to be pcap data) pcap-broker
will exit if the capture command exits
Building pcap-broker
requires the libpcap
development headers, on Debian you can install it with:
$ apt install libpcap-dev
To build from source, clone this repository and run:
$ go build .
$ ./pcap-broker --help
Or you can build the Docker container:
$ docker build -t pcap-broker .
$ docker run -it pcap-broker --help
Alternatively, install directly using go
:
$ go install github.com/fox-it/pcap-broker@latest
$ pcap-broker --help
$ ./pcap-broker --help
Usage of ./pcap-broker:
-cmd string
command to execute for pcap data (eg: tcpdump -i eth0 -n --immediate-mode -s 65535 -U -w -)
-debug
enable debug logging
-json
enable json logging
-listen string
listen address for pcap-over-ip (eg: localhost:4242)
-n disable reverse lookup of connecting PCAP-over-IP client IP address
Arguments can be passed via commandline:
$ ./pcap-broker -cmd "sudo tcpdump -i eth0 -n --immediate-mode -s 65535 -U -w -"
Or alternatively via environment variables:
LISTEN_ADDRESS=:4242 PCAP_COMMAND='sudo tcpdump -i eth0 -n --immediate-mode -s 65535 -U -w -' ./pcap-broker
Using environment variables is useful when you are using pcap-broker
in a Docker setup.
Now you can connect to it via TCP and stream PCAP data using nc
and tcpdump
:
$ nc -v localhost 4242 | tcpdump -nr -
Or use a tool that natively supports PCAP-over-IP, for example tshark
:
$ tshark -i TCP@localhost:4242
One use case is to acquire PCAP from a remote machine over SSH and make this available via PCAP-over-IP.
Such a use case, including an example SSH command to bootstrap this, has been documented in the docker-compose.yml.example
file:
services:
pcap-broker-remote-host:
image: pcap-broker:latest
container_name: pcap-broker-remote-host
restart: always
volumes:
# Mount the private key into container that wil be used for SSH
# Ensure that on the `remote-host` the public key is in the /root/.ssh/authorized_keys file.
- ~/.ssh/id_ed25519:/root/.ssh/id_ed25519:ro
environment:
# Command that will be executed by pcap-broker to read PCAP data.
# Which is to SSH into `remote-host` and run tcpdump on eth0 and write PCAP data to stdout.
# The `not port 22` BPF is necessary to avoid any traffic loops as the PCAP data is transferred over SSH.
PCAP_COMMAND: |-
ssh root@remote-host -oStrictHostKeyChecking=no
tcpdump -U --immediate-mode -ni eth0 -s 65535 -w - not port 22
# Bind on 0.0.0.0 port 4242. From within the same Docker network you can reach it using the `container_name`
# For example in another Docker service you can reach this pcap-broker using `pcap-broker-remote-host:4242`
LISTEN_ADDRESS: "0.0.0.0:4242"
ports:
# This is optional, but makes the PCAP-over-IP port also available locally on the Docker host on port 4200.
# Handy for debugging, for example: `nc -v localhost 4200 | tcpdump -nr -`
- 127.0.0.1:4200:4242
This tool was initially written for Attack & Defend CTF purposes but can be useful in other situations where low latency is preferred, or whenever a no-nonsense PCAP-over-IP server is needed. During the CTF that Fox-IT participated in, pcap-broker
allowed the Blue Team to capture network data once and disseminate this to other tools that natively support PCAP-over-IP, such as: