What media, frames and protocols does the SCO port of tcpdump-3.0.4 support?
Frames: AppleTalk, ARP, DECNET, IP, IPX, RARP in an Ethernet type II, SNAP, 802.3, or FDDI frame
Protocols: TCP UDP BOOTP DNS EGP ICMP NFS NTP OSPF RIP SNMP SunRPC TFTP
tcpdump will start on the first NIC found in /dev/mdi that is not in use. If there are multiple available NICs, you can specify which one to use by running tcpdump with the -i option. See tcpdump.1 for more information.
tcpdump statistics
4 packets received by filter
2 packets dropped by kernel
If you are using the bpf STREAMS driver for filtering, each frame sent up from the MDI driver to bpf will increment the "received frame" statistic. If the bpf filter routine does not accept the frame (i.e. you only want to show certain types of frames) OR bpf encounters a STREAMS failure (see allocb(K)), then the "packets dropped by kernel" statistic will increment.
If you are using user level filtering, the "received by" statistic represents the number of frames received from the MDI driver. If the user level filter does not accept the frame as valid based on your filter then the "packets dropped by kernel" statistic will increment.
Legal Stuff
/*
* Copyright (c) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995
* The Regents of the University of California. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that: (1) source code distributions
* retain the above copyright notice and this paragraph in its entirety, (2)
* distributions including binary code include the above copyright notice and
* this paragraph in its entirety in the documentation or other materials
* provided with the distribution, and (3) all advertising materials mentioning
* features or use of this software display the following acknowledgement:
* ``This product includes software developed by the University of California,
* Lawrence Berkeley Laboratory and its contributors.'' Neither the name of
* the University nor the names of its contributors may be used to endorse
* or promote products derived from this software without specific prior
* written permission.
*
* Bootstrap Protocol (BOOTP). RFC951 and RFC1048.
*
* This file specifies the "implementation-independent" BOOTP protocol
* information which is common to both client and server.
*
* Copyright 1988 by Carnegie Mellon.
*
* Permission to use, copy, modify, and distribute this program for any
* purpose and without fee is hereby granted, provided that this copyright
* and permission notice appear on all copies and supporting documentation,
* the name of Carnegie Mellon not be used in advertising or publicity
* pertaining to distribution of the program without specific prior
* permission, and notice be given in supporting documentation that copying
* and distribution is by permission of Carnegie Mellon and Stanford
* University. Carnegie Mellon makes no representations about the
* suitability of this software for any purpose. It is provided "as is"
* without express or implied warranty.
*
* Copyright (c) 1990, 1991, 1993, 1994
* John Robert LoVerso. All rights reserved.
*
* Redistribution and use in source and binary forms are permitted
* provided that the above copyright notice and this paragraph are
* duplicated in all such forms and that any documentation,
* advertising materials, and other materials related to such
* distribution and use acknowledge that the software was developed
* by John Robert LoVerso.
*
* Copyright, 1990. The Regents of the University of California.
* This software was produced under a U.S. Government contract
* (W-7405-ENG-36) by Los Alamos National Laboratory, which is
* operated by the University of California for the U.S. Department
* of Energy. The U.S. Government is licensed to use, reproduce,
* and distribute this software. Permission is granted to the
* public to copy and use this software without charge, provided
* that this Notice and any statement of authorship are reproduced
* on all copies. Neither the Government nor the University makes
* any warranty, express or implied, or assumes any liability or
* responsibility for the use of this software.
* @(#)snmp.awk.x 1.1 (LANL) 1/15/90
*/
THIS SOFTWARE IS PROVIDED BY THE THE SANTA CRUZ OPERATION ("SCO") ``AS IS''
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL SCO BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
- THE END -
Here is the original README for tcpdump.
---cut paste glue---
@(#) $Header: README,v 1.39+ 94/06/20 20:15:16 leres Exp $ (LBL)
TCPDUMP 3.0.4
Lawrence Berkeley Laboratory
Network Research Group
tcpdump@ee.lbl.gov
ftp://ftp.ee.lbl.gov/tcpdump-*.tar.Z
This directory contains source code for tcpdump, a tool for network
monitoring and data acquisition. The original distribution is
available via anonymous ftp to ftp.ee.lbl.gov, in tcpdump-*.tar.Z.
Tcpdump now uses libcap, a system-independent interface for
user-level packet capture. Before building tcpdump, you must
first retrieve and build libpcap, also from LBL, in:
ftp://ftp.ee.lbl.gov/libpcap-*.tar.Z.
Once libpcap is built (either install it or make sure it's in
../libpcap), you can build tcpdump using the procedure in the INSTALL
file.
Tcpdump and libpcap have been built and tested under SGI Irix 4.x & 5.2,
SunOS 4.x, Solaris 2.3, BSD/386 v1.1, DEC/OSF v1.3 v2.0, and Ultrix 4.x.
SunOS 3.5, 4.3BSD Reno/Tahoe and 4.4BSD are supported as well, but we
currently do not have the resources to carry out testing in these
environments (we suspect you'll run into problems building the most
recent version under these systems -- please send us the patches if
you fix any porting problems).
Tcpdump has reportedly been ported to Mach 3.0 and Linux, but we have
not received patches to integrate back into the master source tree.
The program is loosely based on SMI's "etherfind" although none
of the etherfind code remains. It was originally written by Van
Jacobson as part of an ongoing research project to investigate and
improve tcp and internet gateway performance. The parts of the
program originally taken from Sun's etherfind were later re-written
by Steven McCanne of LBL. To insure that there would be no vestige
of proprietary code in tcpdump, Steve wrote these pieces from the
specification given by the manual entry, with no access to the
source of tcpdump or etherfind.
Over the past few years, tcpdump has been steadily improved
by the excellent contributions from the Internet community
(just browse through the CHANGES file). We are grateful for
all the input.
Richard Stevens gives an excellent treatment of the Internet
protocols in his book ``TCP/IP Illustrated, Volume 1''.
If you want to learn more about tcpdump and how to interpret
it's output, pick up this book.
Problems, bugs, questions, desirable enhancements, etc., should be
sent to the email address "tcpdump@ee.lbl.gov".
- Steve McCanne (mccanne@ee.lbl.gov)
Craig Leres (leres@ee.lbl.gov)
Van Jacobson (van@ee.lbl.gov)
-------------------------------------
This directory also contains some short awk programs intended as
examples of ways to reduce tcpdump data when you're tracking
particular network problems:
send-ack.awk
Simplifies the tcpdump trace for an ftp (or other unidirectional
tcp transfer). Since we assume that one host only sends and
the other only acks, all address information is left off and
we just note if the packet is a "send" or an "ack".
There is one output line per line of the original trace.
Field 1 is the packet time in decimal seconds, relative
to the start of the conversation. Field 2 is delta-time
from last packet. Field 3 is packet type/direction.
"Send" means data going from sender to receiver, "ack"
means an ack going from the receiver to the sender. A
preceding "*" indicates that the data is a retransmission.
A preceding "-" indicates a hole in the sequence space
(i.e., missing packet(s)), a "#" means an odd-size (not max
seg size) packet. Field 4 has the packet flags
(same format as raw trace). Field 5 is the sequence
number (start seq. num for sender, next expected seq number
for acks). The number in parens following an ack is
the delta-time from the first send of the packet to the
ack. A number in parens following a send is the
delta-time from the first send of the packet to the
current send (on duplicate packets only). Duplicate
sends or acks have a number in square brackets showing
the number of duplicates so far.
Here is a short sample from near the start of an ftp:
3.00 0.20 send . 512
3.20 0.20 ack . 1024 (0.20)
3.20 0.00 send P 1024
3.40 0.20 ack . 1536 (0.20)
3.80 0.40 * send . 0 (3.80) [2]
3.82 0.02 * ack . 1536 (0.62) [2]
Three seconds into the conversation, bytes 512 through 1023
were sent. 200ms later they were acked. Shortly thereafter
bytes 1024-1535 were sent and again acked after 200ms.
Then, for no apparent reason, 0-511 is retransmitted, 3.8
seconds after its initial send (the round trip time for this
ftp was 1sec, +-500ms). Since the receiver is expecting
1536, 1536 is re-acked when 0 arrives.
packetdat.awk
Computes chunk summary data for an ftp (or similar
unidirectional tcp transfer). [A "chunk" refers to
a chunk of the sequence space -- essentially the packet
sequence number divided by the max segment size.]
A summary line is printed showing the number of chunks,
the number of packets it took to send that many chunks
(if there are no lost or duplicated packets, the number
of packets should equal the number of chunks) and the
number of acks.
Following the summary line is one line of information
per chunk. The line contains eight fields:
1 - the chunk number
2 - the start sequence number for this chunk
3 - time of first send
4 - time of last send
5 - time of first ack
6 - time of last ack
7 - number of times chunk was sent
8 - number of times chunk was acked
(all times are in decimal seconds, relative to the start
of the conversation.)
As an example, here is the first part of the output for
an ftp trace:
# 134 chunks. 536 packets sent. 508 acks.
1 1 0.00 5.80 0.20 0.20 4 1
2 513 0.28 6.20 0.40 0.40 4 1
3 1025 1.16 6.32 1.20 1.20 4 1
4 1561 1.86 15.00 2.00 2.00 6 1
5 2049 2.16 15.44 2.20 2.20 5 1
6 2585 2.64 16.44 2.80 2.80 5 1
7 3073 3.00 16.66 3.20 3.20 4 1
8 3609 3.20 17.24 3.40 5.82 4 11
9 4097 6.02 6.58 6.20 6.80 2 5
This says that 134 chunks were transferred (about 70K
since the average packet size was 512 bytes). It took
536 packets to transfer the data (i.e., on the average
each chunk was transmitted four times). Looking at,
say, chunk 4, we see it represents the 512 bytes of
sequence space from 1561 to 2048. It was first sent
1.86 seconds into the conversation. It was last
sent 15 seconds into the conversation and was sent
a total of 6 times (i.e., it was retransmitted every
2 seconds on the average). It was acked once, 140ms
after it first arrived.
stime.awk
atime.awk
Output one line per send or ack, respectively, in the form