This repository has been archived by the owner on Oct 23, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 25
/
README
74 lines (53 loc) · 1.93 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
Fri May 25, 2001
Shawn Ostermann
ostermann@cs.ohiou.edu
tcptrace is a TCP connection analysis tool. It can tell you detailed
information about TCP connections by sifting through dump files. The
dump file formats supported are:
Standard tcpdump format (you need the pcap library)
Sun's snoop format
Macintosh Etherpeek format
HP/NetMetrix protocol analysis format
NS simulator output format
NetScout
NLANR Tsh Format
To see the graphs, you'll also need Tim Shepard's xplot program,
available at http://www.xplot.org
I've switched to using "./configure" to set up the Makefile. That
seems to have eased portability problems a great deal. Just say
"./configure" and then "make" to build the program.
Most of the rest of the Docs are on the web. Check out:
http://www.tcptrace.org/
Supported Platforms
-------------------
The program is developed here at OU on Sparc machines running Solaris
8. Our intention is that it also run under common Unix variants. In
particular, we try to test each release on the following platforms:
NetBSD
FreeBSD
Linux
Darwin/OSX (Mac)
Tru64 (Alpha)
We appreciate feedback and fixes on these or other platforms and will
attempt to modify the program to work on other platforms if we can get
enough help from people with access to those platforms and the changes
are not too "esthetically disagreeable".
Running the program
-------------------
Some simple examples:
0) What are the args and what do they mean???
tcptrace
1) Run the program quickly over a dump file
tcptrace dumpfile
2) Get longer output
tcptrace -l dumpfile
3) Generate lots of pretty plot files (you need xplot to see them)
tcptrace -G dumpfile
4) Print the segment contents as you go
tcptrace -p dumpfile
5) Print progress info (useful for large files)
tcptrace -t dumpfile
Of course, you can chain arguments together until you get just what
you want.
Let me know what you think....
Shawn