From owner-freebsd-questions@FreeBSD.ORG  Tue Jun 17 06:33:58 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EBCD837B401
	for <freebsd-questions@freebsd.org>;
	Tue, 17 Jun 2003 06:33:58 -0700 (PDT)
Received: from malkav.snowmoon.com (malkav.snowmoon.com [209.23.60.62])
	by mx1.FreeBSD.org (Postfix) with SMTP id 168EB43FA3
	for <freebsd-questions@freebsd.org>;
	Tue, 17 Jun 2003 06:33:58 -0700 (PDT)
	(envelope-from jaime@snowmoon.com)
Received: (qmail 95276 invoked from network); 17 Jun 2003 13:33:56 -0000
Received: from localhost.snowmoon.com (HELO localhost) (127.0.0.1)
  by localhost.snowmoon.com with SMTP; 17 Jun 2003 13:33:56 -0000
Date: Tue, 17 Jun 2003 09:33:55 -0400 (EDT)
From: jaime@snowmoon.com
To: Bill Moran <wmoran@potentialtech.com>
In-Reply-To: <3EEF1302.8060908@potentialtech.com>
Message-ID: <20030617092913.J94567@malkav.snowmoon.com>
References: <20030617075240.L94567@malkav.snowmoon.com>
	<3EEF1302.8060908@potentialtech.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-questions@freebsd.org
Subject: Re: ping: sendto: No buffer space available
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jun 2003 13:33:59 -0000

On Tue, 17 Jun 2003, Bill Moran wrote:
> What make/model of NIC are you using?

cerberus# ifconfig -a
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 10.0.3.2 netmask 0xffffff00 broadcast 10.0.3.255
        ether 00:e0:81:21:45:8c
        media: Ethernet autoselect (10baseT/UTP)
        status: active
fxp1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 10.1.1.1 netmask 0xffff0000 broadcast 10.1.255.255
        ether 00:e0:81:21:45:8d
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet 127.0.0.1 netmask 0xff000000

	The interface in question is 10.0.3.2.  That interface has worked
fine for over a year.  That driver is in use on several other systems for
several years each.  No problems until now.


> The only time I've ever seen this, the only thing that solved the problem
> was swapping the network card out for a better one.
> That's not to say it isn't a driver problem, as the new network card used
> a different driver as well.

	I think that the NIC is on the logic board.  I can try to install
a PCI card and use that in its place to see if the problem goes away.
Should I bother?

	FWIW, a reboot of the system did not help.

						Jaime