From owner-freebsd-current@FreeBSD.ORG Mon Feb 2 15:59:12 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 0F81916A4CE for ; Mon, 2 Feb 2004 15:59:12 -0800 (PST) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B07243D45 for ; Mon, 2 Feb 2004 15:59:09 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from midget.dons.net.au (ppp33-156.lns1.adl1.internode.on.net [150.101.33.156])i12Nx6xC095081; Tue, 3 Feb 2004 10:29:07 +1030 (CST) Received: from chowder.gsoft.com.au (root@localhost.dons.net.au [127.0.0.1]) by midget.dons.net.au (8.12.9/8.12.9) with ESMTP id i12Nx25n018135; Tue, 3 Feb 2004 10:29:04 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "David W. Hankins" , freebsd-current@freebsd.org Date: Tue, 3 Feb 2004 10:29:01 +1030 User-Agent: KMail/1.5.4 References: <200402021100.12106.doconnor@gsoft.com.au> <20040202173352.GA9816@isc.org> In-Reply-To: <20040202173352.GA9816@isc.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402031029.01379.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.26 (www . roaringpenguin . com / mimedefang) 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 23:59:12 -0000 On Tuesday 03 February 2004 04:03, David W. Hankins wrote: > 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. Hmm, that sounds plausible :) > > 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. It is marked authoritative.. > 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. Ahh OK. > 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. I haven't set a longer timeout, and I did wait longer than 10 seconds, but less than a minute or so.. Guess I probably should have just left it. Thanks for the information. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5