From owner-freebsd-questions@FreeBSD.ORG Sat Jun 14 02:49:58 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 3349A37B401 for ; Sat, 14 Jun 2003 02:49:58 -0700 (PDT) Received: from ns2.wananchi.com (ns2.wananchi.com [62.8.64.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3400443F85 for ; Sat, 14 Jun 2003 02:48:43 -0700 (PDT) (envelope-from wash@wananchi.com) Received: from wash by ns2.wananchi.com with local (Exim 4.20 #5 (FreeBSD)) id 19R7dz-000NPv-JO; Sat, 14 Jun 2003 12:48:19 +0300 Date: Sat, 14 Jun 2003 12:48:19 +0300 From: ODHIAMBO Washington To: Mark Atkinson Message-ID: <20030614094819.GB87960@ns2.wananchi.com> Mail-Followup-To: ODHIAMBO Washington , Mark Atkinson , freebsd-questions@freebsd.org References: <20030613152226.GA91843@ns2.wananchi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Disclaimer: Any views expressed in this message,where not explicitly attributed otherwise, are mine alone!. X-Fortune: Positive, adj.: Mistaken at the top of one's voice. -- Ambrose Bierce, "The Devil's Dictionary" X-Operating-System: FreeBSD 4.8-STABLE i386 X-Best-Window-Manager: Blackbox X-Mailer: Mutt 1.5.3i (2002-12-17) X-Designation: Systems Administrator, Wananchi Online Ltd. X-Location: Nairobi, KE, East Africa. X-Uptime: 12:44PM up 7 days, 2:11, 2 users, load averages: 1.78, 1.67, 1.16 User-Agent: Mutt/1.5.3i cc: freebsd-questions@freebsd.org 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: Sat, 14 Jun 2003 09:49:58 -0000 * Mark Atkinson [20030613 19:00]: wrote: > 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: Not a DHCP network per se, but an ISP environment where clients get assigned dynamic IPs on dialup. However, this problem was never so pronounced when I was running 4.7-STABLE, only after 4.8-STABLE. > - 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. No idea if that applies to me, but we do not run a DHCP server. > Either that or you have a whole bunch of machines that use gratuitous > ARP to advertise the new interfaces in a failover situation. Yikes! I need to be a network specialist, sort of.. but no. -Wash -- Odhiambo Washington "The box said 'Requires Wananchi Online Ltd. www.wananchi.com Windows 95, NT, or better,' Tel: +254 2 313985-9 +254 2 313922 so I installed FreeBSD." GSM: +254 72 743223 +254 733 744121 This sig is McQ! :-) "For three days after death hair and fingernails continue to grow but phone calls taper off." -- Johnny Carson