From owner-freebsd-net@FreeBSD.ORG Thu Mar 23 02:43:09 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2375A16A401 for ; Thu, 23 Mar 2006 02:43:09 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from mail.stovebolt.com (mail.stovebolt.com [66.221.101.248]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0FD343D4C for ; Thu, 23 Mar 2006 02:43:08 +0000 (GMT) (envelope-from pauls@utdallas.edu) Received: from [192.168.2.101] (adsl-66-141-178-163.dsl.rcsntx.swbell.net [66.141.178.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTP id 4FA23114307 for ; Wed, 22 Mar 2006 20:40:06 -0600 (CST) Date: Wed, 22 Mar 2006 20:41:59 -0600 From: Paul Schmehl To: freebsd-net@freebsd.org Message-ID: <450528E72F6DEFD144E3DA9D@Paul-Schmehls-Computer.local> In-Reply-To: References: X-Mailer: Mulberry/4.0.0 (Mac OS X) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========884C8AE3C6750BEA20AF==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Loopback problem X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Mar 2006 02:43:09 -0000 --==========884C8AE3C6750BEA20AF========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On March 22, 2006 7:43:31 PM -0600 Paul Schmehl =20 wrote: > I have two machines (that I know of) that have the same problem. The > loopback interface has no ipv4 address, and it doesn't start up on boot. > If I bring the interface up (ifconfig lo0 up),. it has no ipv4 address. > If I bring it up this way - ifconfig lo0 inet 127.0.0.1, then I have an > ipv4 address and everything works fine. > > On box is 5.4 SECURITY. The other is 6.0 SECURITY. Both boxes have > ifconfig=3D"lo0 inet 127.0.0.1" in the /etc/defaults/rc.conf file. Both > boxes boot fine and work fine, except for this one problem, which has > manifested odd symptoms from time to time but never merited investigation > (until now.) > > Since I did the installs on both boxes, I've obviously missed something > during the install (or chosen the wrong option). Does anyone have a clue > what it might be? Or how I might fix this problem so the boxes will > bring up lo0 at boot? > I just figured out the problem with one box. (The other is down right now, = so I can't get to it.) For some reason the following was in /etc/rc.conf=20 (I don't know if that was done by setup or some other program): network_interfaces=3D"l0 xl0 xl1" I changed that to: network_interfaces=3D"lo0 xl0 xl1" and now the box activates lo0 on boot, including the ipv4 address. I'll have to check the other box tomorrow morning. Paul Schmehl (pauls@utdallas.edu) Adjunct Information Security Officer University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu/ --==========884C8AE3C6750BEA20AF==========--