Bug 1018005 - F19 - NM doesn't use nm-connection-editor output
F19 - NM doesn't use nm-connection-editor output
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
19
i686 Linux
unspecified Severity high
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-10 20:25 EDT by Bill Gradwohl
Modified: 2013-10-11 22:08 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-10-11 04:28:51 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
hostapd.conf file I'm using. (943 bytes, text/plain)
2013-10-10 20:25 EDT, Bill Gradwohl
no flags Details

  None (edit)
Description Bill Gradwohl 2013-10-10 20:25:53 EDT
Created attachment 810828 [details]
hostapd.conf file I'm using.

Description of problem:
While getting hostapd working, I discovered that nothing I do in nm-connection-editor is used by NetworkManager at run time for a wireless hotspot. This really has nothing to do with hostapd, but its what I'm using to display this bug.

How reproducible:
Configured hostapd.conf - file attached
Configured the wireless NIC via nm-connection-editor. NIC is Atheros AR9285 with driver ath9k.
systemctl enable hostapd.service


Actual results:
Booting the box results in hostapd up, but ip addr show displays the wireless NIC state as DOWN.
Issuing an ifconfig wlp2s0 up 10.0.0.1 netmask 255.255.255.0 results in the state becoming UP. To me, this indicates that NM is not using the config I set up in nm-connection-editor.

Additional info:
I'm not attempting to use dnsmasq or dhcp on the hostapd box. I'm hard coding IP addresses on other boxes to minimize what's needed on the hostapd box. After I manually set up the IP address via ifconfig and systemctl restart hostapd.service, other boxes can connect wirelessly to the hostapd box. Restarting hostapd alone will not do it. I must manually set the IP address and then restart will make things function as expected.
Comment 1 Jirka Klimes 2013-10-11 04:28:51 EDT
nm-connection editor is *just* an editor for connection profiles. In order to apply the parameters you set there, you need to activate the connection profile to an interface using NetworkManager.
You can do this by e.g nm-applet (GUI), nmcli or some other client.

$ nmcli con up id "your profile name created in the editor"

Closing as not-a-bug. Feel free to reopen if I misunderstood the thing and you feel there is a bug (in that case attach NM logs please).
Comment 2 Bill Gradwohl 2013-10-11 22:08:00 EDT
I just nuked the box and reinstalled. The problem persists.

Using nm-connection-editor, I created a wireless ifcfg file. There is no option in NetworkManager to associate that config with the wireless NIC. Only wired NIC's have that button as an option.

The only service I have beyond a vanilla install is hostapd. With it enabled, the wireless NIC does not come up at boot time. hostapd is active, but the wireless NIC is state DOWN.

If I manually execute :
   ifconfig wlp2s0 up 10.0.0.1/24
   systemctl restart hostapd
the wireless NIC state is UP and the hotspot becomes available for my boxes to connect.

The logs show activity against wlp2s0 that fails during boot. If my ifcfg is somehow not associated with wlp2s0, then I'm missing how to set up a permanent association. I see no way to do it. nm-connection-editor clearly associates my wireless ifcfg file with the wireless NIC, so I'm at a loss to see what else is required to make the association one time permanently.

I see I can't attach any files. I have the /var/log/messages for one boot event as well as the ifcfg wireless file I'm using available.

Note You need to log in before you can comment on or make changes to this bug.