Date: Wed, 3 May 1995 12:30:02 -0700 From: System Operator <operator@alano.diatel.upm.es> To: freebsd-bugs Subject: kern/379: Using tcpdump with DC21040 Ethernet card halts network Message-ID: <199505031930.MAA11645@freefall.cdrom.com> In-Reply-To: Your message of Wed, 3 May 1995 21:20:14 %2B0200 <199505031920.VAA00437@alano.diatel.upm.es>
next in thread | previous in thread | raw e-mail | index | archive | help
>Number: 379 >Category: kern >Synopsis: Using tcpdump with DC21040 Ethernet card halts network >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs (FreeBSD bugs mailing list) >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed May 3 12:30:01 1995 >Originator: Javier Martin Rueda >Organization: >Release: FreeBSD 2.1.0-Development i386 >Environment: 950412-SNAP >Description: I wanted to look at the packets received from a certain host on the net, so I decided to use tcpdump for this. However, when I started tcpdump, the kernel wrote to the console the following message: de0: enabling 10baseT/UTP port And from then on, all network connectivity is halted. The console still works, but the ethernet card doesn't (no more telnet, ftp, not even ping). Note that when the computer boots and the ethernet card is probed and attached it says: de0: enabling Thinwire/AUI port So, it seems the kernel is trying to change the type of ethernet port to an incorrect one. My card is a SMC 8432BT (BNC and RJ45 connectors, though I only use the BNC). >How-To-Repeat: Execute the following command: tcpdump -i de0 -w file host myhost >Fix: Not known, sorry. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505031930.MAA11645>