tcpprep(1) | User Commands | tcpprep(1) |
tcpprep - Create a tcpreplay cache cache file from a pcap file.
tcpprep [-flags] [-flag [value]] [--option-name[[=| ]value]]
All arguments must be options.
tcpprep is a pcap(3) file pre-processor which creates a cache file which provides "rules" for tcprewrite(1) and tcpreplay(1) on how to process and send packets.
The basic operation of tcpreplay is to resend all packets from the input file(s) out a single file. Tcpprep processes a pcap file and applies a set of user-specified rules to create a cache file which tells tcpreplay whether or not to send each packet and which interface the packet should be sent out of.
For more details, please see the Tcpreplay Manual at: http://tcpreplay.appneta.com
in the range 0 through 5
If configured with --enable-debug, then you can specify a verbosity level for debugging output. Higher numbers increase verbosity.
Tcpprep will try to automatically determine the primary function of hosts based on the traffic captured and classify each host as client or server. In order to do so, you must provide a hint to tcpprep as to how to search for clients and servers. Valid hints are:
bridge Bridge mode processes each packet to try to determine if the sender is a client or server. Once all the packets are processed, the results are weighed according to the server/client ratio (--ratio) and systems are assigned an interface. If tcpprep is unable to determine what role a system plays, tcpprep will abort.
router Router mode works just like bridge mode, except that after weighing is done, systems which are undetermined are considered a server if they fall inside a network known to contain other servers. Router has a greater chance of successfully splitting clients and servers but is not 100% foolproof.
client Client mode works just like bridge mode, except that unclassified systems are treated as clients. Client mode should always complete successfully.
server Server mode works just like bridge mode, except that unclassified systems are treated as servers. Server mode should always complete successfully.
first First mode works by looking at the first time
each IP is seen in the SRC and DST fields in the IP header. If the host
is first seen in the SRC field, it is a client and if it's first seen in
the DST field, it is marked as a server. This effectively replicates the
processing of the tomahawk test tool. First mode should always complete
successfully.
Specify a comma delimited list of CIDR netblocks to match against the source IP of each packet. Packets matching any of the CIDR's are classified as servers.
IPv4 Example:
IPv6 Example:
--cidr=192.168.0.0/16,172.16.0.0/12,10.0.0.0/8
--cidr=[::ffff:0:0/96],[fe80::/16]
Specify a regular expression to match against the source IP of each packet. Packets matching the regex are classified as servers.
Specifies that TCP and UDP traffic over IPv4 and IPv6 should be classified as client or server based upon the destination port of the header.
Specify a list of MAC addresses to match against the source MAC of each packet. Packets matching one of the values are classified as servers.
Normally the --mac, --regex and --cidr flags specify are used to specify the servers and non-IP packets are classified as clients. By using --reverse, these features are reversed so that the flags specify clients and non-IP packets are classified as servers.
Specify a comment to be imbedded within the output cache file and later viewed.
By default, tcpprep includes the arguments passed on the command line in the cache file comment (in addition to any user specified --comment). If for some reason you do not wish to include this, specify this option.
Override default of processing all packets stored in the capture file and only send/edit packets which match the provided rule. Rules can be one of:
S:<CIDR1>,... - Source IP must match specified IPv4/v6 CIDR(s)
D:<CIDR1>,... - Destination IP must match specified IPv4/v6 CIDR(s)
B:<CIDR1>,... - Both source and destination IP must match specified IPv4/v6 CIDR(s)
E:<CIDR1>,... - Either IP must match specified IPv4/v6 CIDR(s)
P:<LIST> - Must be one of the listed packets where the list corresponds to the packet number in the capture file.
would process packets 1 through 5, the 9th and 15th packet, and packets 72 until the end of the file
-x P:1-5,9,15,72-
F:'<bpf>' - BPF filter. See the tcpdump(8)
man page for syntax.
Override default of processing all packets stored in the capture file and only send/edit packets which do NOT match the provided rule. Rules can be one of:
S:<CIDR1>,... - Source IP must not match specified IPv4/v6 CIDR(s)
D:<CIDR1>,... - Destination IP must not match specified IPv4/v6 CIDR(s)
B:<CIDR1>,... - Both source and destination IP must not match specified IPv4/v6 CIDR(s)
E:<CIDR1>,... - Either IP must not match specified IPv4/v6 CIDR(s)
P:<LIST> - Must not be one of the listed packets where the list corresponds to the packet number in the capture file.
would skip packets 1 through 5, the 9th and 15th packet, and packets 72 until the end of the file
-x P:1-5,9,15,72-
Uses a list of ports used by servers in the same format as of /etc/services: <service_name> <port>/<protocol> # comment
Example: http 80/tcp
By default, non-IP traffic which can not be classified as client or server is classified as "client". Specifying --nonip will reclassify non-IP traffic as "server". Note that the meaning of this flag is reversed if --reverse is used.
Since a given host may have both client and server traffic being sent to/from it, tcpprep uses a ratio to weigh these packets. If you would like to override the default of 2:1 server to client packets required for a host to be classified as a server, specify it as a floating point value.
in the range 0 through 32
By default, auto modes use a minimum network mask length of 30 bits to build networks containing clients and servers. This allows you to override this value. Larger values will increase performance but may provide inaccurate results.
in the range 0 through 32
By default, auto modes use a maximum network mask length of 8 bits to build networks containing clients and servers. This allows you to override this value. Larger values will decrease performance and accuracy but will provide greater chance of success.
When enabling verbose mode (-v) you may also specify
one or more additional arguments to pass to tcpdump to modify the
way packets are decoded. By default, -n and -l are used. Be sure to
quote the arguments so that they are not interpreted by tcprewrite. The
following arguments are valid:
[ -aAeNqRStuvxX ]
[ -E spi@ipaddr algo:secret,... ]
[ -s snaplen ]
This option has not been fully documented.
Any option that is not marked as not presettable may be preset by loading values from configuration ("RC" or ".INI") file(s). The homerc file is "$$/", unless that is a directory. In that case, the file ".tcppreprc" is searched for within that directory.
See OPTION PRESETS for configuration files.
One of the following exit values will be returned:
Copyright 2013-2022 Fred Klassen - AppNeta Copyright 2000-2012 Aaron Turner For support please use the tcpreplay-users@lists.sourceforge.net mailing list. The latest version of this software is always available from: http://tcpreplay.appneta.com/
Copyright (C) 2000-2022 Aaron Turner and Fred Klassen all rights reserved. This program is released under the terms of the GNU General Public License, version 3 or later.
Please send bug reports to: tcpreplay-users@lists.sourceforge.net
This manual page was AutoGen-erated from the tcpprep option definitions.
01 Jan 2023 | tcpprep |