From owner-freebsd-stable@FreeBSD.ORG Fri Jan 27 14:33:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8D6E16A420 for ; Fri, 27 Jan 2006 14:33:15 +0000 (GMT) (envelope-from wfroning@home.angui.sh) Received: from angui.sh (dsl081-242-113.sfo1.dsl.speakeasy.net [64.81.242.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EF1944112 for ; Fri, 27 Jan 2006 14:33:05 +0000 (GMT) (envelope-from wfroning@home.angui.sh) Received: from home.angui.sh (localhost.angui.sh [127.0.0.1]) by angui.sh (8.13.4/8.13.3) with ESMTP id k0REUavs033950 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Jan 2006 06:30:36 -0800 (PST) (envelope-from wfroning@home.angui.sh) Received: from localhost (wfroning@localhost) by home.angui.sh (8.13.4/8.13.3/Submit) with ESMTP id k0REUakl033947; Fri, 27 Jan 2006 06:30:36 -0800 (PST) (envelope-from wfroning@home.angui.sh) Date: Fri, 27 Jan 2006 06:30:36 -0800 (PST) From: Will Froning To: "Kelly D. Grills" In-Reply-To: <20060122155131.GA823@the-grills.com> Message-ID: <20060127062215.R33584@home.angui.sh> References: <43D339CC.3020204@forrie.com> <20060122155131.GA823@the-grills.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: -2.82 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.51 on 64.81.57.93 Cc: freebsd-stable@freebsd.org Subject: Re: dhclient wedged X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jan 2006 14:33:16 -0000 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