From owner-freebsd-questions@FreeBSD.ORG Sat Sep 30 15:24:53 2006 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C55716A403 for ; Sat, 30 Sep 2006 15:24:53 +0000 (UTC) (envelope-from lauasanf@wilderness.homeip.net) Received: from mxsf28.cluster1.charter.net (mxsf28.cluster1.charter.net [209.225.28.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C75143D46 for ; Sat, 30 Sep 2006 15:24:52 +0000 (GMT) (envelope-from lauasanf@wilderness.homeip.net) Received: from mxip32a.cluster1.charter.net (mxip32a.cluster1.charter.net [209.225.28.247]) by mxsf28.cluster1.charter.net (8.12.11.20060308/8.12.11) with ESMTP id k8UFOoAX022447 for ; Sat, 30 Sep 2006 11:24:51 -0400 Received: from 24-159-55-136.dhcp.jcsn.tn.charter.com (HELO [192.168.1.6]) ([24.159.55.136]) by mxip32a.cluster1.charter.net with ESMTP; 30 Sep 2006 11:24:50 -0400 Message-ID: <451E8C49.1080805@wilderness.homeip.net> Date: Sat, 30 Sep 2006 10:24:57 -0500 From: Laurence Sanford User-Agent: Thunderbird 1.5.0.7 (X11/20060926) MIME-Version: 1.0 To: Chuck Swiger References: <451DCFD4.3070408@wilderness.homeip.net> <451E74C8.6070702@mac.com> In-Reply-To: <451E74C8.6070702@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: questions@freebsd.org Subject: Re: Can't ping localhost? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Sep 2006 15:24:53 -0000 Chuck Swiger wrote: > Laurence Sanford wrote: >> Anyone got any ideas on this? >> >> lauasanf@colossus(~)$ ping 127.0.0.1 >> PING 127.0.0.1 (127.0.0.1): 56 data bytes >> ping: sendto: Can't assign requested address >> ping: sendto: Can't assign requested address >> ping: sendto: Can't assign requested address >> ping: sendto: Can't assign requested address >> ping: sendto: Can't assign requested address >> ping: sendto: Can't assign requested address >> ^C >> --- 127.0.0.1 ping statistics --- >> 6 packets transmitted, 0 packets received, 100% packet loss >> >> >> lauasanf@colossus(~)$ ifconfig lo0 >> lo0: flags=8008 mtu 16384 > > If there isn't an "inet 127.0.0.1" entry following, the loopback isn't > properly configured. Perhaps you have a "network_interfaces" entry > listed in /etc/rc.conf which does not mention "lo0"...? > Thanks for even bothering to reply Chuck. Honestly, at my age, I should know better than to post to mailing lists while too tired to be coherent. The actual point of my question was, how exactly does a system come to boot up without having lo0 configured as 127.0.0.1? I do have a network interfaces line in rc.conf that specifies nve0, but that's the way it's always been on this box, and this is only a recent development that it's not been assigned correctly at boot time. I was looking into several other issues I've been seeing (not getting emails from this box for periodic tasks, etc) and finally ran it down to this. Did something change recently? My last update was sept 2nd, and this stopped working for me only about a week ago, maybe two, so it didn't coincide with that update. Now that I've got a little more mental capacity to work with, anyone got something to point me in the right direction? Is it a good idea to configure lo0 in rc.conf even though it should happen automatically? Thanks again.