Subsections
I've tried to keep this document up to date with the changes in tcpreplay,
but occasionally I get too busy, make a mistake or just forget something.
If you find anything in this document which could be improved upon,
please let me know.
If you still have a question after reading the Tcpreplay manual and
FAQ, please contact the Tcpreplay-Users <tcpreplay-users@lists.sourceforge.net>
mailing list. Note that if you ask a question which has clearly been
covered in either the manual or FAQ, you will most likely be told
to RTFM.
- tcpreplay - replay packets stored in a pcap file as they were captured
- tcprewrite - edit packets stored in a pcap file
- tcpprep - a pcap pre-processor for tcpreplay/tcprewrite
- flowreplay1 - connects to a server(s) and replays the client side of the connection
stored in a pcap file
Recently, other people and projects have developed better versions
of two applications that ship with tcpreplay 2.x:
- pcapmerge - merges two or more pcap files into one. Ethereal now ships
with a more powerful appliation called 'mergecap'.
- capinfo - displays basic information about a pcap file. Ethereal now
ships with a more powerful application of the same name.
The source code is available in tarball format on the tcpreplay homepage:
http://tcpreplay.sourceforge.net/ I also encourage users familiar
with Subversion to try checking out the latest code as it often has
additional features and bugfixes not found in the tarballs.
svn checkout https://www.synfin.net:444/svn/tcpreplay/trunk tcpreplay-3
There are OS X and Debian packages available via Fink and APT respectively.
Both packages are maintained by other people and occasionally are
out of date with the latest source code release.
- Libnet2 1.1.x or better (1.1.3 fixes a checksum bug)
- Libpcap3 0.6.x or better (0.8.3 or better recommended)
- To support the packet decoding feature you'll need tcpdump4 installed.
- You'll also need a compatible operating system. Basically, any *NIX
operating system should work. Linux, *BSD, Solaris, OS X and others
should all work. If you find any compatibility issues with any *NIX
OS, please let me know.
Two easy steps:
- As a normal user: ./configure && make
- As root: make install
There are some optional arguments which can be passed to the 'configure'
script which may help in cases where your libnet, libpcap or tcpdump
installation is not standard or if it can't determine the correct
network interface card to use for testing. If you find that configure
isn't completing correctly, run: ./configure -help for more
information.
You may also choose to run 'make test -i' as root:
- make test is just a series of sanity checks which try to find serious
bugs (crashes) in tcpprep and tcpreplay.
- make test requires at least one properly configured network interface.
If the configure script can't guess what a valid interface is you
can specify it with the -with-testnic and -with-testnic2 arguments.
- If make test fails, often you can find details in test/test.log.
- OpenBSD's make has a bug where it ignores the MAKEFLAGS variable in
the Makefile, hence you'll probably want to run: make -is test
instead.
Footnotes
- ... flowreplay1
- Flowreplay is still ``alpha'' quality and is not usable for most
situations. Anyone interested in helping me develop flowreplay is
encouraged to contact me.
- ... Libnet2
- http://www.packetfactory.net/libnet/
- ... Libpcap3
- http://www.tcpdump.org/
- ... tcpdump4
- http://www.tcpdump.org/
Aaron Turner
2005-02-27