From skh@Hunter.COM  Tue Jul 30 14:05:15 1996
Received: from gatekeeper.hunter.com (gatekeeper.hunter.com [199.217.148.2])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA06820
          for <FreeBSD-gnats-submit@freebsd.org>; Tue, 30 Jul 1996 14:05:14 -0700 (PDT)
Received: (from skh@localhost) by gatekeeper.hunter.com (8.7.5/8.7.3) id QAA01408; Tue, 30 Jul 1996 16:04:24 -0500 (CDT)
Message-Id: <199607302104.QAA01408@gatekeeper.hunter.com>
Date: Tue, 30 Jul 1996 16:04:24 -0500 (CDT)
From: KHamilton@Hunter.COM
Reply-To: KHamilton@Hunter.COM
To: FreeBSD-gnats-submit@freebsd.org, Khamilton@Hunter.COM
Subject: Intel Pro 100B Rejects Packets
X-Send-Pr-Version: 3.2

>Number:         1446
>Category:       kern
>Synopsis:       Intel Pro/100B (fxp0/fxp1) interface drops all packets.
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jul 30 14:10:01 PDT 1996
>Closed-Date:    Tue Jul 30 19:09:13 PDT 1996
>Last-Modified:  Tue Jul 30 19:11:42 PDT 1996
>Originator:     Kent Hamilton
>Release:        FreeBSD 2.1.5-RELEASE i386
>Organization:
Hunter Engineering Company
>Environment:
Dual homed system.  Two Intel Pro/100B NIC's.  64MB RAM, Pentium 100.
FreeBSD 2.1.5-RELEASE (upgraded via source download from 2.1-STABLE).
Kernel config files or other info can be made available upon request.
>Description:
The system acts as a dual homed proxie firewall running TIS FWTK.
The network interface on the inside network will begin to ignore
all incoming packets.  I have swapped the inside NIC, the cables,
the hub port, and the PCI slot.  If you log on the console and
run any program which puts the card in promiscous mode or if you
up and down the interface it will begin accepting packets again.
This problem started with 2.1-STABLE on a sup from the last week
in June or first week in July.  I have tried updating first to the
latest stable (as of last week), then to 2.1.5-RELEASE.  The problem
still exists under both versions.
Sniffing the inside net shows that packets are still be routed 
to the card correctly but no reply packets are seen.
>How-To-Repeat:
Unknown, sorry.  It happens here at least twice a day now.

>Fix:
I'm running 'tcpdump -i fxp1 -c 5' from cron once every 15 minutes
at the moment to ensure the card resets.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: davidg 
State-Changed-When: Tue Jul 30 19:09:13 PDT 1996 
State-Changed-Why:  
This problem is caused by a bug in the NIC that has been fixed in 
later steppings. It happens whenever the NIC receives garbage (such 
as happens when a cable is unplugged, or an interface is switched 
from 100 to 10Mbits on the same hub). It's not a software problem. 
>Unformatted:
