From owner-freebsd-ipfw@FreeBSD.ORG  Wed Nov  7 16:09:36 2012
Return-Path: <owner-freebsd-ipfw@FreeBSD.ORG>
Delivered-To: freebsd-ipfw@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id 4BFE376F
 for <freebsd-ipfw@freebsd.org>; Wed,  7 Nov 2012 16:09:36 +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 00A6D8FC0A
 for <freebsd-ipfw@freebsd.org>; Wed,  7 Nov 2012 16:09:35 +0000 (UTC)
Received: from mailnull by mail.nitronet.pl with virscan (Exim 4.76 (FreeBSD))
 (envelope-from <ptyll@nitronet.pl>) id 1TW7Yc-000Dw4-Km
 for freebsd-ipfw@freebsd.org; Wed, 07 Nov 2012 16:28:46 +0100
Date: Wed, 7 Nov 2012 16:28:16 +0100
From: Pawel Tyll <ptyll@nitronet.pl>
X-Priority: 3 (Normal)
Message-ID: <805416930.20121107162816@nitronet.pl>
To: freebsd-net@freebsd.org, freebsd-ipfw@freebsd.org
Subject: IPFW pipe list - invalid oid len 0
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: <locally generated>
X-SA-Exim-Mail-From: ptyll@nitronet.pl
X-SA-Exim-Scanned: No (on mail.nitronet.pl); SAEximRunCond expanded to false
X-BeenThere: freebsd-ipfw@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IPFW Technical Discussions <freebsd-ipfw.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ipfw>,
 <mailto:freebsd-ipfw-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ipfw>
List-Post: <mailto:freebsd-ipfw@freebsd.org>
List-Help: <mailto:freebsd-ipfw-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw>,
 <mailto:freebsd-ipfw-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 16:09:36 -0000

Hi lists,

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?