From owner-freebsd-current Tue Nov 5 22:41:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA23523 for current-outgoing; Tue, 5 Nov 1996 22:41:08 -0800 (PST) Received: from dcs.stu.rpi.edu (kdupuis@dcs.stu.rpi.edu [128.113.161.29]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA23516 for ; Tue, 5 Nov 1996 22:41:05 -0800 (PST) Received: from localhost (kdupuis@localhost) by dcs.stu.rpi.edu (8.7.6/8.7.3) with SMTP id BAA01280 for ; Wed, 6 Nov 1996 01:40:55 -0500 (EST) Date: Wed, 6 Nov 1996 01:40:54 -0500 (EST) From: "Kenneth J. Dupuis" To: freebsd-current@freebsd.org Subject: 2.2-961014 and 3c590 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Update on the ethernet card from hell... I'm able to simulate the problem whenever I want by either 1) FTPing from the machine 2) HTTPing from the machine 3) ping flooding with 1000 byte packets to or from the machine. When the network ceases to work, a simple ping to the next-door neighbor results in a "No buffer space available". I can now "ifconfig vx0 down" and then "ifconfig vx0 up" the interface and all is well until I do it again. ifconfig reports a "OACTIVE" flag when the interface is "flooded", or whatever the case may be. Does someone know what is going on here? What does that flag mean?