[PC-BSD Testing] UP or DHCP for Ethernet devices
kris at pcbsd.org
Wed Sep 15 06:18:47 PDT 2010
-----BEGIN PGP SIGNED MESSAGE-----
On 09/15/2010 06:32, Lars Engels wrote:
> Quoting Kris Moore <kris at pcbsd.org>:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> On 09/14/2010 11:14, Dru Lavigne wrote:
>>> I had a head scratcher installing 8.1 on a 32 bit testing system.
>>> Instead of Ethernet automatically working (as it always has in the
>>> past), it gave a device busy error during startup. Manually running
>>> dhclient on the device (em0) would not connect to the DHCP server
>>> and instead gave a "send_packet: Device busy" error.
>>> The fix was to change the rc.conf flag on the device from UP to
>>> DHCP. Kris, do you know what UP was supposed to do?
>>> Testing mailing list
>>> Testing at lists.pcbsd.org
>> The dhcp stuff is usually done via the lagg0 interface, so we mark the
>> network device as "up" to ensure its available when lagg0 starts its
>> dhcp requests. I'll have to experiment with that, maybe using "up" isn't
>> needed anymore if lagg is taking care of it already.
> may I propose that the lagg device is created optionally? Would it be
> possible to ask the user if he likes to use the failover mode when a
> wireless and wired interface is available?
> I like the feature but I think it should not be enabled without the
> explicit permission of the user.
I've now set up the GUI to not mark any wired devices as "up". Also I've
added it to the 9.0 TODO to create a way to disable lagg via the GUI,
since that seems like a reasonable request :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the Testing