Red Hat Bugzilla – Bug 448760
NetworkManager does not start sys-wide net. configuration, but ifup does
Last modified: 2009-09-13 20:48:40 EDT
Description of problem:
I have a system-wide wireless network configuration (i.e., /etc/sysconfig/network-scripts/ifcfg-
wlan0). I need to use a system-wide configuration because I use LDAP and Kerberos. Therefore, the
network must be available before I log in.
NetworkManager will not bring my network up. Running "ifup wlan0" works fine.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure system to use LDAP for NSS and Kerberos for system authentication.
2. Configure the network using the files I have attached.
3. Reboot the system.
NetworkManager does not bring up the wireless link. The boot script prints "Waiting for network...
However, once the system is done booting, manually running "ifup wlan0" does bring the link up.
NetworkManager should bring the link up.
I am using the b43 drivers on an Apple iBook G3.
My network uses a hidden SSID. Any relation to bug #448437?
I've tried restarting the NetworkManager process after disabling SELinux, but the network initialization
Created attachment 306952 [details]
Created attachment 306953 [details]
Created attachment 306954 [details]
Created attachment 306955 [details]
Created attachment 306956 [details]
Log of a NetworkManager service restart (wlan0 up fails)
Could you update to:
Also, does an 'iwlist wlan0 scan' show your AP?
Created attachment 306978 [details]
Fragment of the output from iwlist
I tried the new NetworkManager version suggested in the previous comment, but
it still did not connect.
I have attached the iwlist output corresponding to my wireless network.
I don't want to confuse this bug... but let me second this finding. If the old
/etc/init.d/network isn't going to be running by default, and NM is... NM needs
to work :-)
Could it be as simple as "anaconda only sets NM_CONTROLLED= rather than
NM_CONTROLLED=yes as well" ? This is from comment #6 of BZ #441886... but I've
noticed this myself on all my F9 machines.
I'm wondering why anaconda and NM aren't leaving us with a network that comes up
automatically... even for simple 100 Mbps eth0 connections. Shouldn't have to
do an "ifup" manually to get a network connection.
I am now using NetworkManager-0.7.0-0.9.4.svn3675.fc9.ppc but my problem remains.
When I stop the NetworkManager service and run "nm-system-settings --debug --plugins=ifcfg-
fedora," the following is printed:
** Message ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-wlan0 ...
** Message ifcfg-fedora: read connection 'System FlynComputing (wlan0)' ...
** Message ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ...
** Message ifcfg-fedora: read connection 'System eth0' ...
** Message ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-lo ...
** Message ifcfg-fedora: read connection 'System lo' ...
But, if I bring the NetworkManager service up, wlan0 is still not brought up.
This is still an issue with NetworkManager-0.7.0-0.11.svn4022.1.fc10.ppc.
This bug has been triaged
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
In my experience, wireless networks are never brought up until after logging in.
(In reply to comment #13)
> In my experience, wireless networks are never brought up until after logging
Please read the original report. Many people have valid requirements for a wireless network before logging in.
(In reply to comment #14)
> (In reply to comment #13)
> > In my experience, wireless networks are never brought up until after logging
> > in.
> Please read the original report. Many people have valid requirements for a
> wireless network before logging in.
NM will bring up ifcfg wifi connections before login if they are set ONBOOT=yes and NM_CONTROLLED=yes.
(In reply to comment #16)
> NM will bring up ifcfg wifi connections before login if they are set ONBOOT=yes
> and NM_CONTROLLED=yes.
Yes. I am using these two lines. Please see this bug's first attachment.
Created attachment 326251 [details]
Log of a failed NetworkManager service start
Created attachment 326252 [details]
Dmesg during a failed NetworkManager start
Created attachment 326253 [details]
Log of a successful ifup
Created attachment 326254 [details]
Dmesg during a successful ifup
Which kernel was this with? Is this issue better with 184.108.40.206 kernels from updates? It looks like perhaps the wifi AP wasn't seen from a scan, which could indicate driver issues. When this happens, can you run 'nm-tool' and see if NM has found your AP?
Kernel is 220.127.116.11-170.2.5.fc10.ppc.
I just noticed something funny in my dmesg output (Comment #19). The dmesg says "wlan0: authenticate with AP 00:1c:f0:ea:14:87" But, this is not the MAC of my access point. nm-tool says my access point's MAC is 00:11:50:75:94:FA.
As you can see in Comment #1, the interface's ESSID is set to FlynComputing, which nm-tool confirms is 00:11:50:75:94:FA. Why is it trying to associate with the wrong access point?
This really ought to be fixed by . I am presently reviewing Fedora 12 Alpha and will provide feedback.
Confirmed fixed in Fedora 12 Alpha. Not concerned about Fedora 10.