Path: utzoo!attcan!uunet!wuarchive!mit-eddie!bu-cs!xylogics!loverso
From: loverso@Xylogics.COM (John Robert LoVerso)
Newsgroups: comp.bugs.4bsd
Subject: Re: A ping question and the infamous "sendto: No buffer space available" message
Message-ID: <7855@xenna.Xylogics.COM>
Date: 3 Dec 89 21:52:30 GMT
References: <1989Dec1.102932.15678@larouch.uucp> <4355@helios.ee.lbl.gov>
Reply-To: loverso@Xylogics.COM (John Robert LoVerso)
Organization: Xylogics, Inc., Burlington MA
Lines: 19

In article <4355@helios.ee.lbl.gov> leres@helios.ee.lbl.gov (Craig Leres) writes:
> Ralph Yozzo writes:
> > Has anyone run into a situation where "ping'ing" a host gives a
> > sendto:No buffer space available
> 
> Sometimes, you can reset the
> hardware by ifconfig'ing the interface down and then back up.

This will probably only work in 4.3tahoe and later, where a call to
if_flushq() was added to if_down().  This just frees all the packet
chains queued for the interface - without this, ifconfig'ing back up
just leaves the i/f queue full.

Some useful information can be gleamed with the "ifnet" adb script
(in /usr/lib/adb), which will show you (among other things) the size
of the i/f queue.  This should work on any reasonable machine providing
a /dev/kmem.  On an Annex, "netstat -iQ" gives the queue size.

John