Date: Wed, 22 Jul 2009 14:28:50 -0500 From: Brooks Davis <brooks@freebsd.org> To: "Paul A. Procacci" <pprocacci@datapipe.net> Cc: freebsd-stable@freebsd.org Subject: Re: ue0 dhclient FBSD8-BETA2 Message-ID: <20090722192850.GB94204@lor.one-eyed-alien.net> In-Reply-To: <4A676307.8090503@datapipe.net> References: <4A676307.8090503@datapipe.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--mojUlQ0s9EVzWg2t Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 22, 2009 at 02:05:43PM -0500, Paul A. Procacci wrote: > Gents, >=20 > Since the name changed for my cdce device, booting up the OS fails to=20 > obtain an address via dhcp on this interface. dhclient works normally=20 > after the machine is booted and I provide the command on the command line. >=20 > I've got the following in my rc.conf which I would have thought to be=20 > enough, but it doesn't matter as dhclient never gets run, >=20 > ifconfig_ue0=3D"DHCP" >=20 > This isn't a deal breaker by any means, but would like to inquire about= =20 > about the proper steps for getting dhclient to physically work on the ue0= =20 > interface. Docs on this subject (usb ethernet changes) at this point are= =20 > 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 --mojUlQ0s9EVzWg2t Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iD8DBQFKZ2hyXY6L6fI4GtQRAkASAJ4odFjzq7gC4GLK32QpkDzaCD8b+ACgllXl uo3oAdYLwofFfq9DfF5Hmz0= =tNgX -----END PGP SIGNATURE----- --mojUlQ0s9EVzWg2t--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090722192850.GB94204>