From owner-freebsd-current Fri Nov 19 13:56:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id EC65014DE9 for ; Fri, 19 Nov 1999 13:56:29 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id QAA02988; Fri, 19 Nov 1999 16:56:26 -0500 (EST) (envelope-from luoqi) Date: Fri, 19 Nov 1999 16:56:26 -0500 (EST) From: Luoqi Chen Message-Id: <199911192156.QAA02988@lor.watermarkgroup.com> To: ak03@gte.com Subject: RE: arplookup 127.0.0.1 failed: could not allocate llinfo Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There is no need to fix kernel if the same result could be achieved by simple > rc.network file modification. Yes, solution proposed in conf/14913 is > not complete and only works in network_interfaces="auto" case, but the > modification to make it work in 100% cases is pretty trivial. > I finally found the problem, it was not a kernel bug, it was dhcp client. In /sbin/dhclient-script, it tried to install a route from localhost to the ether interface, which was bogus if the loop-back interface was not configured. Under BSD4.4, there's no need to add such a route, it will be automatically generated by the kernel. So the simplest solution to this problem is to delete all `route add xxx 127.0.0.1' statements from the script. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message