Date: Sat, 8 Apr 2000 02:34:42 -0400 (EDT) From: Trevor Johnson <trevor@jpj.net> To: David Holloway <davidhol@windriver.com> Cc: current@FreeBSD.ORG Subject: Re: Overwhelming messages from /sys/netinet/if_ether.c Message-ID: <Pine.BSI.4.21.0004080231110.29341-100000@blues.jpj.net> In-Reply-To: <200004071942.MAA01133@papermill.wrs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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 (<URL:http://www.phystech.com/download/dhcpcd.html>) 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.4.21.0004080231110.29341-100000>