Date: Wed, 22 Jul 2009 15:06:32 -0500 From: "Paul A. Procacci" <pprocacci@datapipe.net> To: Brooks Davis <brooks@freebsd.org> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: ue0 dhclient FBSD8-BETA2 Message-ID: <4A677148.6070506@datapipe.net> In-Reply-To: <20090722192850.GB94204@lor.one-eyed-alien.net> References: <4A676307.8090503@datapipe.net> <20090722192850.GB94204@lor.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A677148.6070506>