Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 448760
| Summary: | NetworkManager does not start sys-wide net. configuration, but ifup does | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | W. Michael Petullo <mike> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 10 | CC: | cra, dcbw, jfrieben, joshua, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | powerpc | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-09-14 00:48:40 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 438944 | ||
| Attachments: | |||
|
Description
W. Michael Petullo
2008-05-28 17:04:26 UTC
Created attachment 306952 [details]
/etc/sysconfig/network-scripts/ifcfg-wlan0
Created attachment 306953 [details]
/etc/sysconfig/network
Created attachment 306954 [details]
/etc/sysconfig/wpa_supplicant
Created attachment 306955 [details]
/etc/wpa_supplicant/wpa_supplicant.conf
Created attachment 306956 [details]
Log of a NetworkManager service restart (wlan0 up fails)
Could you update to: https://admin.fedoraproject.org/updates/F9/pending/NetworkManager-0.7.0-0.9.3.svn3675.fc9 and retest? 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping 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 > in. 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. I agree. 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 2.6.27.12 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 2.6.27.12-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 [1]. I am presently reviewing Fedora 12 Alpha and will provide feedback. [1] https://fedoraproject.org/wiki/Features/NetworkManagerSystemConnections Confirmed fixed in Fedora 12 Alpha. Not concerned about Fedora 10. |