Date: Tue, 25 Jan 2000 23:42:05 +0000 From: Stuart Henderson <sthen@naiad.eclipse.net.uk> To: Archie Cobbs <archie@whistle.com> Cc: Stuart Henderson <sh@eclipse.net.uk>, Michael Robinson <robinson@netrinsics.com>, freebsd-security@FreeBSD.ORG Subject: Re: tcpdump Message-ID: <20000125234205.A6950@naiad.eclipse.net.uk> In-Reply-To: <200001252153.NAA66515@bubba.whistle.com>; from archie@whistle.com on Tue, Jan 25, 2000 at 01:53:18PM -0800 References: <388C79F9.1F129231@eclipse.net.uk> <200001252153.NAA66515@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 25, 2000 at 01:53:18PM -0800, Archie Cobbs wrote: > Stuart Henderson writes: > > > * (BTW, please don't send us patches to print the packet out in ascii) > > > > > > I've just finished with my latest version of such patches. Does that make > > > me some sort of E133t H4x0r or something? > > > > Not really, since the original tcpdump will spit forth ascii without > > much trouble anyway. (Your mod is better though, since you lose the decode > > of packet headers if you just do this by setting -w-). > > So.. how do you get tcpdump to spit forth ascii? Through a pipeline, using -l to line-buffer the output: # tcpdump -w - -s 2000 -l * | strings To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000125234205.A6950>