If a Ethernet interface is configured for DHCP, but it's not actually connected to the network, the dhcpcd client will hang until it times out, making startup really slow. The startup scripts should check to make sure that the card is actually connected to something before attempting DHCP. The mii-diag program (sys-apps/mii-diag) reports whether an Ethernet interface is actually connected to anything. Could someone add a call to mii-diag in the right place in the network startup scripts? Reproducible: Always Steps to Reproduce:
ethtool is more recent and reliable than mii-diag, but be sure to take into account the fact that some network cards don't support either of them.
/etc/conf.d/net.example shows how this can be done Robin is right though - not all networks cards support this, hence it will not be included by default. However, baselayout-1.12.0-alpha3 will contain much better parallel startup support AND give you the ability to background dhcp requests
*** Bug 123875 has been marked as a duplicate of this bug. ***
(In reply to comment #2) > /etc/conf.d/net.example shows how this can be done > > Robin is right though - not all networks cards support this, hence it will not > be included by default. > > However, baselayout-1.12.0-alpha3 will contain much better parallel startup > support AND give you the ability to background dhcp requests OpenRC these days tries to do a request again after the user canceled it, I'll look into the net.example.
