From owner-freebsd-questions@FreeBSD.ORG Sat Jun 28 11:36:30 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 3A4A237B401 for ; Sat, 28 Jun 2003 11:36:30 -0700 (PDT) Received: from mta1.adelphia.net (mta1.adelphia.net [64.8.50.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8352C43FD7 for ; Sat, 28 Jun 2003 11:36:29 -0700 (PDT) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com ([24.53.179.151]) by mta1.adelphia.net (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with ESMTP id <20030628184005.UTGQ25556.mta1.adelphia.net@potentialtech.com>; Sat, 28 Jun 2003 14:40:05 -0400 Message-ID: <3EFDE02C.5010003@potentialtech.com> Date: Sat, 28 Jun 2003 14:36:28 -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: budsz References: <20030628175128.GA4404@kumprang.or.id> In-Reply-To: <20030628175128.GA4404@kumprang.or.id> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD-Questions Subject: Re: What's this mean? 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: Sat, 28 Jun 2003 18:36:30 -0000 budsz wrote: > Hi dude, > > I get message in /var/log/message: > > /kernel: in_cksum: out of data by 3 > > Would you explain this message? in_chksum is a routine that validates the checksum of recieved network data. As far as I can tell from the code, that error means that the packet of data was three bytes shorter than it should have been. One way or the other it's a network problem. Could be crappy NIC or other hardware. Could be some sort of attack using invalid packets. I'm not familiar enough with that corner of the code to say for sure. Is this happening frequently? If you only saw the message once, you can probably ignore it as a network glitch, but if it's showing up often, you'd do well to track down the source and fix it. -- Bill Moran Potential Technologies http://www.potentialtech.com