From owner-freebsd-questions@FreeBSD.ORG Fri Jun 13 08:59:53 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 3E27237B401 for ; Fri, 13 Jun 2003 08:59:53 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F44843F75 for ; Fri, 13 Jun 2003 08:59:50 -0700 (PDT) (envelope-from freebsd-questions@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19QqpQ-0008Fh-00 for ; Fri, 13 Jun 2003 17:51:00 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19Qqn3-00083y-00 for ; Fri, 13 Jun 2003 17:48:33 +0200 From: Mark Atkinson Date: Fri, 13 Jun 2003 08:51:11 -0700 Lines: 47 Message-ID: References: <20030613152226.GA91843@ns2.wananchi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@main.gmane.org User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030328 X-Accept-Language: en-us, en In-Reply-To: <20030613152226.GA91843@ns2.wananchi.com> Sender: news Subject: Re: arp messages: Why is this happening? 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: Fri, 13 Jun 2003 15:59:53 -0000 This is probably a DHCP network? This would happen if a client gets a new DHCP assigned IP address, instead of it's old one, and before the freebsd boxes' ARP cache expired for that machine. Usually this only happens with: - broken DHCP clients (not requesting it's old ip back upon reboot). - broken DHCP servers (not maintaining lease state properly to assign clients their old addresses) - tight DHCP address spaces (ie. the DHCP server must reuse previously leased IP addresses to accomodate new DISCOVERS). or a combination of the above. Either that or you have a whole bunch of machines that use gratuitous ARP to advertise the new interfaces in a failover situation. ODHIAMBO Washington wrote: > My log files (and console) fill up with these messages. > > > >>arp: 62.8.64.172 moved from 00:c0:05:11:01:f1 to 00:c0:05:10:01:f1 on bge1 >>arp: 62.8.64.201 moved from 00:c0:05:10:01:f1 to 00:c0:05:11:01:f1 on bge1 >>arp: 62.8.64.201 moved from 00:c0:05:11:01:f1 to 00:c0:05:10:01:f1 on bge1 >>arp: 62.8.64.145 moved from 00:c0:05:11:01:f1 to 00:c0:05:10:01:f1 on bge1 >>arp: 62.8.64.212 moved from 00:c0:05:11:01:f1 to 00:c0:05:10:01:f1 on bge1 >>arp: 62.8.64.188 moved from 00:c0:05:11:01:f1 to 00:c0:05:10:01:f1 on bge1 > > ... > > > Googling doesn't seem to give me a good answer as to why. > This is 4.8-STABLE > > > > > -Wash > --- Mark atkin901 at NOSPAM yahoo dot com (!wired)?(coffee++):(wired);