开发工具:Visual C++
上传日期:2003-09-19 14:40:56
上 传 者管理员
说明:  一个Window下的TCPDUMP源码
(Window under a TCPDUMP source)

WinDump (0, 2000-03-22)
WinDump\ACLOCAL.M4 (18834, 1999-05-19)
WinDump\addrtoname.c (17223, 1999-06-18)
WinDump\addrtoname.h (1758, 1999-05-19)
WinDump\appletalk.h (4290, 1999-05-19)
WinDump\ATIME.AWK (529, 1999-05-19)
WinDump\BOOTP.H (3677, 1999-05-19)
WinDump\BPF_DUMP.C (2166, 1999-05-19)
WinDump\CHANGES (17522, 1999-05-19)
WinDump\config.cache (2488, 1999-05-19)
WinDump\config.guess (21063, 1999-05-19)
WinDump\config.status (5652, 1999-05-19)
WinDump\CONFIG.SUB (20163, 1999-05-19)
WinDump\configure (89405, 1999-05-19)
WinDump\configure.in (4104, 1999-05-19)
WinDump\DECNET.H (17495, 1999-05-19)
WinDump\ethertype.h (2350, 1999-05-19)
WinDump\EXTRACT.H (2278, 1999-05-19)
WinDump\FDDI.H (2711, 1999-05-19)
WinDump\FILES (1394, 1999-05-19)
WinDump\gmt2local.c (2287, 1999-05-19)
WinDump\gmt2local.h (1310, 1999-05-19)
WinDump\IGRP.H (1057, 1999-05-19)
WinDump\INSTALL (6404, 1999-05-19)
WinDump\install-sh (5585, 1999-05-19)
WinDump\interface.h (7698, 1999-05-19)
WinDump\IPX.H (827, 1999-05-19)
WinDump\LBL (0, 2000-03-22)
WinDump\LBL\GNUC.H (780, 1999-05-19)
WinDump\LLC.H (3156, 1999-05-19)
WinDump\MACHDEP.C (1666, 1999-05-19)
WinDump\MACHDEP.H (1328, 1999-05-19)
WinDump\Makefile.in (4860, 1999-05-19)
WinDump\MAKEMIB (4413, 1999-05-19)
WinDump\MAN (0, 2000-03-22)
WinDump\MAN\TCPDUMP.MAN (64717, 1999-05-19)
WinDump\MAN\tcpdump.man.ps (76076, 1999-05-19)
WinDump\MIB.H (22458, 1999-05-19)
WinDump\MKDEP (2459, 1999-05-19)
WinDump\NETBIOS.H (281, 1999-05-19)
... ...

@(#) $Header: README,v 1.54 ***/01/27 21:36:20 vern Exp $ (LBL) TCPDUMP 3.4 Lawrence Berkeley National 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 libpcap, 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. 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 its output, pick up this book. Some tools for viewing and analyzing tcpdump trace files are available from the Internet Traffic Archive: http://www.acm.org/sigcomm/ITA/ Another tool that tcpdump users might find useful is tcpslice: ftp://ftp.ee.lbl.gov/tcpslice.tar.Z It is a program that can be used to extract portions of tcpdump binary trace files. See the above distribution for further details and documentation. Problems, bugs, questions, desirable enhancements, source code contributions, etc., should be sent to the email address "tcpdump@ee.lbl.gov". - Steve McCanne Craig Leres Van Jacobson ------------------------------------- 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.2 ... ...