NM fails to connect when booting ?? -[SOLVED]
tmz at pobox.com
Wed Mar 18 03:25:14 UTC 2009
William Case wrote:
> It has been reported by someone else as a medium level bug. See:
Or see the changelog of NetworkManager-0.7.0.99-3:
* Mon Mar 09 2009 Dan Williams <dcbw at redhat.com> - 1:0.7.0.99-3
- Missing ONBOOT should actually mean ONBOOT=yes (rh #489422)
Bug #489422 is "No network after last NM update"
> The bug comments gave me the following work around:
> The automatic wired network connection can be made to work by doing:
> "if and only if the flag ONBOOT in
> /etc/sysconfig/network-scripts/ifcfg-eth0 is set to "yes""
> My ifcfg-eth0 file had ONBOOT=no; I changed it to ONBOOT=yes and now my
> Internet connection is made automatically on boot.
> I would think that this is more than a medium level concern,
> particularly for new users of Fedora 10.
Well, the levels aren't really used my many maintainers (though maybe
they are for RHEL bugs, which 470477 is...). But aside from that, the
NM release on Fedora fixes the bug that a missing ONBOOT parameter is
treated differently in NM than it was by the network service. I can't
see how having ONBOOT=no and NM not starting that device could be
construed as an NM bug though. It's perhaps a bug if some tool is
automatically writing the ONBOOT=no into the ifcfg file when it
In any case, I'm glad you found the solution. :)
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
Problems are opportunity in work clothes.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 542 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20090317/018ea3de/attachment-0001.bin
More information about the users