| README (56893) | README (75115) |
|---|---|
| 1@(#) $Header: /tcpdump/master/tcpdump/README,v 1.54.1.1 1999/10/07 23:47:09 mcr Exp $ (LBL) | 1@(#) $Header: /tcpdump/master/tcpdump/README,v 1.58 2000/12/08 06:59:11 mcr Exp $ (LBL) |
| 2 | 2 |
| 3TCPDUMP 3.4 4Lawrence Berkeley National Laboratory 5Network Research Group 6tcpdump@ee.lbl.gov 7ftp://ftp.ee.lbl.gov/tcpdump.tar.Z | 3TCPDUMP 3.6 4Now maintained by "The Tcpdump Group" 5See www.tcpdump.org |
| 8 | 6 |
| 7Please send inquiries/comments/reports to tcpdump-workers@tcpdump.org 8 9Anonymous CVS is available via: 10 cvs -d cvs.tcpdump.org:/tcpdump/master login 11 (password "anoncvs") 12 cvs -d cvs.tcpdump.org:/tcpdump/master checkout tcpdump 13 14Version 3.6 of TCPDUMP can be retrived with the CVS tag "tcpdump_3_6": 15 cvs -d cvs.tcpdump.org:/tcpdump/master checkout -r tcpdump_3_6 tcpdump 16 17Please send patches against the master copy to patches@tcpdump.org. 18 19formerly from Lawrence Berkeley National Laboratory 20 Network Research Group <tcpdump@ee.lbl.gov> 21 ftp://ftp.ee.lbl.gov/tcpdump.tar.Z (3.4) 22 |
|
| 9This directory contains source code for tcpdump, a tool for network | 23This directory contains source code for tcpdump, a tool for network |
| 10monitoring and data acquisition. The original distribution is 11available via anonymous ftp to ftp.ee.lbl.gov, in tcpdump.tar.Z. | 24monitoring and data acquisition. This software was originally 25developed by the Network Research Group at the Lawrence Berkeley 26National Laboratory. The original distribution is available via 27anonymous ftp to ftp.ee.lbl.gov, in tcpdump.tar.Z. More recent 28development is performed at tcpdump.org, http://www.tcpdump.org/ |
| 12 | 29 |
| 13Tcpdump now uses libpcap, a system-independent interface for user-level | 30Tcpdump uses libpcap, a system-independent interface for user-level |
| 14packet capture. Before building tcpdump, you must first retrieve and | 31packet capture. Before building tcpdump, you must first retrieve and |
| 15build libpcap, also from LBL, in: | 32build libpcap, also originally from LBL and now being maintained by 33tcpdump.org; see http://www.tcpdump.org/ . |
| 16 | 34 |
| 17 ftp://ftp.ee.lbl.gov/libpcap.tar.Z 18 | |
| 19Once libpcap is built (either install it or make sure it's in 20../libpcap), you can build tcpdump using the procedure in the INSTALL 21file. 22 23The program is loosely based on SMI's "etherfind" although none of the 24etherfind code remains. It was originally written by Van Jacobson as 25part of an ongoing research project to investigate and improve tcp and 26internet gateway performance. The parts of the program originally --- 18 unchanged lines hidden (view full) --- 45Another tool that tcpdump users might find useful is tcpslice: 46 47 ftp://ftp.ee.lbl.gov/tcpslice.tar.Z 48 49It is a program that can be used to extract portions of tcpdump binary 50trace files. See the above distribution for further details and 51documentation. 52 | 35Once libpcap is built (either install it or make sure it's in 36../libpcap), you can build tcpdump using the procedure in the INSTALL 37file. 38 39The program is loosely based on SMI's "etherfind" although none of the 40etherfind code remains. It was originally written by Van Jacobson as 41part of an ongoing research project to investigate and improve tcp and 42internet gateway performance. The parts of the program originally --- 18 unchanged lines hidden (view full) --- 61Another tool that tcpdump users might find useful is tcpslice: 62 63 ftp://ftp.ee.lbl.gov/tcpslice.tar.Z 64 65It is a program that can be used to extract portions of tcpdump binary 66trace files. See the above distribution for further details and 67documentation. 68 |
| 53Problems, bugs, questions, desirable enhancements, source code 54contributions, etc., should be sent to the email address 55"tcpdump@ee.lbl.gov". | 69Problems, bugs, questions, desirable enhancements, etc. 70should be sent to the address "tcpdump-workers@tcpdump.org". |
| 56 | 71 |
| 57 - Steve McCanne 58 Craig Leres 59 Van Jacobson | 72Source code contributions, etc. should be sent to the email address 73"patches@tcpdump.org". 74 75Current versions can be found at www.tcpdump.org 76 77 - The TCPdump team 78 79original text by: Steve McCanne, Craig Leres, Van Jacobson 80 |
| 60------------------------------------- 61This directory also contains some short awk programs intended as 62examples of ways to reduce tcpdump data when you're tracking 63particular network problems: 64 65send-ack.awk 66 Simplifies the tcpdump trace for an ftp (or other unidirectional 67 tcp transfer). Since we assume that one host only sends and --- 132 unchanged lines hidden (view full) --- 200 at the data. 201 202 - Change something in the local protocol implementation and 203 redo the steps above. 204 205 - Once a week, tell your funding agent that you're discovering 206 wonderful things and you'll write up that research report 207 "real soon now". | 81------------------------------------- 82This directory also contains some short awk programs intended as 83examples of ways to reduce tcpdump data when you're tracking 84particular network problems: 85 86send-ack.awk 87 Simplifies the tcpdump trace for an ftp (or other unidirectional 88 tcp transfer). Since we assume that one host only sends and --- 132 unchanged lines hidden (view full) --- 221 at the data. 222 223 - Change something in the local protocol implementation and 224 redo the steps above. 225 226 - Once a week, tell your funding agent that you're discovering 227 wonderful things and you'll write up that research report 228 "real soon now". |
| 208 | |