tcpreplay
v4.6.1 open-sourceThe section your link pointed to isn't on tcpreplay's page any more, so we've brought you to the top.
Edit and replay captured network traffic at arbitrary speeds — a suite of pcappcapA packet capture, recorded network packets that can be inspected later. Analysts use it to reconstruct communication and investigate protocol behavior or suspicious traffic. tools for *NIX and Windows.
tcpreplay --xdp -i eth0 capture.pcap tcpreplay --xdp --xdp-no-fallback --xdp-queue 2 -i eth0 capture.pcap tcpreplay --loss 10 -i eth0 capture.pcap tcpreplay --xdp -i eth0 capture.pcap tcpreplay --xdp --xdp-no-fallback --xdp-queue 2 -i eth0 capture.pcap tcpreplay --loss 10 -i eth0 capture.pcap tcpreplay --edit -S <source_seq> -A <source_ack> -s <snaplen> capture.pcap tcpreplay --fuzz-factor=0.5 capture.pcap tcpreplay --fuzz-seed=12345 -i eth0 capture.pcap tcpreplay --unique-ip-loops=5 -i eth0 capture.pcap tcpreplay --stats=0 -i eth0 capture.pcap tcpreplay --unique-ip --duration=60 capture.pcap tcpreplay --qtx-bypass --netmap-delay 50 capture.pcap
Summary
tcpreplay is an open-source (GPLv3) suite of command-line utilities for UNIX and Windows-under-Cygwin that replays network traffic previously captured with tools like tcpdump or Wireshark back onto a live network, rewriting Layer 2/3/4 headers and classifying traffic as client or server along the way. It runs in single or dual NICNICA network interface card or adapter, the hardware that connects a computer to a network. It sends and receives packets over the link. mode, from a trickle up to full wire rate, and is aimed at people testing firewalls, IDS/IPSIDS/IPSIntrusion Detection System / Intrusion Prevention System — network or host monitors that inspect traffic for known attack patterns, alerting on matches (IDS) or actively blocking them (IPS). and NetFlow appliances rather than at those doing packet capturepacket captureA packet capture, recorded network packets that can be inspected later. Analysts use it to reconstruct communication and investigate protocol behavior or suspicious traffic. itself. Injection backends include AF_XDPAF_XDPA Linux kernel interface that hands raw packets to a userspace program straight off the network card, skipping the kernel's networking stack. It is how userspace tools reach line rate on 100G links. and io_uring for high-speed links, plus a raw IP path for interfaces like WireGuardWireGuardA modern VPN protocol and Linux kernel module, maintained as an open-source project, that establishes encrypted tunnels using minimal code and fast cryptography, giving cyber tools a lightweight, high-performance transport layer. that lack an L2 header. First committed in 2002, it remains active, with 76 contributors and a release 24 days ago.
Edit and replay captured network traffic at arbitrary speeds — a suite of pcap tools for *NIX and Windows.
How tcpreplay helps
Will my firewall or IPS actually catch this traffic when it's live, not just sitting in a pcap?
replays the captured packets back onto a real link at the same timing they were recorded with, so the appliance sees the traffic exactly as it arrived the first time, rather than as a file being parsed offline
Can my inline device tell the difference between the client side and the server side of a captured conversation?
classifies each captured flow as client or server and can send them out two separate interfaces so an in-line device sees traffic arriving from the correct direction
Will my NetFlow appliance's timeout settings hold up under a real flow rate, not just a handful of test flows?
drives the link at rates up to hundreds of thousands of flows per second and reports flows-per-second statistics so flow-expiry tuning can be checked against real throughput
Does my monitoring stack still work once headers no longer match the original capture environment?
rewrites Layer 2, 3 and 4 header fields as it replays so the traffic matches a different network's addressing instead of the one it was captured on
Can my application stay correct when the network isn't ideal?
drops a configurable percentage of packets at random during replay so the receiving application can be watched under simulated loss instead of a clean feed
Will traffic reach a tunnel or VPN interface that never had a normal frame header to begin with?
sends packets through a raw IP path for interfaces like WireGuard or tun that lack a Layer 2 header, rebuilding just enough framing to get them onto the wire
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Screenshots
From the release notes, newest first. Click one to see it full size.Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for tcpreplay, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail tcpreplay puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
20 entries
No entries match these filters.
- August 20261
- July 202612
- July 20241
- November 20181
- May 20171
- March 20171
- January 20161
- December 20141
- January 20141
Project health
Issue, contributor and maintainer activity in appneta/tcpreplay, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 5 −1 vs prior 12 months
- Maintainers 1 +2 joined · −2 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 17% of issues opened, last 12 months
- Median time to close 2.4 days first maintainer reply 0.9 hours
- Open backlog 0 of 531 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 0
- Contributors / month 0
- Commits / month 0
- Stars 1,349
- bugs 44%
- features 17%
- other 39%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.