From owner-freebsd-current Fri Apr 7 23:34:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from blues.jpj.net (blues.jpj.net [204.97.17.146]) by hub.freebsd.org (Postfix) with ESMTP id F329837BD54 for ; Fri, 7 Apr 2000 23:34:46 -0700 (PDT) (envelope-from trevor@jpj.net) Received: from localhost (trevor@localhost) by blues.jpj.net (right/backatcha) with ESMTP id e386YgF00382; Sat, 8 Apr 2000 02:34:42 -0400 (EDT) Date: Sat, 8 Apr 2000 02:34:42 -0400 (EDT) From: Trevor Johnson To: David Holloway Cc: current@FreeBSD.ORG Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c In-Reply-To: <200004071942.MAA01133@papermill.wrs.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 > I say with 99% certainty that assigning 0.0.0.0 to > the interface is a requirement of dhcp. > > You can't stop using it and expect dhcp to work. The Linux folks stopped doing it: 2.0 supported the net interface 0.0.0.0 IP address convention (meaning the kernel should accept all IP packets). 2.[12] don't, hence things like many bootp/dhcp configurations which used this feature break. The proper fix is to modify bootp/dhcp clients to accomplish the same thing using raw sockets instead. I think dhcpcd () already works this way, but bootpc hasn't been updated yet. --message from David Wragg (dpw@doc.ic.ac.uk) at http://www.tux.org/hypermail/linux-kernel/1999week05/0601.html __ Trevor Johnson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message