Home
Search all pages
Subjects
By activity
Professions, Sciences, Humanities, Business, ...
User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...
Text Strings
Conversions, tests, processing, manipulation,...
Math
Integer, Floating point, Matrix, Statistics, Boolean, ...
Processing
Algorithms, Memory, Process control, Debugging, ...
Stored Data
Data storage, Integrity, Encryption, Compression, ...
Communications
Networks, protocols, Interprocess, Remote, Client Server, ...
Hard World Timing, Calendar and Clock, Audio, Video, Printer, Controls...
File System
Management, Filtering, File & Directory access, Viewers, ...
|
|
|
RocketLink!--> Man page versions:
OpenBSD
FreeBSD
NetBSD
Others
IPRESEND(1) OpenBSD Reference Manual IPRESEND(1)
NAME
ipresend - resend IP packets out to network
SYNOPSIS
ipsend [-EHPRSTX] [-d device] [-g gateway] [-m mtu] [-r filename]
DESCRIPTION
ipresend was designed to allow captured packets to be resent onto the
network for use in testing. ipresend supports a number of different file
formats as input, including saved snoop and tcpdump(8) binary data.
ipresend must be run as root.
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 possible 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 Set the MTU used when sending out packets to mtu. This op-
tion allows you to set a fake MTU, allowing the simulation
of network interfaces with small MTU's.
-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 -r is a binary file produced
using libpcap (i.e., tcpdump(8) 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, cur-
rently.
-T The input file is to be text output from tcpdump(8). The
text formats which are currently supported are those which
result from the following tcpdump(8) option combinations:
tcpdump -n
tcpdump -nq
tcpdump -nqt
tcpdump -nqtt
tcpdump -nqte
-X The input file is composed of text descriptions of IP pack-
ets.
SEE ALSO
ipftest(1), ipresend(1), iptest(1), bpf(4), tcpdump(8)
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 darrenr@cyber.com.au
OpenBSD 2.6 October 9, 1999 2
Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts Institute of Technology, Free Software Foundation, FreeBSD Inc., and others. |
(Corrections, notes, and links courtesy of RocketAware.com)
FreeBSD Sources for ipresend(1) OpenBSD sources for ipresend(1)
Up to: Communication Debugging - Status, tracing, and debugging communications and protocols.
RocketLink!--> Man page versions:
OpenBSD
FreeBSD
NetBSD
Others
Rapid-Links:
Search | About | Comments | Submit Path: RocketAware >
ipresend.1/
RocketAware.com is a service of Mib Software Copyright 1999, Forrest J. Cavalier III. All Rights Reserved. We welcome submissions and comments
|