From owner-freebsd-current@FreeBSD.ORG Tue Dec 23 12:26:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1E9216A4CE for ; Tue, 23 Dec 2003 12:26:32 -0800 (PST) Received: from mta10.adelphia.net (mta10.adelphia.net [68.168.78.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22A3143D48 for ; Tue, 23 Dec 2003 12:26:31 -0800 (PST) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com ([68.68.113.33]) by mta10.adelphia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20031223202630.BGUH14686.mta10.adelphia.net@potentialtech.com>; Tue, 23 Dec 2003 15:26:30 -0500 Message-ID: <3FE8A4F6.1000300@potentialtech.com> Date: Tue, 23 Dec 2003 15:26:30 -0500 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031005 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Leo Bicknell References: <20031223201948.GB33497@ussenterprise.ufp.org> In-Reply-To: <20031223201948.GB33497@ussenterprise.ufp.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: 127.0.0.1 missing from lo0? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Dec 2003 20:26:32 -0000 Leo Bicknell wrote: > I just noticed that my -current machine (early December) doesn't > have 127.0.0.1 configured on lo0. This breaks some things I didn't > even know were broken until today. I just verified my test box, > even when rebooted, comes back without 127.0.0.1 on lo0. Anyone else > seen the problem, or do I need to pull my config apart bit-by-bit to > find the reason? There have been some points along the development path where an improper network_interfaces line in /etc/rc.conf would cause lo0 not to be configured (at least that I noticed). I haven't checked this in a while, so I don't know if current versions of rc.network have the problem or not, but at one time: network_interfaces="lo0 fxp0" worked, while network_interfaces="fxp0" would not configure lo0. Don't know if this is your problem or not, but it's something to look at. -- Bill Moran Potential Technologies http://www.potentialtech.com