From owner-freebsd-questions Thu Dec 16 17:14:13 1999 Delivered-To: freebsd-questions@freebsd.org Received: from boom.firecracker.com (opscntr.dbq.mwci.net [209.207.4.33]) by hub.freebsd.org (Postfix) with ESMTP id 8A01F14C9D for ; Thu, 16 Dec 1999 17:14:07 -0800 (PST) (envelope-from jbutt@mwci.net) Received: from opscntr.dbq.mwci.net (opscntr.dbq.mwci.net [209.207.4.33]) by boom.firecracker.com (8.8.8/8.8.8) with SMTP id TAA28173; Thu, 16 Dec 1999 19:02:21 -0600 (CST) (envelope-from jbutt@mwci.net) Date: Thu, 16 Dec 1999 19:02:20 -0600 (CST) From: "James D. Butt 'J.D'" X-Sender: jbutt@boom.firecracker.com To: Nathaniel Schein Cc: Stephen Bader , freebsd-questions@FreeBSD.ORG Subject: RE: Network Connectivity Problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is a serious problem that I encountered once with a 3C509 NIC (ep0) on > 3.3-RELEASE. The network would just stop working after 3-4hours. I solved > the problem only after installing 3.2-Stable and making world. I don't know > if the make world was necessary but I did it for good measure. Since, the > system is rock solid and is being used for internal DNS, Sendmail and the We have had the problem with FreeBSD 2.2.5-Release and 3.3-Stable and BSDI 2.0 with 3c509c's and cheap ne2k's.. I always assume that it was due to either bad netcard code or more than likely crap nic's....as we have never seen this on any SMC or tulip based nic's... my 2 cents.. -------------------------------------------------------------------------- James D. Butt 'J.D.' jbutt@mwci.net - jbutt@firecracker.com MidWest Communications, Inc. -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message