From owner-freebsd-questions@FreeBSD.ORG Tue Jun 17 06:09:23 2003 Return-Path: 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 E870A37B401 for ; Tue, 17 Jun 2003 06:09:23 -0700 (PDT) Received: from pa-plum1b-166.pit.adelphia.net (pa-plum1b-217.pit.adelphia.net [24.53.161.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3582F43FA3 for ; Tue, 17 Jun 2003 06:09:23 -0700 (PDT) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com (working [172.16.0.95]) h5HD9MOg005478; Tue, 17 Jun 2003 09:09:22 -0400 (EDT) (envelope-from wmoran@potentialtech.com) Message-ID: <3EEF1302.8060908@potentialtech.com> Date: Tue, 17 Jun 2003 09:09:22 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030429 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jaime References: <20030617075240.L94567@malkav.snowmoon.com> In-Reply-To: <20030617075240.L94567@malkav.snowmoon.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2003 13:09:24 -0000 Jaime wrote: > I've been noticing for a few days that my network's performance is > less than good. When I checked on it, I found that the firewall > attempting to ping the ISP's DNS resolver would have "hiccups." The ISP > claims that there is nothing wrong on the T-1 line and that there is a > problem on the ethernet interface of the router (which leads to the > firewall). > > The pings will run just fine for several minutes at a time and > then begin to output this: > > ping: sendto: No buffer space available > > This will go on for anywhere from 15 seconds to 5 minutes, during > which we're effectively not connected to the Internet at all. An > occasional ping will work, but only about 1 in 20 and it seems random. > Then, just as suddenly, the connection will work again. > > I'm not completely sure what this means, but I found the following > command in the mailing list archives: > > cerberus# sysctl -a | grep intr_qu > net.inet.ip.intr_queue_maxlen: 50 > net.inet.ip.intr_queue_drops: 6987 > > Does anyone have any suggestions or tips? What make/model of NIC are you using? 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. -- Bill Moran Potential Technologies http://www.potentialtech.com