| Server IP : 104.21.29.46 / Your IP : 216.73.216.123 Web Server : Apache System : Linux server1.morocco-tours.com 3.10.0-1127.19.1.el7.x86_64 #1 SMP Tue Aug 25 17:23:54 UTC 2020 x86_64 User : zagoradraa ( 1005) PHP Version : 7.4.33 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/wireshark/ |
Upload File : |
<?xml version="1.0" ?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>dumpcap - The Wireshark Network Analyzer 1.10.14</title> <link rel="stylesheet" href="../docbook/ws.css" type="text/css" /> <meta http-equiv="content-type" content="text/html; charset=utf-8" /> <link rev="made" href="mailto:root@localhost" /> </head> <body> <h1 id="NAME">NAME</h1> <p>dumpcap - Dump network traffic</p> <h1 id="SYNOPSIS">SYNOPSIS</h1> <p><b>dumpcap</b> <span style="white-space: nowrap;">[ <b>-a</b> <capture autostop condition> ] ...</span> <span style="white-space: nowrap;">[ <b>-b</b> <capture ring buffer option>] ...</span> <span style="white-space: nowrap;">[ <b>-B</b> <capture buffer size> ] </span> <span style="white-space: nowrap;">[ <b>-c</b> <capture packet count> ]</span> <span style="white-space: nowrap;">[ <b>-C</b> <byte limit> ]</span> <span style="white-space: nowrap;">[ <b>-d</b> ]</span> <span style="white-space: nowrap;">[ <b>-D</b> ]</span> <span style="white-space: nowrap;">[ <b>-f</b> <capture filter> ]</span> <span style="white-space: nowrap;">[ <b>-g</b> ]</span> <span style="white-space: nowrap;">[ <b>-h</b> ]</span> <span style="white-space: nowrap;">[ <b>-i</b> <capture interface>|rpcap://<host>/<capture interface>|TCP@<host>:<port>|- ]</span> <span style="white-space: nowrap;">[ <b>-I</b> ]</span> <span style="white-space: nowrap;">[ <b>-L</b> ]</span> <span style="white-space: nowrap;">[ <b>-M</b> ]</span> <span style="white-space: nowrap;">[ <b>-n</b> ]</span> <span style="white-space: nowrap;">[ <b>-N</b> <packet limit> ]</span> <span style="white-space: nowrap;">[ <b>-p</b> ]</span> <span style="white-space: nowrap;">[ <b>-P</b> ]</span> <span style="white-space: nowrap;">[ <b>-q</b> ]</span> <span style="white-space: nowrap;">[ <b>-s</b> <capture snaplen> ]</span> <span style="white-space: nowrap;">[ <b>-S</b> ]</span> <span style="white-space: nowrap;">[ <b>-t</b> ]</span> <span style="white-space: nowrap;">[ <b>-v</b> ]</span> <span style="white-space: nowrap;">[ <b>-w</b> <outfile> ]</span> <span style="white-space: nowrap;">[ <b>-y</b> <capture link type> ]</span></p> <h1 id="DESCRIPTION">DESCRIPTION</h1> <p><b>Dumpcap</b> is a network traffic dump tool. It lets you capture packet data from a live network and write the packets to a file. <b>Dumpcap</b>'s default capture file format is <b>pcap-ng</b> format. When the <b>-P</b> option is specified, the output file is written in the <b>pcap</b> format.</p> <p>Without any options set it will use the libpcap/WinPcap library to capture traffic from the first available network interface and writes the received raw packet data, along with the packets' time stamps into a pcap file.</p> <p>If the <b>-w</b> option is not specified, <b>Dumpcap</b> writes to a newly created pcap file with a randomly chosen name. If the <b>-w</b> option is specified, <b>Dumpcap</b> writes to the file specified by that option.</p> <p>Packet capturing is performed with the pcap library. The capture filter syntax follows the rules of the pcap library.</p> <h1 id="OPTIONS">OPTIONS</h1> <dl> <dt id="a-capture-autostop-condition">-a <capture autostop condition></dt> <dd> <p>Specify a criterion that specifies when <b>Dumpcap</b> is to stop writing to a capture file. The criterion is of the form <i>test</i><b>:</b><i>value</i>, where <i>test</i> is one of:</p> <p><b>duration</b>:<i>value</i> Stop writing to a capture file after <i>value</i> seconds have elapsed.</p> <p><b>filesize</b>:<i>value</i> Stop writing to a capture file after it reaches a size of <i>value</i> kB. If this option is used together with the -b option, dumpcap will stop writing to the current capture file and switch to the next one if filesize is reached. Note that the filesize is limited to a maximum value of 2 GiB.</p> <p><b>files</b>:<i>value</i> Stop writing to capture files after <i>value</i> number of files were written.</p> </dd> <dt id="b-capture-ring-buffer-option">-b <capture ring buffer option></dt> <dd> <p>Cause <b>Dumpcap</b> to run in "multiple files" mode. In "multiple files" mode, <b>Dumpcap</b> will write to several capture files. When the first capture file fills up, <b>Dumpcap</b> will switch writing to the next file and so on.</p> <p>The created filenames are based on the filename given with the <b>-w</b> option, the number of the file and on the creation date and time, e.g. outfile_00001_20050604120117.pcap, outfile_00002_20050604120523.pcap, ...</p> <p>With the <i>files</i> option it's also possible to form a "ring buffer". This will fill up new files until the number of files specified, at which point <b>Dumpcap</b> will discard the data in the first file and start writing to that file and so on. If the <i>files</i> option is not set, new files filled up until one of the capture stop conditions match (or until the disk is full).</p> <p>The criterion is of the form <i>key</i><b>:</b><i>value</i>, where <i>key</i> is one of:</p> <p><b>duration</b>:<i>value</i> switch to the next file after <i>value</i> seconds have elapsed, even if the current file is not completely filled up.</p> <p><b>filesize</b>:<i>value</i> switch to the next file after it reaches a size of <i>value</i> kB. Note that the filesize is limited to a maximum value of 2 GiB.</p> <p><b>files</b>:<i>value</i> begin again with the first file after <i>value</i> number of files were written (form a ring buffer). This value must be less than 100000. Caution should be used when using large numbers of files: some filesystems do not handle many files in a single directory well. The <b>files</b> criterion requires either <b>duration</b> or <b>filesize</b> to be specified to control when to go to the next file. It should be noted that each <b>-b</b> parameter takes exactly one criterion; to specify two criterion, each must be preceded by the <b>-b</b> option.</p> <p>Example: <b>-b filesize:1000 -b files:5</b> results in a ring buffer of five files of size one megabyte each.</p> </dd> <dt id="B-capture-buffer-size">-B <capture buffer size></dt> <dd> <p>Set capture buffer size (in MiB, default is 4 MiB). This is used by the capture driver to buffer packet data until that data can be written to disk. If you encounter packet drops while capturing, try to increase this size. Note that, while <b>Dumpcap</b> attempts to set the buffer size to 4 MiB by default, and can be told to set it to a larger value, the system or interface on which you're capturing might silently limit the capture buffer size to a lower value or raise it to a higher value.</p> <p>This is available on UNIX systems with libpcap 1.0.0 or later and on Windows. It is not available on UNIX systems with earlier versions of libpcap.</p> <p>This option can occur multiple times. If used before the first occurrence of the <b>-i</b> option, it sets the default capture buffer size. If used after an <b>-i</b> option, it sets the capture buffer size for the interface specified by the last <b>-i</b> option occurring before this option. If the capture buffer size is not set specifically, the default capture buffer size is used instead.</p> </dd> <dt id="c-capture-packet-count">-c <capture packet count></dt> <dd> <p>Set the maximum number of packets to read when capturing live data.</p> </dd> <dt id="C-byte-limit">-C <byte limit></dt> <dd> <p>Limit the amount of memory in bytes used for storing captured packets in memory while processing it. If used in combination with the <b>-N</b> option, both limits will apply. Setting this limit will enable the usage of the separate thread per interface.</p> </dd> <dt id="d">-d</dt> <dd> <p>Dump the code generated for the capture filter in a human-readable form, and exit.</p> </dd> <dt id="D">-D</dt> <dd> <p>Print a list of the interfaces on which <b>Dumpcap</b> can capture, and exit. For each network interface, a number and an interface name, possibly followed by a text description of the interface, is printed. The interface name or the number can be supplied to the <b>-i</b> option to specify an interface on which to capture.</p> <p>This can be useful on systems that don't have a command to list them (e.g., Windows systems, or UNIX systems lacking <b>ifconfig -a</b>); the number can be useful on Windows 2000 and later systems, where the interface name is a somewhat complex string.</p> <p>Note that "can capture" means that <b>Dumpcap</b> was able to open that device to do a live capture. Depending on your system you may need to run dumpcap from an account with special privileges (for example, as root) to be able to capture network traffic. If "<b>dumpcap -D</b>" is not run from such an account, it will not list any interfaces.</p> </dd> <dt id="f-capture-filter">-f <capture filter></dt> <dd> <p>Set the capture filter expression.</p> <p>The entire filter expression must be specified as a single argument (which means that if it contains spaces, it must be quoted).</p> <p>This option can occur multiple times. If used before the first occurrence of the <b>-i</b> option, it sets the default capture filter expression. If used after an <b>-i</b> option, it sets the capture filter expression for the interface specified by the last <b>-i</b> option occurring before this option. If the capture filter expression is not set specifically, the default capture filter expression is used if provided.</p> </dd> <dt id="g">-g</dt> <dd> <p>This option causes the output file(s) to be created with group-read permission (meaning that the output file(s) can be read by other members of the calling user's group).</p> </dd> <dt id="h">-h</dt> <dd> <p>Print the version and options and exits.</p> </dd> <dt id="i-capture-interface-rpcap:-host-capture-interface-TCP-host:port">-i <capture interface>|rpcap://<host>/<capture interface>|TCP@<host>:<port>|-</dt> <dd> <p>Set the name of the network interface or pipe to use for live packet capture.</p> <p>Network interface names should match one of the names listed in "<b>dumpcap -D</b>" (described above); a number, as reported by "<b>dumpcap -D</b>", can also be used. If you're using UNIX, "<b>netstat -i</b>" or "<b>ifconfig -a</b>" might also work to list interface names, although not all versions of UNIX support the <b>-a</b> option to <b>ifconfig</b>.</p> <p>If no interface is specified, <b>Dumpcap</b> searches the list of interfaces, choosing the first non-loopback interface if there are any non-loopback interfaces, and choosing the first loopback interface if there are no non-loopback interfaces. If there are no interfaces at all, <b>Dumpcap</b> reports an error and doesn't start the capture.</p> <p>Pipe names should be either the name of a FIFO (named pipe) or ``-'' to read data from the standard input. Data read from pipes must be in standard pcap format.</p> <p>This option can occur multiple times. When capturing from multiple interfaces, the capture file will be saved in pcap-ng format.</p> <p>Note: the Win32 version of <b>Dumpcap</b> doesn't support capturing from pipes or stdin!</p> </dd> <dt id="I">-I</dt> <dd> <p>Put the interface in "monitor mode"; this is supported only on IEEE 802.11 Wi-Fi interfaces, and supported only on some operating systems.</p> <p>Note that in monitor mode the adapter might disassociate from the network with which it's associated, so that you will not be able to use any wireless networks with that adapter. This could prevent accessing files on a network server, or resolving host names or network addresses, if you are capturing in monitor mode and are not connected to another network with another adapter.</p> <p>This option can occur multiple times. If used before the first occurrence of the <b>-i</b> option, it enables the monitor mode for all interfaces. If used after an <b>-i</b> option, it enables the monitor mode for the interface specified by the last <b>-i</b> option occurring before this option.</p> </dd> <dt id="L">-L</dt> <dd> <p>List the data link types supported by the interface and exit. The reported link types can be used for the <b>-y</b> option.</p> </dd> <dt id="M">-M</dt> <dd> <p>When used with <b>-D</b>, <b>-L</b> or <b>-S</b>, print machine-readable output. The machine-readable output is intended to be read by <b>Wireshark</b> and <b>TShark</b>; its format is subject to change from release to release.</p> </dd> <dt id="n">-n</dt> <dd> <p>Save files as pcap-ng. This is the default.</p> </dd> <dt id="N-packet-limit">-N <packet limit></dt> <dd> <p>Limit the number of packets used for storing captured packets in memory while processing it. If used in combination with the <b>-C</b> option, both limits will apply. Setting this limit will enable the usage of the separate thread per interface.</p> </dd> <dt id="p">-p</dt> <dd> <p><i>Don't</i> put the interface into promiscuous mode. Note that the interface might be in promiscuous mode for some other reason; hence, <b>-p</b> cannot be used to ensure that the only traffic that is captured is traffic sent to or from the machine on which <b>Dumpcap</b> is running, broadcast traffic, and multicast traffic to addresses received by that machine.</p> <p>This option can occur multiple times. If used before the first occurrence of the <b>-i</b> option, no interface will be put into the promiscuous mode. If used after an <b>-i</b> option, the interface specified by the last <b>-i</b> option occurring before this option will not be put into the promiscuous mode.</p> </dd> <dt id="P">-P</dt> <dd> <p>Save files as pcap instead of the default pcap-ng. In situations that require pcap-ng, such as capturing from multiple interfaces, this option will be overridden.</p> </dd> <dt id="q">-q</dt> <dd> <p>When capturing packets, don't display the continuous count of packets captured that is normally shown when saving a capture to a file; instead, just display, at the end of the capture, a count of packets captured. On systems that support the SIGINFO signal, such as various BSDs, you can cause the current count to be displayed by typing your "status" character (typically control-T, although it might be set to "disabled" by default on at least some BSDs, so you'd have to explicitly set it to use it).</p> </dd> <dt id="s-capture-snaplen">-s <capture snaplen></dt> <dd> <p>Set the default snapshot length to use when capturing live data. No more than <i>snaplen</i> bytes of each network packet will be read into memory, or saved to disk. A value of 0 specifies a snapshot length of 262144, so that the full packet is captured; this is the default.</p> <p>This option can occur multiple times. If used before the first occurrence of the <b>-i</b> option, it sets the default snapshot length. If used after an <b>-i</b> option, it sets the snapshot length for the interface specified by the last <b>-i</b> option occurring before this option. If the snapshot length is not set specifically, the default snapshot length is used if provided.</p> </dd> <dt id="S">-S</dt> <dd> <p>Print statistics for each interface once every second.</p> </dd> <dt id="t">-t</dt> <dd> <p>Use a separate thread per interface.</p> </dd> <dt id="v">-v</dt> <dd> <p>Print the version and exit.</p> </dd> <dt id="w-outfile">-w <outfile></dt> <dd> <p>Write raw packet data to <i>outfile</i>.</p> <p>NOTE: The usage of "-" for stdout is not allowed here!</p> </dd> <dt id="y-capture-link-type">-y <capture link type></dt> <dd> <p>Set the data link type to use while capturing packets. The values reported by <b>-L</b> are the values that can be used.</p> <p>This option can occur multiple times. If used before the first occurrence of the <b>-i</b> option, it sets the default capture link type. If used after an <b>-i</b> option, it sets the capture link type for the interface specified by the last <b>-i</b> option occurring before this option. If the capture link type is not set specifically, the default capture link type is used if provided.</p> </dd> </dl> <h1 id="CAPTURE-FILTER-SYNTAX">CAPTURE FILTER SYNTAX</h1> <p>See the manual page of pcap-filter(7) or, if that doesn't exist, tcpdump(8), or, if that doesn't exist, <a href="http://wiki.wireshark.org/CaptureFilters">http://wiki.wireshark.org/CaptureFilters</a>.</p> <h1 id="SEE-ALSO">SEE ALSO</h1> <p>wireshark(1), tshark(1), editcap(1), mergecap(1), capinfos(1), pcap(3), pcap-filter(7) or tcpdump(8)</p> <h1 id="NOTES">NOTES</h1> <p><b>Dumpcap</b> is part of the <b>Wireshark</b> distribution. The latest version of <b>Wireshark</b> can be found at <a href="http://www.wireshark.org">http://www.wireshark.org</a>.</p> <p>HTML versions of the Wireshark project man pages are available at: <a href="http://www.wireshark.org/docs/man-pages">http://www.wireshark.org/docs/man-pages</a>.</p> <h1 id="AUTHORS">AUTHORS</h1> <p><b>Dumpcap</b> is derived from the <b>Wireshark</b> capturing engine code; see the list of authors in the <b>Wireshark</b> man page for a list of authors of that code.</p> </body> </html>
| .. | |||||
| diameter | |||||
| dtds | |||||
| help | |||||
| profiles | |||||
| radius | |||||
| tpncp | |||||
| wimaxasncp | |||||
| AUTHORS-SHORT | |||||
| COPYING | |||||
| capinfos.html | |||||
| cfilters | |||||
| colorfilters | |||||
| console.lua | |||||
| dfilters | |||||
| dftest.html | |||||
| dtd_gen.lua | |||||
| dumpcap.html | |||||
| editcap.html | |||||
| ipmap.html | |||||
| manuf | |||||
| mergecap.html | |||||
| pdml2html.xsl | |||||
| randpkt.html | |||||
| rawshark.html | |||||
| reordercap.html | |||||
| services | |||||
| smi_modules | |||||
| text2pcap.html | |||||
| tshark.html | |||||
| wireshark-filter.html | |||||
| wireshark.html | |||||
| ws.css |