Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: dhcpcd vs dhclient
On Fri July 30 2010 12:03:51 matthew sporleder wrote:
> On Fri, Jul 30, 2010 at 12:06 AM, Chris Ross
> <cross+netbsd%distal.com@localhost>
wrote:
> > On Jul 29, 2010, at 9:28 PM, matthew sporleder wrote:
<snip>
> > I can see now that I'm getting the same failure of ntpdate. If -b is
> > required to make dhcpcd work, but I need -w to make the rest of the boot
> > process work, there seems to be an impass.
> >
> > Why had you suggested -b -t 0?
>
> I was using it so that I had an ip by the time I finished booting
> instead of waiting for dhcpcd to fail, finish booting, and then having
> to run /etc/rc.d/network restart. I think it had something to do with
> wpa_supplicant starting up too late in the boot process.
wpa_supplicant starts before dhcpcd/dhclientd, correct? I believe that problem
is that wpa_supplicant -B returns before the interface is usable. A new option
to make wpa_supplicant (-B) not return until the interface is up and
associated might be a solution.
Regards,
Sverre
Home |
Main Index |
Thread Index |
Old Index