Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 13 Jul 1997 13:08:52 -0400
From:      Matthew Hunt <mph@astro.psu.edu>
To:        Doug White <dwhite@resnet.uoregon.edu>
Cc:        mark abrenio <mabrenio@usa.net>, questions@FreeBSD.ORG
Subject:   Re: tcptrace
Message-ID:  <19970713130852.27665@astro.psu.edu>
In-Reply-To: <Pine.BSF.3.96.970712221453.6418I-100000@localhost>; from Doug White on Sat, Jul 12, 1997 at 10:16:26PM -0700
References:  <33C7757A.41C67EA6@usa.net> <Pine.BSF.3.96.970712221453.6418I-100000@localhost>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Sat, Jul 12, 1997 at 10:16:26PM -0700, Doug White wrote:

> I guess it depends on that tcptrace is processing....

The idea of tcptrace is to convert the packet-oriented output of
tcpdump and similar programs to a connection-oriented listing showing
details of a whole TCP connection at once.

Furthermore, I can verify the orignal poster's problem:

townhouse:~# tcptrace
must specify at least one file name
usage: tcptrace [args...]* dumpfile [more files]*
[...]
Supported Input File Formats:
        tcpdump          tcpdump -- Public domain program from LBL
        snoop            Sun Snoop -- Distributed with Solaris
        etherpeek        etherpeek -- Mac sniffer program
        netmetrix        Net Metrix -- Commercial program from HP
Version: Ostermann's tcptrace -- version 3.2.5 -- Wed Feb  5, 1997

townhouse:~# tcpdump -w foo -i ppp0

townhouse:~# tcptrace foo 
1 args remaining, starting with 'foo'
Ostermann's tcptrace -- version 3.2.5 -- Wed Feb  5, 1997

Running file 'foo'
Don't understand packet format (9)




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?19970713130852.27665>