From owner-freebsd-questions@FreeBSD.ORG Sun Jan 23 20:26:36 2005 Return-Path: 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 B6FCD16A4CE for ; Sun, 23 Jan 2005 20:26:36 +0000 (GMT) Received: from out007.verizon.net (out007pub.verizon.net [206.46.170.107]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2668543D2D for ; Sun, 23 Jan 2005 20:26:36 +0000 (GMT) (envelope-from reso3w83@verizon.net) Received: from ringworm.mechee.com ([4.26.84.7]) by out007.verizon.net ESMTP <20050123202635.WCGD21228.out007.verizon.net@ringworm.mechee.com>; Sun, 23 Jan 2005 14:26:35 -0600 Received: by ringworm.mechee.com (Postfix, from userid 1001) id CDBD12CE745; Sun, 23 Jan 2005 12:22:56 -0800 (PST) From: "Michael C. Shultz" To: freebsd-questions@freebsd.org Date: Sun, 23 Jan 2005 12:22:52 -0800 User-Agent: KMail/1.7.2 References: <20050123183343.GD21544@thingy.apana.org.au> <11418268078.20050123210226@hexren.net> <20050123200900.GE21544@thingy.apana.org.au> In-Reply-To: <20050123200900.GE21544@thingy.apana.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501231222.54339.reso3w83@verizon.net> X-Authentication-Info: Submitted using SMTP AUTH at out007.verizon.net from [4.26.84.7] at Sun, 23 Jan 2005 14:26:35 -0600 Subject: Re: dhclient problems in 5.3-RELEASE X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 20:26:36 -0000 On Sunday 23 January 2005 12:09 pm, David Gerard wrote: > Hexren (me@hexren.net) [050124 07:02]: > > DG> On reboot, I ran dhclient and it completely failed to get an IP > > address. DG> But I know the cable is good and the DHCP server is > > working, because I DG> booted the box in question into Windows and > > it grabbed an IP just fine. So DG> where do I start on diagnosing > > what's up with this installation? > > > > Start by sniffing the network traffic on the DHCP Server machine > > while you request an address. See where it differs from the usual. > > Maybe the problem becomes obvious then. :) > > As I noted, it served fine to the Windows installation on the same > box on the same wire from the same server. Also, just before > installing 5.3, it was serving just fine to FreeBSD 4.10 on the same > box on the same wire from the same server. The only factor that's > different is the software and OS running. I'm wondering what if > anything's changed in dhclient between 4.10 and 5.3 ... is there some > daft but obvious gotcha I've missed? Or are you saying the 5.3 > dhclient is much, much fussier in some way? > > > - d. A while back I had exactly the same problem as you, what I did to prove there was a problem with dhclient in 5.3 was I copied the dir /usr/src/sbin/dhclient from a 4.10 machine to my 5.3 machine, then "make install"'ed it and it worked. I did my best to explain the problem in the lists to no avail so now the machine that runs the dsl modem is running FreeBSD 4.11 and I just don't worry about it anymore. -Mke