| Summary: | Network manager creates corrupt ifcfg files that prevent OS from suspending | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ken <redhat-bugzilla> |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | dcbw, jklimes, redhat-bugzilla |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-12 01:13:23 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Ken
2011-10-29 09:06:18 UTC
NetworkManager ifcfg-rh plugin *does* quote values if they contain problematic characters like spaces, etc. So, I'm not sure how your ifcfg file got created. Moreover NAME=value is for the name of the connection and not SSID. AP's SSID is stored in ESSID variable and it is also quoted when containing spaces. Thanks for looking into this. Let me delete the problematic files and see if I can determine what is creating them. Let me add what may be relevant information before I do in case I forget to mention it later: 1. I am not running gnome. Instead I am managing the wireless networking with nmcli and nm-tool. I did use nm-applet once so that I could enter the passphrase for my WPA2 access point. 2. The files in /etc/sysconfig/network-scripts were system generated, and the SSID was used for both the NAME and ESSID variables, and of course, the files were generated without quotes around the values for these variables. 3. When I started I was using a Fedora16-beta install. I have since been accepting all yum updates on a regular basis. 4. I have little understanding of the internals network-manager. I tried deleting the problematic network scripts and then running nm-tool, nmcli, nm-applet. I also restarted NetworkManager. Nothing re-creates the network scripts. I was able to recreate the scripts if I tried to connect to the problematic networks with nm-applet, but in this case the values were properly quoted. In other words, I cannot reproduce this problem. Sorry for wasting your time. |