From owner-freebsd-bugs Tue Jul 30 14:10:48 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA07198 for bugs-outgoing; Tue, 30 Jul 1996 14:10:48 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA07183; Tue, 30 Jul 1996 14:10:22 -0700 (PDT) Resent-Date: Tue, 30 Jul 1996 14:10:22 -0700 (PDT) Resent-Message-Id: <199607302110.OAA07183@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, KHamilton@Hunter.COM 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 ; 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 X-Send-Pr-Version: 3.2 Subject: kern/1446: Intel Pro 100B Rejects Packets Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 1446 >Category: kern >Synopsis: Intel Pro/100B (fxp0/fxp1) interface drops all packets. >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jul 30 14:10:01 PDT 1996 >Last-Modified: >Originator: Kent Hamilton >Organization: Hunter Engineering Company >Release: FreeBSD 2.1.5-RELEASE i386 >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. >Audit-Trail: >Unformatted: