From owner-freebsd-current Mon Apr 17 21:41: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from dustdevil.waterspout.com (dustdevil.waterspout.com [208.13.60.151]) by hub.freebsd.org (Postfix) with ESMTP id A898D37BC86 for ; Mon, 17 Apr 2000 21:40:54 -0700 (PDT) (envelope-from csg@dustdevil.waterspout.com) Received: (from csg@localhost) by dustdevil.waterspout.com (8.9.3/8.9.3) id XAA01048; Mon, 17 Apr 2000 23:48:02 -0500 (EST) (envelope-from csg) Date: Mon, 17 Apr 2000 23:48:01 -0500 From: "C. Stephen Gunn" To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c Message-ID: <20000417234801.A979@waterspout.com> References: <38EE011D.B81BA63C@cvzoom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38EE011D.B81BA63C@cvzoom.net>; from dmmiller@cvzoom.net on Fri, Apr 07, 2000 at 11:39:09AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 07, 2000 at 11:39:09AM -0400, Donn Miller wrote: > /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0! I was discussing this issue with Robert Watson the other day on IRC. The issue is more complicated than just removing the notification in sys/netinet/if_ether.c. It's a fundamental problem with the way in_arpinput() seems to process packets, and checking the receive interface versus several interefaces that may or may-not have IPV4 addresses. If I remember Robert's remark in particular, it was related to ARP processing on IPV6 only interfaces that might be plugged into the same wire as IPV4 interfaces on the same machine. This physical configuration yields "host is on but received arp on " errors to be logged as well. Robert's suggestion, that I started researching, was to not perform ARP processing on interfaces that don't have IPV4 addresses assigned. This soultion should also address the problems for logging 0.0.0.0 addresses. If anybody is seriously interested, I'll bump the priority on generating a diff, and posting it here. - Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message