From owner-freebsd-current@FreeBSD.ORG Thu Jan 8 13:54:10 2004 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 E6BC116A4CE for ; Thu, 8 Jan 2004 13:54:10 -0800 (PST) Received: from mail.lambertfam.org (www.lambertfam.org [216.223.208.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id C547843D5D for ; Thu, 8 Jan 2004 13:54:09 -0800 (PST) (envelope-from lambert@lambertfam.org) Received: by mail.lambertfam.org (Postfix, from userid 999) id 4DD1934D50; Thu, 8 Jan 2004 16:54:09 -0500 (EST) Date: Thu, 8 Jan 2004 16:54:09 -0500 From: Scott Lambert To: freebsd-current@FreeBSD.org Message-ID: <20040108215409.GB902@www.lambertfam.org> Mail-Followup-To: freebsd-current@FreeBSD.org References: <20040108204617.GA902@www.lambertfam.org> <20040108214238.489255D04@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040108214238.489255D04@ptavv.es.net> User-Agent: Mutt/1.5.5.1i Subject: Re: 5.2 RC2 DHCP/resolv.conf install problem 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: Thu, 08 Jan 2004 21:54:11 -0000 On Thu, Jan 08, 2004 at 01:42:38PM -0800, Kevin Oberman wrote: > > Date: Thu, 8 Jan 2004 15:46:17 -0500 > > From: Scott Lambert > > Sender: owner-freebsd-current@freebsd.org > > > > I've had this happen a couple of times over the past mumble months. But > > I don't install 5.x often enough and thought I was just seeing a fluke > > in the way my system installed. Seeing it for third time is just too > > many flukes. > > > > Last night I installed 5.2 RC2 on my shiny new Compaq Presario 2195US. > > When it rebooted the first time, DHCP gave me my IP address and default > > route but resolv.conf did not exist. To fix, I touched /etc/resolv.conf > > and restarted dhclient. > > > > My DHCP server is a Linksys WAP/Router/4-port switch, but I don't think > > the DHCP server is material to the issue. > > I was seeing the same thing last November when I was traveling. It only > happened in my hotel room on the broadband connection. > > My suspicion is that the DHCP server is not providing a DNS server and > that it is simply deleting the resolv.conf instead of leaving the > existing one. > > You might want to try doing a capture of traffic to the bootps port on > your system and see if that is what is happening. I've only had this happen on the first boot; but I suppose I have a populated resolv.conf after that, don't I? I'll have to dig some more. Hmm, was one of these instances at work? I'll have to check both places. Thanks. -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org