From owner-freebsd-current Fri Dec 14 6:32:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from savvyworld.net (adsl-64-173-182-158.dsl.mtry01.pacbell.net [64.173.182.158]) by hub.freebsd.org (Postfix) with ESMTP id BD94D37B416; Fri, 14 Dec 2001 06:32:35 -0800 (PST) Received: (from root@localhost) by savvyworld.net (8.11.6/8.11.4) id fBEEWYm07729; Fri, 14 Dec 2001 06:32:34 -0800 (PST) (envelope-from eculp@EnContacto.Net) Received: from 64.173.182.155 ( [64.173.182.155]) as user eculp@EnContacto.Net by Mail.SavvyWorld.Net with HTTP; Fri, 14 Dec 2001 06:32:34 -0800 Message-ID: <1008340354.3c1a0d828bd01@Mail.SavvyWorld.Net> Date: Fri, 14 Dec 2001 06:32:34 -0800 From: Edwin Culp To: Robert Watson Cc: current@FreeBSD.Org Subject: Re: dhclient References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Originating-IP: 64.173.182.155 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Robert, I got it working by adding a dhclient configuration file rather than using the empty file that I have always used. I'm not sure why but it works:-) I'll break out ethereal a little later and see if I can figure it out. Thanks, ed Quoting Robert Watson : > > On Thu, 13 Dec 2001, Edwin Culp wrote: > > > Is anyone using dhclient successfully with Current of the last week or > > so? I don't use it all the time but I have been trying for the last > > couple of days without success. > > > > It accesses the server and changes the interface ip to 0.0.0.0 netmask > > 255.255.255.255. > > My -CURRENT dhclient is working just fine on several boxes from Dec 11, > 12, and 13. And I guess also 14, given the time :-). As pointed out, > 0.0.0.0 is what dhclient will set the interface IP address to when it > doesn't have a valid lease currently, and needs to look for one. If it > fails to quickly find a lease, it keeps trying, but you actually get a > window to see this address on your interface, whereas if it runs quickly, > you often won't. > > Using a packet sniffer can be invaluable in debugging DHCP problems: > tcpdump udp port dhcpc or udp port dhcps is useful, but even better is > ethereal's ability to decode the DHCP packet in detail, display options > cleanly, etc. You might want to try looking to make sure that you're > getting a response, and if you are, whether it looks adequate :-). > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > robert@fledge.watson.org NAI Labs, Safeport Network Services > > > > --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message