[PC-BSD Testing] UP or DHCP for Ethernet devices

Lars Engels lars.engels at 0x20.net
Wed Sep 15 03:32:19 PDT 2010

Quoting Kris Moore <kris at pcbsd.org>:

> 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?
>> Cheers,
>> Dru
>> _______________________________________________
>> Testing mailing list
>> Testing at lists.pcbsd.org
>> http://lists.pcbsd.org/mailman/listinfo/testing
> 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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: PGP Digital Signature
URL: <http://lists.pcbsd.org/pipermail/testing/attachments/20100915/da4db943/attachment.bin>

More information about the Testing mailing list