From owner-freebsd-current@FreeBSD.ORG Fri Apr 22 18:22:47 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12D3E16A4CE for ; Fri, 22 Apr 2005 18:22:47 +0000 (GMT) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6B7043D3F for ; Fri, 22 Apr 2005 18:22:46 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.12.8) with ESMTP id j3MIMksG070624; Fri, 22 Apr 2005 11:22:46 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id j3MIMkPc070623; Fri, 22 Apr 2005 11:22:46 -0700 (PDT) (envelope-from rizzo) Date: Fri, 22 Apr 2005 11:22:46 -0700 From: Luigi Rizzo To: Randy Bush Message-ID: <20050422112246.A70611@xorpc.icir.org> References: <17001.9557.627987.505930@roam.psg.com> <17001.16520.774703.612151@roam.psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <17001.16520.774703.612151@roam.psg.com>; from randy@psg.com on Fri, Apr 22, 2005 at 08:20:56AM -1000 cc: FreeBSD Current Subject: Re: significant increase in ipfw pullup failed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 18:22:47 -0000 wonder if it is related to the recent import of ipfw v6 support... cheers luigi On Fri, Apr 22, 2005 at 08:20:56AM -1000, Randy Bush wrote: > >> on a 1ru system with an fxp > >> yesterday, i cvsupped Apr 21 17:00 and built, first time in a few weeks > >> previously i got an ipfw pullup failed a couple of times a day > >> now i get them every few minutes > >> > >> anyone else seeing this, or should i start to send someone into > >> the colo to check cables? > > > > What it means is that the IPFW code didn't see a long enough packet to > > contain enough data to be logged usefully. That could be a sign of > > hardware problems like a flaky cable or a NIC that is going wonky: if > > you can check "netstat -i" and look for excessive input errors or > > collisions. > > > > If the machine is connected to a managed switch, look for "runt > > packets", smaller than 54 bytes (56?, whatever the minimum valid size > > is).... > > sorry, did all that before whining. but, as i might not have, > your asking was quite appropriate. > > # netstat -m > 204 mbufs in use > 134/13120 mbuf clusters in use (current/max) > 0/4/3536 sfbufs in use (current/peak/max) > 319 KBytes allocated to network > 0 requests for sfbufs denied > 0 requests for sfbufs delayed > 0 requests for I/O initiated by sendfile > > # netstat -i > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll > fxp0 1500 00:30:48:51:c8:5e 47087068 0 46603594 0 0 > fxp0 1500 RG.NET/24 rip 47394365 - 47237789 - - > fxp0 1500 ssh/32 ssh 5129 - 0 - - > fxp1* 1500 00:30:48:51:c8:5f 0 0 0 0 0 > lo0 16384 857260 0 857260 0 0 > lo0 16384 your-net localhost 223262 - 223262 - - > > it appears to be a plain increase in the reporting of pullup failed. > > randy > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"