From owner-freebsd-questions Sun Jul 13 10:09:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA28875 for questions-outgoing; Sun, 13 Jul 1997 10:09:07 -0700 (PDT) Received: from nexus.astro.psu.edu (nexus.astro.psu.edu [128.118.147.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA28870 for ; Sun, 13 Jul 1997 10:09:03 -0700 (PDT) Received: from mstar.astro.psu.edu by nexus.astro.psu.edu (4.1/Nexus-1.3) id AA26091; Sun, 13 Jul 97 13:08:57 EDT Received: by mstar.astro.psu.edu (SMI-8.6/Client-1.3) id NAA22053; Sun, 13 Jul 1997 13:08:52 -0400 Message-Id: <19970713130852.27665@astro.psu.edu> Date: Sun, 13 Jul 1997 13:08:52 -0400 From: Matthew Hunt To: Doug White Cc: mark abrenio , questions@FreeBSD.ORG Subject: Re: tcptrace Reply-To: Matthew Hunt References: <33C7757A.41C67EA6@usa.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: ; from Doug White on Sat, Jul 12, 1997 at 10:16:26PM -0700 Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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)