From owner-freebsd-net@FreeBSD.ORG Wed Nov 7 16:22:53 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D9EC4E1F for ; Wed, 7 Nov 2012 16:22:53 +0000 (UTC) (envelope-from ptyll@nitronet.pl) Received: from mail.nitronet.pl (smtp.nitronet.pl [195.90.106.27]) by mx1.freebsd.org (Postfix) with ESMTP id 892688FC19 for ; Wed, 7 Nov 2012 16:22:53 +0000 (UTC) Received: from mailnull by mail.nitronet.pl with virscan (Exim 4.76 (FreeBSD)) (envelope-from ) id 1TW8Oy-000FP2-P4 for freebsd-net@freebsd.org; Wed, 07 Nov 2012 17:22:52 +0100 Date: Wed, 7 Nov 2012 17:22:28 +0100 From: Pawel Tyll X-Priority: 3 (Normal) Message-ID: <1688071357.20121107172228@nitronet.pl> To: freebsd-net@freebsd.org, freebsd-ipfw@freebsd.org Subject: Re: IPFW pipe list - invalid oid len 0 In-Reply-To: <805416930.20121107162816@nitronet.pl> References: <805416930.20121107162816@nitronet.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: Nitronet.pl X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: ptyll@nitronet.pl X-SA-Exim-Scanned: No (on mail.nitronet.pl); SAEximRunCond expanded to false X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2012 16:22:53 -0000 > I'm running: > /sbin/ipfw pipe list > pipestats-`date "+%Y%m%d-%H%M%S"` > from cron every minute for statistical purposes. > Randomly (more often in loaded hours) it results in: > ipfw: invalid oid len 0 > Is this enough to squash this bug? Just a quick note: It happened since 8.2, and it's still happening on 12-hour old 9-PRERELEASE.