Date: Sun, 13 Jul 1997 21:32:33 -0700 (PDT) From: Doug White <dwhite@gdi.uoregon.edu> To: Matthew Hunt <mph@pobox.com> Cc: mark abrenio <mabrenio@usa.net>, questions@FreeBSD.ORG Subject: Re: tcptrace Message-ID: <Pine.BSF.3.96.970713213048.3780G-100000@localhost> In-Reply-To: <19970713130852.27665@astro.psu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 13 Jul 1997, Matthew Hunt wrote: > 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. Thanks for the clarify. The only thing I can think if is that the version of tcpdump in FreeBSD varies from the output that tcptrace is expecting. You might check the tcptrace docs and see if it requires certain flags. Also, make sure file 'foo' actually has valid data, perhaps you forgot to compile in bpf and the error is going into the file and not to the console. :) Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major Spam routed to /dev/null by Procmail | Death to Cyberpromo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970713213048.3780G-100000>