From owner-freebsd-stable@FreeBSD.ORG Wed Jul 22 20:06:31 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6CCC106564A for ; Wed, 22 Jul 2009 20:06:31 +0000 (UTC) (envelope-from pprocacci@datapipe.net) Received: from mta31.charter.net (mta31.charter.net [216.33.127.82]) by mx1.freebsd.org (Postfix) with ESMTP id 382268FC13 for ; Wed, 22 Jul 2009 20:06:30 +0000 (UTC) (envelope-from pprocacci@datapipe.net) Received: from imp11 ([10.20.200.11]) by mta31.charter.net (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090722200614.WXHF2647.mta31.charter.net@imp11>; Wed, 22 Jul 2009 16:06:14 -0400 Received: from beast.myhome ([75.138.226.179]) by imp11 with smtp.charter.net id K86D1c00S3ss4W30586DQr; Wed, 22 Jul 2009 16:06:14 -0400 Message-ID: <4A677148.6070506@datapipe.net> Date: Wed, 22 Jul 2009 15:06:32 -0500 From: "Paul A. Procacci" User-Agent: Thunderbird 2.0.0.22 (X11/20090722) MIME-Version: 1.0 To: Brooks Davis References: <4A676307.8090503@datapipe.net> <20090722192850.GB94204@lor.one-eyed-alien.net> In-Reply-To: <20090722192850.GB94204@lor.one-eyed-alien.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-stable@freebsd.org" Subject: Re: ue0 dhclient FBSD8-BETA2 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: Wed, 22 Jul 2009 20:06:31 -0000 Brooks, I appreciate the quick follow up. You were right, and this now work perfectly. Thank you for taking the time to respond to my question. Thanks, Paul Brooks Davis wrote: > On Wed, Jul 22, 2009 at 02:05:43PM -0500, Paul A. Procacci wrote: > >> Gents, >> >> Since the name changed for my cdce device, booting up the OS fails to >> obtain an address via dhcp on this interface. dhclient works normally >> after the machine is booted and I provide the command on the command line. >> >> I've got the following in my rc.conf which I would have thought to be >> enough, but it doesn't matter as dhclient never gets run, >> >> ifconfig_ue0="DHCP" >> >> This isn't a deal breaker by any means, but would like to inquire about >> about the proper steps for getting dhclient to physically work on the ue0 >> interface. Docs on this subject (usb ethernet changes) at this point are >> scarce and I'm not sure what specifically needs to be done. >> > > This generally means that ue0 never reports a link up event which means > dhclient never gets run. If so, the driver is broken, but you may be > able to work around it by changing DHCP to SYNCDHCP. In that case > it may work if the cable is plugged in when the device it attached. > > -- Brooks >