Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ipresend(1) [netbsd man page]

IPRESEND(1)						      General Commands Manual						       IPRESEND(1)

ipresend - resend IP packets out to network SYNOPSIS
ipresend [ -EHPRSTX ] [ -d <device> ] [ -g <gateway> ] [ -m <MTU> ] [ -r <filename> ] DESCRIPTION
ipresend was designed to allow packets to be resent, once captured, back out onto the network for use in testing. ipresend supports a num- ber of different file formats as input, including saved snoop/tcpdump binary data. OPTIONS
-d <interface> Set the interface name to be the name supplied. This is useful with the -P, -S, -T and -E options, where it is not otherwise possi- ble to associate a packet with an interface. Normal "text packets" can override this setting. -g <gateway> Specify the hostname of the gateway through which to route packets. This is required whenever the destination host isn't directly attached to the same network as the host from which you're sending. -m <MTU> Specify the MTU to be used when sending out packets. This option allows you to set a fake MTU, allowing the simulation of network interfaces with small MTU's without setting them so. -r <filename> Specify the filename from which to take input. Default is stdin. -E The input file is to be text output from etherfind. The text formats which are currently supported are those which result from the following etherfind option combinations: etherfind -n etherfind -n -t -H The input file is to be hex digits, representing the binary makeup of the packet. No length correction is made, if an incorrect length is put in the IP header. -P The input file specified by -i is a binary file produced using libpcap (i.e., tcpdump version 3). Packets are read from this file as being input (for rule purposes). -R When sending packets out, send them out "raw" (the way they came in). The only real significance here is that it will expect the link layer (i.e. ethernet) headers to be prepended to the IP packet being output. -S The input file is to be in "snoop" format (see RFC 1761). Packets are read from this file and used as input from any interface. This is perhaps the most useful input type, currently. -T The input file is to be text output from tcpdump. The text formats which are currently supported are those which result from the following tcpdump option combinations: tcpdump -n tcpdump -nq tcpdump -nqt tcpdump -nqtt tcpdump -nqte -X The input file is composed of text descriptions of IP packets. SEE ALSO
ipftest(1), ipsend(1), iptest(1), bpf(4), ipsend(5), tcpdump(8) DIAGNOSTICS
Needs to be run as root. BUGS
Not all of the input formats are sufficiently capable of introducing a wide enough variety of packets for them to be all useful in testing. If you find any, please send email to me at IPRESEND(1)

Check Out this Related Man Page

TCPPROF(1)						    BSD General Commands Manual 						TCPPROF(1)

tcpprof -- report profile of network traffic SYNOPSIS
tcpprof [-?hdnpR] [-f filter expr] [-i interface] [-P port] [-r filename] [-s seconds] [-S letters] [-t lines] DESCRIPTION
tcpprof reports a profile of network traffic by ranking it by link type, ip protocol, TCP/UDP port, ip address, or network address. Network information is collected either by reading data from filename, or by directly monitoring the network interface interface. The default action for tcpprof is to automatically search for an appropriate interface, and to generate a profile before it exits. When reading data from filename, tcpprof will display the profile and exit immediately after the entire file has been processed. When col- lecting data from interface, tcpprof will keep running unless the -s option had been specified. OPTIONS
The options are as follows: -f filter expr Filter the packets according the rules given by filter expr. For the syntax of these rules, see tcpdump(1). The argument must be quoted if it contains spaces in order to separate it from other options. -h, -? Display version and a brief help message. -d tcpprof will track the source and destination information separately, where applicable, and identify source data with a ">" and destination data with "<". For example, a "http <" statistic signifies all traffic with destination port 80 (http). This option only applies to port, host and network statistics. -i interface Do a live capture (rather than read from a file) on the interface interface given on the command line. If interface is "auto" then tcpprof tries to find an appropriate one by itself. -P port This tells tcpprof to ignore TCP and UDP ports greater than or equal to port when displaying port statistics. This is not the same as filtering these port numbers out of the data set. This way, packets with i.e. the source port above port and the desti- nation port below port will be able to still count the lower port number as a statistic. In addition, this doesn't affect the other statistic types (link, protocol, etc.) -p Set the interface into non-promiscuous mode (promiscuous is the default) when doing live captures. -r filename Read all data from filename, which may be a regular file, a named pipe or "-" to read it's data from standard input. Acceptable file formats include pcap (tcpdump(1) files) and "snoop" format files. filename is usually a file created by the tcpdump(1) com- mand using the "-w" option. -S letters Tells tcpprof which statistics to display. letters must be a string of one or more of the following letters: l show stats about the link layer i show stats about all ip protocols p show stats about TCP/UDP ports h show stats about hosts/ip addresses n show stats about network addresses a a synonym for "liphn" -s seconds When monitoring an interface, tcpprof runs for only seconds seconds, and then quits. Has no effect when reading data from a file. -t lines When printing a profile of the data, tcpprof will display a maximum of lines lines for each statistic. SIGNALS
Upon receiving a SIGINT, tcpprof will print any remaining statistics, and then exit. FILES
/dev/bpfn the packet filter device EXAMPLES
tcpprof -i fxp0 -S a Displays a complete profile of network data passing through the fxp0 network interface, after the user enters ^C (control C). tcpprof -r file.dump -S a Displays a complete profile of network data from the tcpdump(1) generated file "file.dump". SEE ALSO
tcpdump(1), pcap(3), bpf(4) HISTORY
tcpprof was first written along side tcpstat in Winter 1998 using FreeBSD 3.0, and then finally retrofitted for Linux in Spring 2000. It became installed along with tcpstat since version 1.5. AUTHORS
Paul Herman <> Cologne, Germany. Please send all bug reports to this address. BUGS
Not tested with link types other than Ethernet, PPP, and "None" types. There may be problems reading non-IPv4 packets across platforms when reading null type link layers. This is due to a lack of a standardized packet type descriptor in libpcap for this link type. Snoop file formats cannot be read from stdin or named pipes. BSD
December 22, 2001 BSD
Man Page