From owner-freebsd-questions Mon Jan 3 12:16:27 2000 Delivered-To: freebsd-questions@freebsd.org Received: from vcnet.com (mail.vcnet.com [209.239.239.15]) by hub.freebsd.org (Postfix) with SMTP id 9CA5C14A04 for ; Mon, 3 Jan 2000 12:16:21 -0800 (PST) (envelope-from jpr@vcnet.com) Received: (qmail 50784 invoked from network); 3 Jan 2000 20:16:18 -0000 Received: from joff.vc.net (HELO ?209.239.239.22?) (209.239.239.22) by mail.vcnet.com with SMTP; 3 Jan 2000 20:16:18 -0000 Mime-Version: 1.0 Message-Id: In-Reply-To: <38710103.AA8454FC@owp.csus.edu> References: <38710103.AA8454FC@owp.csus.edu> Date: Mon, 3 Jan 2000 12:14:14 -0800 To: Joseph Scott From: Jon Rust Subject: Re: tcpdump => ascii Cc: freebsd-questions@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. Thanks, jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message