Date: Sun, 23 Jan 2005 21:45:43 +0100 From: Hexren <me@hexren.net> To: David Gerard <fun@thingy.apana.org.au> Cc: freebsd-questions@freebsd.org Subject: Re[2]: dhclient problems in 5.3-RELEASE Message-ID: <1220865763.20050123214543@hexren.net> In-Reply-To: <20050123200900.GE21544@thingy.apana.org.au> References: <20050123183343.GD21544@thingy.apana.org.au> <11418268078.20050123210226@hexren.net> <20050123200900.GE21544@thingy.apana.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
DG> 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. :) DG> As I noted, it served fine to the Windows installation on the same box on DG> the same wire from the same server. Also, just before installing 5.3, it DG> was serving just fine to FreeBSD 4.10 on the same box on the same wire from DG> the same server. The only factor that's different is the software and OS DG> running. I'm wondering what if anything's changed in dhclient between DG> 4.10 and 5.3 ... is there some daft but obvious gotcha I've missed? Or are DG> you saying the 5.3 dhclient is much, much fussier in some way? DG> - d. --------------------------------------------- I do not know, as I myself only looked once at the code and that was only very briefly. But I have seen myown set of fuzzy DHCP behavior involving different OSes and various network equipment. That is why I suggested to you that you should sniff the traffic to get an idea of where things go astray. At that point you should be able to decide which side stops talking to the other. Armed with that knowledge you should be able to a) look for the error yourself b) pinpoint its general direction more accurate and thus maybe try and find a workaround. For example another DHCP server, c) see who supports the software and send him a bug report or d) provide this list with more information :) Hexren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1220865763.20050123214543>