Date: Mon, 03 Jan 2000 20:21:14 +0000 From: Joseph Scott <joseph.scott@owp.csus.edu> To: Jon Rust <jpr@vcnet.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: tcpdump => ascii Message-ID: <387104B9.8A32C05C@owp.csus.edu> References: <v04210153b4969f6e75fa@[209.239.239.22]> <38710103.AA8454FC@owp.csus.edu> <v0421015ab496b3772c51@[209.239.239.22]>
next in thread | previous in thread | raw e-mail | index | archive | help
Jon Rust wrote: > > At 8:05 PM +0000 1/3/00, Joseph Scott wrote: > >Jon Rust wrote: > >> > >> I used to run all BSD/OS machines. The version of tcpdump included > >> with BSD/OS used a flag, -X, to display the output (specifically, the > >> payload) in human readable format. Very useful. FreeBSD's tcpdump > >> doesn't seem to have such a flag. I'm attempting to watch an SMTP > >> session to what's going wrong with a user's attempt to send mail. How > >> can I decode the output? > > > > Personally I've always used tcpshow to do this ( in the ports > >collection ). However after looking that man page for tcpdump I > >believe the -d option will do the same thing that you saw with -X > > No, -d is for something totally different AFAICT. I'll check out tcpshow. Opps. You're right, my bad. -d displays the packet matching code in readable format, not the contents of the packets. Yeah, tcpshow then will do the trick. /usr/ports/net/tcpshow Sorry about that. -- Joseph Scott joseph.scott@owp.csus.edu Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?387104B9.8A32C05C>