From owner-freebsd-current@FreeBSD.ORG Sun May 21 08:40:06 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from localhost.my.domain (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 820F116A420; Sun, 21 May 2006 08:40:05 +0000 (UTC) (envelope-from davidxu@freebsd.org) From: David Xu To: Peter Jeremy Date: Sun, 21 May 2006 16:39:54 +0800 User-Agent: KMail/1.8.2 References: <200605211204.10259.davidxu@freebsd.org> <20060521055332.GE1587@turion.vk2pj.dyndns.org> <200605211400.30163.davidxu@freebsd.org> In-Reply-To: <200605211400.30163.davidxu@freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200605211639.54343.davidxu@freebsd.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: couldn't bind to local address X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 21 May 2006 08:40:06 -0000 On Sunday 21 May 2006 14:00, David Xu wrote: > in fact, finally I found sysinstall only put nve0 in variable > network_interfaces, this causes lo0 does not have an address assigned. > > David Xu Sorry for misleading, I finally found the culprit, it is gnome Networking Setting dialog, if you use it, it will write network_interfaces into /etc/rc.conf, but it ignores lo0, so next time when you reboot your machine, the lo0 adaptive does not have an address, now I can reproduce it on another machine, there is a line in my rc.conf file: network_interfaces=fxp0 but no lo0 David Xu