Description of problem: The NetworkManager service does not configure devices with "NM_CONTROLLED=yes" in /etc/sysconfig/network-scripts/ifcfg-eth0 until after GUI authentication has occurred (regardless of whether the "ONBOOT" variable is set to "yes"). This prevents network-based authentication (NIS, LDAP, Kerberos, AD) from succeeding. Affected Version: NetworkManager 0.7.0-0.6.7.svn3235.fc8 How reproducible: Always reproducable with "ONBOOT=yes" and "NM_CONTROLLED=yes" set in /etc/sysconfig/network-scripts. Actual results: By default, the "network" service is disabled in Fedora 8 and startup services such as NTP and Winbind fail prior to NetworkManager starting. The ethernet device and "Winbind" can be manually restarted from the console to re-enable network authentication. Upon exiting the X Window System, the ethernet device is disabled again. This requires "network" and "winbind" to be restarted again before the next user can log into the system. Expected results: NetworkManager should start prior to any network service. If "ONBOOT=yes" and "NC_CONTROLLED=yes" then the network should be enabled regardless of the GUI login state. When the user exits the session, networking should remain enabled so the next user can log onto the system using network authentication. Additional info: Evolution and Pidgin are linked with NetworkManager and report the network is unavailable when "NM_CONTROLLED=no" and the "network" service is started at boot. My company uses Kerberos 5 to authenticate users and Winbind to get user information via Active Directory though all forms of network authentication are affected by the lack of networking during interactive login.
Latest rawhide and F8-updates-testing builds have the system settings service enabled, which fixes this issue.