This is automatically generated documentation. Edit after the "COMMENTS" heading; changes to the main body will be lost.
FromTcpdump -- Click element; reads packets from an ASCII tcpdump output file
FromTcpdump(FILENAME [, KEYWORDS])
Ports: no inputs, 1 output
Package: analysis (core)
Reads textual TCP/IP packet descriptors from an ASCII tcpdump output file,
then creates packets resembling those descriptors and pushes them out the
output. Optionally stops the driver when there are no more packets.
The file may be compressed with gzip(1) or bzip2(1); FromTcpdump will
run zcat(1) or bzcat(1) to uncompress it.
FromTcpdump reads from the file named FILENAME unless FILENAME is a
single dash `
-', in which case it reads from the standard input. It will
not uncompress the standard input, however.
FromTcpdump doesn't parse many of the relevant parts of the file. It handles
fragments badly, for example. Mostly it just does TCP and some rudimentary
Keyword arguments are:
active' handler is written). Default is true.
sampling_probhandler to find out the actual probability. If MULTIPACKET is true, then the sampling probability applies separately to the multiple packets generated per record. Only available in user-level processes.
FromTcpdump is a notifier signal, active when the element is active and the dump contains more packets. tcpdump's binary output is generally much better than the output of FromTcpdump. Unfortunately, some people just throw it away.
Generated by 'click-elem2man' from '../elements/analysis/fromtcpdump.hh' on 24/May/2007.