On Thu, Apr 09, 2009 at 07:51:38PM +0400, Dmitry Marakasov wrote: > * Brooks Davis (bro...@freebsd.org) wrote: > > > > Shouldn't synchronous_dhclient be ON by default then? The way it > > > is, DHCP is not used at all, I ended up with unreachable box which > > > didn't get any IP already. > > > > Unless you have one of the few interfaces that does not generate > > link status events, dhclient will be started by devd. The only ones I > > know of are a subset set of ed(4) devices, though I think imp may have > > fixed those recently with a stub ifmedia interface. > > I use ale(4). Will test some more. Couldn't the fact that the interface > is renamed be the reason?
Shouldn't be. I use renamed interfaces a fair bit. The ale(4) driver uses mii, but so lack of link events shouldn't be an issue unless the driver is buggy. > Also, how is the issue of services not starting because of no default > route/dns/network available solved when running dhclient from devd? The wait in /etc/rc.d/defaultroute. -- Brooks
pgp5WJjzRT5Bq.pgp
Description: PGP signature
