From owner-freebsd-stable  Mon Apr  9 16:17:50 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from radix.cryptio.net (radix.cryptio.net [199.181.107.213])
	by hub.freebsd.org (Postfix) with ESMTP id 19B6137B422
	for <stable@freebsd.org>; Mon,  9 Apr 2001 16:17:48 -0700 (PDT)
	(envelope-from emechler@radix.cryptio.net)
Received: (from emechler@localhost)
	by radix.cryptio.net (8.11.3/8.11.3) id f39NHlq33475
	for stable@freebsd.org; Mon, 9 Apr 2001 16:17:47 -0700 (PDT)
	(envelope-from emechler)
Date: Mon, 9 Apr 2001 16:17:46 -0700
From: Erick Mechler <emechler@techometer.net>
To: stable@freebsd.org
Subject: Runt packets
Message-ID: <20010409161746.B33217@techometer.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I have a dual-homed machine doing routing and firewalling on which hundreds
of the following messages appear in my logs every 10 minutes or so:

  /kernel: icmp-response bandwidth limit 44069/200 pps
  /kernel: arp: runt packet
  last message repeated 14691 times

At the same time these messages are occurring, I find the following while
doing a tcpdump on the internal interface (it doesn't happen on the
external interface at all):

  19:05:34.247543 arp-#12469 for proto #208 (166) hardware #1 (183)
  19:05:34.247588 arp-#12469 for proto #208 (166) hardware #1 (183)
  19:05:34.247630 arp-#12469 for proto #208 (166) hardware #1 (183)
  19:05:34.247674 arp-#12469 for proto #208 (166) hardware #1 (183)
  19:05:34.247718 arp-#12469 for proto #208 (166) hardware #1 (183)
  19:05:34.247762 arp-#12469 for proto #208 (166) hardware #1 (183)
  19:05:34.247805 arp-#12469 for proto #208 (166) hardware #1 (183)

...except there are thousands of these.  Has anybody seen this before?  
I'm running a slightly old version of 4.2 (Thu Dec 14 15:28:03 EST 2000),
but I didn't see any relevant diffs to sys/netinet/if_ether.c which is
where the "runt packet" errors are sent to syslog.  Could this be a problem
of bad hardware on the part of one of the internal hosts?

Any and all help is much appreciated.

Thanks!
Erick

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message