[PC-BSD Testing] UP or DHCP for Ethernet devices
josh at tcbug.org
Tue Sep 14 09:30:22 PDT 2010
On Tuesday 14 September 2010 11:04:41 Kris Moore wrote:
> 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.
It is busy because it's a member of lagg0, which should handle the DHCP
request just fine. The UP on a wired lagg member is extranious. You do need
it for wireless so the wireless interface can associate before the it's added
to the lagg device.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 488 bytes
Desc: This is a digitally signed message part.
More information about the Testing