ipresend(1) [freebsd man page]

IPRESEND(1)						      General Commands Manual						       IPRESEND(1)

NAME

       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

       snoop(1m), tcpdump(8), etherfind(8c), ipftest(1), ipresend(1), iptest(1), bpf(4), dlpi(7p)

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 darrenr@pobox.com

																       IPRESEND(1)

Check Out this Related Man Page

PFLOG(4)                                                   BSD Kernel Interfaces Manual                                                   PFLOG(4)

NAME

     pflog -- packet filter logging interface

SYNOPSIS

     device pflog

DESCRIPTION

     The pflog interface is a pseudo-device which makes visible all packets logged by the packet filter, pf(4).  Logged packets can easily be mon-
     itored in real time by invoking tcpdump(1) on the pflog interface, or stored to disk using pflogd(8).

     The pflog0 interface is created automatically at boot if both pf(4) and pflogd(8) are enabled; further instances can be created using
     ifconfig(8).

     Each packet retrieved on this interface has a header associated with it of length PFLOG_HDRLEN.  This header documents the address family,
     interface name, rule number, reason, action, and direction of the packet that was logged.  This structure, defined in <net/if_pflog.h> looks
     like

           struct pfloghdr {
                   u_int8_t        length;
                   sa_family_t     af;
                   u_int8_t        action;
                   u_int8_t        reason;
                   char            ifname[IFNAMSIZ];
                   char            ruleset[PF_RULESET_NAME_SIZE];
                   u_int32_t       rulenr;
                   u_int32_t       subrulenr;
                   uid_t           uid;
                   pid_t           pid;
                   uid_t           rule_uid;
                   pid_t           rule_pid;
                   u_int8_t        dir;
                   u_int8_t        pad[3];
           };

EXAMPLES

     Create a pflog interface and monitor all packets logged on it:

           # ifconfig pflog1 up
           # tcpdump -n -e -ttt -i pflog1

SEE ALSO

     tcpdump(1) inet(4), inet6(4), netintro(4), pf(4), ifconfig(8), pflogd(8)

HISTORY

     The pflog device first appeared in OpenBSD 3.0.

BSD                                                              December 10, 2001                                                             BSD

Linux and UNIX Man Pages

ipresend(1) [freebsd man page]

Check Out this Related Man Page