The newest /etc/conf.d/net.lo file in openrc (0.11.2) has a "waiting for carrier" (mis)feature enabled by default. If you rely on meta devices *cough*bridges*cough* that doens't supply carrier sense your next reboot will be full of fail. While this can be worked around by setting "carrier_timout" to zero [quote]# Incase users don't want this nice feature ...[endquote], if you don't know to do this before your reboot you will have to go find this using a local console. That's an "existing system" breaker lying right there in a raw emerge. I know this from having it take out my home firewall and one of my laptops. It's also pretty sure to submarine anybody using Xen. This "nice feature" needs to be re-implemented (and tested) using a non-trivial network config before it escapes ~ARCH. Heck, it would have been nice if that happened _before_ it got _into_ ~ARCH... 8-) The following was one of my config files that was so-boned by the new breakage until I added the feature squelching carrier_timout disable. ##### Begin Config ##### carrier_timeout=0 modules="iproute2 dhcpcd wpa_supplicant" interfaces="br0" bridge_br0="" forward_delay_br0="0" stp_state_br0="0" depend_wlan0() { provide !net } depend_eth0() { provide !net after br0 } bridge_add_eth0="br0" config_br0="null" config_eth0="null" config_wlan0="null" postup_eth0() { ip address flush dev ${IFACE} return 0; }
P.S. don't worry about the postup_eth0 thing. I didn't include the pre/post up/down functions that make the per-interface postup work as it is bash specific and that is apparently frowned uppon by the openrc reason de arte.
*** This bug has been marked as a duplicate of bug 439938 ***
