From owner-freebsd-questions Fri Nov 13 12:36:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25724 for freebsd-questions-outgoing; Fri, 13 Nov 1998 12:36:38 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25718 for ; Fri, 13 Nov 1998 12:36:37 -0800 (PST) (envelope-from mruhl@cisco.com) Received: from cisco.com (corrupt.cisco.com [171.71.66.10]) by pita.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id MAA03592; Fri, 13 Nov 1998 12:36:14 -0800 (PST) Message-ID: <364C96FE.905F7A24@cisco.com> Date: Fri, 13 Nov 1998 12:30:54 -0800 From: "Michael J. Ruhl" Organization: Cisco Systems X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: kent@iastate.edu CC: freebsd-questions@FreeBSD.ORG Subject: Re: Tcpdump and errors References: <199811132031.OAA18947@isua2.iastate.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Vander Velden wrote: > > Hi. What must I do so that tcpdump shows me errors such as collisions, > babel, crc, etc? The card in the machine is an old isa no-name lnc type > device. > > Thanks. Hmm, I think that you misunderstand the purpose of tcpdump. I don't believe there is any way for tcpdump to show errors, it only shows the content of the network packets. If you want to see collisions, you should use netstat -i. Mike -------------------------------------------------------------- Michael J. Ruhl mruhl@cisco.com Cisco Systems Tall Blond Guy Buckaroo.Banzai@Yoyodyne.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message