From owner-freebsd-stable@FreeBSD.ORG Tue Apr 6 03:51:46 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CEB071065670 for ; Tue, 6 Apr 2010 03:51:46 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [76.96.62.56]) by mx1.freebsd.org (Postfix) with ESMTP id 2BDA38FC19 for ; Tue, 6 Apr 2010 03:51:45 +0000 (UTC) Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44]) by qmta06.westchester.pa.mail.comcast.net with comcast id 1ojL1e0030xGWP8563rmeA; Tue, 06 Apr 2010 03:51:46 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta12.westchester.pa.mail.comcast.net with comcast id 23rl1e0053S48mS3Y3rlll; Tue, 06 Apr 2010 03:51:46 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 13E0E9B419; Mon, 5 Apr 2010 20:51:44 -0700 (PDT) Date: Mon, 5 Apr 2010 20:51:44 -0700 From: Jeremy Chadwick To: "Mikhail T." Message-ID: <20100406035144.GA98354@icarus.home.lan> References: <4BBA8D9F.7000006@aldan.algebra.com> <20100406021414.GA96148@icarus.home.lan> <4BBAA1B9.7060101@aldan.algebra.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4BBAA1B9.7060101@aldan.algebra.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: stable@FreeBSD.org Subject: Re: binding on 127.0.0.1 not working after upgrade to 7.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Apr 2010 03:51:46 -0000 On Mon, Apr 05, 2010 at 10:51:37PM -0400, Mikhail T. wrote: > Jeremy Chadwick написав(ла): > > Check ifconfig -a and make sure lo0 appears / has a correct IP address, > > and the interface is up. > > > You are right, it is not up: > > lo0: flags=8008 metric 0 mtu 16384 > > Manually running `ifconfig lo0 127.0.0.1' fixed the problem for the time > being... > > But why? What changed so significantly in the last few month, that lo0 > broke, of all things? :-) It hasn't broken on any of the systems I maintain, including my own two home servers. If this problem was common/widespread, there'd be a lot more reports of it coming in. There is likely something else going on in your rc.conf or configuration setup (possibly you botched a mergemaster merge?) which is causing the problem. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |