From owner-freebsd-current Sat Apr 8 4:21:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (Postfix) with ESMTP id ADFD137B63A; Sat, 8 Apr 2000 04:21:50 -0700 (PDT) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.8) with ESMTP id MAA29490; Sat, 8 Apr 2000 12:22:03 +0100 (BST) (envelope-from arg@arg1.demon.co.uk) Date: Sat, 8 Apr 2000 12:22:03 +0100 (BST) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Mike Smith Cc: David Holloway , "Rodney W. Grimes" , current@freebsd.org Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c In-Reply-To: <200004080032.RAA03588@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 7 Apr 2000, Mike Smith wrote: > > > > However, this isn't really an excuse for issuing ARP with a source address > > of zero: the initial DHCP exchange is done with broadcasts (so doesn't > > need ARP), and after that the address is known. The problem presumably > > arises due to other traffic trying to go out while DHCP is still > > configuring the interface. > > If you look at the original error message, you'll note that it's actually > due to seeing another packet which claims the same Ip address. Yes, but what caused that packet to be sent? Plainly, with only a single machine (and all others correctly configured) you'll never see the error. If you've got one machine configured to do DHCP, you've probably got several - and so if two boot at the same time you have the conditions to generate the error. On the other hand, this isn't really a plausible explanation for "overwhelming" numbers of errors - unless perhaps the DHCP server is dead. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message