Starting with F18, the ifcfg-* scripts are being written with DHCPV6C=yes set. This makes starting network interfaces take significantly longer, since few environments, even on networks with IPv6, will actually have a DHCPv6 server (so the attempts have to time out). Why is this being set by default?
I timed "ifup eth0" on a VM. With DHCPV6C=yes, ifup took 66 seconds. With that commented out, it took 3 seconds. Adding over a minute to "ifup" in the default config is unacceptable. Both cases are using DHCP for IPv4. This is on a network using RAs for IPv6 (which is probably the more common IPv6 setup, but still a small fraction of the total network setups). I think the default config should be for IPv4 DHCP and IPv6 RAs, as that covers the most common setups with the quickest activation. Anything else will take configuration; if somebody is on an IPv6-only network, they'll need to disable IPv4 DHCP (as that would also take a long time to time out), and if they are using IPv6 DHCP, they'll have to enable it.
The ifcfg files are generated by dracut in modules.d/45ifcfg/write-ifcfg.sh. I agree with having IPv6 auto configuration as default (just IPV6INIT=yes). Pavel, any comments?
Also note that for NetworkManager, DHCPV6C=yes triggers dhcpv6 configuration only if IPV6_AUTOCONF=no (it is "yes" by default for NM), if IPV6_AUTOCONF=yes, auto configuration is done despite the DHCPV6C option.
This is caused probably by commit 32ec0a762d1dce36f20857ffd222863a3d550ed7, sending a patch for review.
commit c5a742a3bf2b9b9aab835639bed5c8c7477cb3a2
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.