Date: Fri, 27 Jan 2006 06:30:36 -0800 (PST) From: Will Froning <wfroning@angui.sh> To: "Kelly D. Grills" <kdgrills@the-grills.com> Cc: freebsd-stable@freebsd.org Subject: Re: dhclient wedged Message-ID: <20060127062215.R33584@home.angui.sh> In-Reply-To: <20060122155131.GA823@the-grills.com> References: <43D339CC.3020204@forrie.com> <20060122155131.GA823@the-grills.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Kelly, On Sun, 22 Jan 2006, Kelly D. Grills wrote: =>On Sun, Jan 22, 2006 at 02:52:44AM -0500, Forrest Aldrich wrote: =>> =>> I reported this problem a few OS versions back... pre-6. I'm on =>> FreeBSD-6-STABLE, and I've found the dhclient once again "wedged" in a =>> mode that was eating a lot of CPU. =>> =>> The solution is to kill it, and restart. =>> =>> I'm on Comcast's network, so I don't really know if their DHCP server is =>> doing something that FreeBSD's stock dhclient doesn't like; however, I =>> wonder if someone else has noticed this problem, etc. =>> =>Yes, I've also had the same problem (6.0-RELEASE), on Comcast also. =>I installed isc-dhcp3-client-3.0.3_1 from ports and haven't had a =>problem since. (crossing fingers ;=) not sure if it's the same problem for you, but Comcast in my area supplies a bad entry for DNS Suffix/Search order ((hsd1.ca.comcast.net)(hsd2.ca.comcast.net)) And my little netgear router doesn't like that entry and _seems_ to only supply "hsd1.ca.comcast.net))" via dhcp. My Mac and Winbloze boxes do fine, but FBSD rejects the dhoffer unless isc's dhclient is used. I haven't tried plugging directly into the Comcast router, so I don't know if FBSD will accept the original offer with parens... Thanks, Will -- Will Froning Unix Sys. Admin. wfroning@angui.sh
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060127062215.R33584>