From owner-freebsd-questions Thu Aug 10 13:40:34 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id NAA23098 for questions-outgoing; Thu, 10 Aug 1995 13:40:34 -0700 Received: from orion.sirius.com (orion.sirius.com [140.174.229.12]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id NAA23090 for ; Thu, 10 Aug 1995 13:40:29 -0700 Received: (from jtmack@localhost) by orion.sirius.com (8.6.11/8.6.9) id NAA17751; Thu, 10 Aug 1995 13:40:15 -0700 Date: Thu, 10 Aug 1995 13:40:14 -0700 (PDT) From: Jim Mack To: questions@freebsd.org Subject: Device de0 dropping Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: questions-owner@freebsd.org Precedence: bulk Hi, I have a 486DX4 PCI machine with a Compex ReadyLink PCI ethernet card, Adaptec 1542 SCSI and some generic VGA video card. I am using the staple GENERIC kernel and have not tried recompiling yet on this system. The problem is, I have about 20 aliasesed IP addresses on the de0 interface and every day the device just seems to disappear and not receive or send any packets. I checked the messages before this happens and there is no indication of any errors occuring. Before I increased the memory and changed the network card I used to receive "mb_map full" errors. But since I put more memory in the "mb_map full" only pops up in the messages every 5th or so time the device decides to die. Sometimes I can even ifconfig down the device and then ifconfig the device back up with success. But when I do that the IP address that shows up when I do a 'ifconfig de0' as the local and broadcast are one of the aliased ones and not the original. Any ideas? Anymore information you want me to provide?. Thanks for listening. Jim Mack