From owner-freebsd-security@FreeBSD.ORG Sat Sep 4 19:36:07 2004 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA87216A4CE for ; Sat, 4 Sep 2004 19:36:07 +0000 (GMT) Received: from out014.verizon.net (out014pub.verizon.net [206.46.170.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50D7D43D39 for ; Sat, 4 Sep 2004 19:36:07 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] ([68.160.193.218]) by out014.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040904193606.HPHQ24490.out014.verizon.net@[192.168.1.3]>; Sat, 4 Sep 2004 14:36:06 -0500 Message-ID: <413A1916.8090404@mac.com> Date: Sat, 04 Sep 2004 15:35:50 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Jean M. Vandette" References: <6.1.2.0.2.20040904144122.0de6c0c0@pop.securenet.net> In-Reply-To: <6.1.2.0.2.20040904144122.0de6c0c0@pop.securenet.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out014.verizon.net from [68.160.193.218] at Sat, 4 Sep 2004 14:36:06 -0500 cc: freebsd-security@freebsd.org Subject: Re: IPFW PULLUP Failed X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Sep 2004 19:36:07 -0000 Jean M. Vandette wrote: > Greetings all > > I keep getting the message on the console "IPFW pullup failed" > > I cannot seem to find out what it means or how to correct it any help > would be of great help. I'm running FreeBSD 5.1-RELEASE-p17 This is probably the wrong list for the question, but the message means that IPFW saw a very short/invalid network packet, one so short that there was not enough information to create a more useful log entry. If you're seeing lots of them, it may be a result of failing network hardware or a cabling glitch. -- -Chuck