Date: Mon, 14 Jul 1997 08:25:40 -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: <19970714082540.58698@astro.psu.edu> In-Reply-To: <Pine.BSF.3.96.970713213048.3780G-100000@localhost>; from Doug White on Sun, Jul 13, 1997 at 09:32:33PM -0700 References: <19970713130852.27665@astro.psu.edu> <Pine.BSF.3.96.970713213048.3780G-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 13, 1997 at 09:32:33PM -0700, Doug White wrote: > 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. :) I can eliminate the last possibility because I use tcpdump frequently, and it would have lost much of its entertainment value by now if it didn't work. :-) A couple of months ago, tcptrace would successfully consume the output of "tcpdump -w foo" without any special arguments. Granted, it segfaulted with annoying frequency, but it tried. My best guess, then, is that you may be right in that the output of FreeBSD's tcpdump might vary from what tcptrace wants. I may have to look into whether the output format has changed in the past few months. Matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970714082540.58698>