From owner-freebsd-current@FreeBSD.ORG Mon Feb 2 09:33:53 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 57B1816A4CE for ; Mon, 2 Feb 2004 09:33:53 -0800 (PST) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57FCC43D1D for ; Mon, 2 Feb 2004 09:33:52 -0800 (PST) (envelope-from David_Hankins@isc.org) Received: by farside.isc.org (Postfix, from userid 10200) id 4059BA84A; Mon, 2 Feb 2004 17:33:52 +0000 (UTC) Date: Mon, 2 Feb 2004 17:33:52 +0000 From: "David W. Hankins" To: freebsd-current@freebsd.org Message-ID: <20040202173352.GA9816@isc.org> References: <200402021100.12106.doconnor@gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200402021100.12106.doconnor@gsoft.com.au> User-Agent: Mutt/1.4i Subject: Re: dhclient can't get a DHCP lease.. 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: Mon, 02 Feb 2004 17:33:53 -0000 On Mon, Feb 02, 2004 at 11:00:12AM +1030, Daniel O'Connor wrote: > Feb 2 10:22:40 metatron dhcpd: DHCPREQUEST for 0.0.0.0 from 00:20:e0:65:13:1d > via dc0: unknown lease 0.0.0.0. > Feb 2 10:22:53 metatron dhcpd: DHCPREQUEST for 0.0.0.0 from 00:20:e0:65:13:1d > via dc0: unknown lease 0.0.0.0. it would have been nice to have gotten a before-n-after on /var/db/dhclient.leases. my only guess would be that yours was somehow corrupted. > DHCP server is FreeBSD with isc-dhcp3-3.0.1.r9 which hasn't changed for a > while. just a side-note...if you had 'authoritative;' configured, it would send a NAK upon the first REQ for an unknown address. this would send clients back to init state much more rapidly than your experience. sadly, so rapidly you probably never would have noticed a problem. > Gah.. > I just went to do some more tracing and it worked fine after not working > all morning.. The working one did a DHCPDISCOVER first, though I don't know > why :( my guess would be that after reaching the request timeout, dhclient entered the address-selection loop (in dhclient's case, it picks the first one that got ACK'd on the list and throws out all else), and since that NULL address was the only lease and wasn't ACK'd, it exited the loop without picking a lease. when that happens, dhclient goes back to init state to get new leases. if 'all morning' was an extended period, then i presume you were interrupting dhclient when you realized it was not working right, or have configured a large reboot timeout in etc/dhclient.conf. the default reboot timeout is 10 seconds. -- David W. Hankins "If you don't do it right the first time, Operations Engineer you'll just have to do it again." Internet Systems Consortium, Inc. -- Jack T. Hankins