hostapd and fedora19 wifi hotspot

[Gianluca Cecchi]

On Tue, Jul 16, 2013 at 3:26 PM, Gianluca Cecchi  wrote:
> Hello,
> on my laptop (Asus U36sd) I had fedora 17 and configured hostapd
> setting bridge on virbr0 and using wpa2.
> Reinstalled in fedora 19 with same settings (only changed name of wlan
> interface) apparently this doesn't work with this same hw.
> I get:
> nl80211: Failed to set interface wlp3s0 into AP mode
>
> wireless adapter:
> 03:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network
> Adapter (PCI-Express) (rev 01)
>
> I see that there is a WIFI hot spot function now on Network Manager
> (NetworkManager-0.9.8.2-8.git20130709.fc19.x86_64) but I read
> somewhere (article dated 2012) that it supports only wep, even if you
> could configure wpa.
>
> Questions:
> 1) Any hint to have hostapd running in f19 or making further debug
> actions? It was useful to use it with libvirtd "default" network
> (manually created in f19 because not automatically defined as before)
> to automatically get routing and dns information.

Possibly NetworkManager that keeps wpa_supplicant running could
interfere and prevent hostapd to set AP mode?


[g.cecchi at ope46 ~]$ sudo systemctl status wpa_supplicant
wpa_supplicant.service - WPA Supplicant daemon
   Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled)
   Active: active (running) since Tue 2013-07-16 09:18:38 CEST; 7h ago
 Main PID: 497 (wpa_supplicant)
   CGroup: name=systemd:/system/wpa_supplicant.service
           └─497 /usr/sbin/wpa_supplicant -u -f
/var/log/wpa_supplicant.log -c /etc/wpa_supplican...

Jul 16 09:18:38 ope46 systemd[1]: Starting WPA Supplicant daemon...
Jul 16 09:18:38 ope46 systemd[1]: Started WPA Supplicant daemon.


[g.cecchi at ope46 ~]$ sudo systemctl stop wpa_supplicant

But as soon as I stop wpa, NetworkManager starts it again...

Jul 16 17:03:28 ope46 systemd[1]: Stopping WPA Supplicant daemon...
Jul 16 17:03:28 ope46 systemd[1]: Stopped WPA Supplicant daemon.
Jul 16 17:03:28 ope46 NetworkManager[438]: <info> wpa_supplicant stopped
Jul 16 17:03:28 ope46 NetworkManager[438]: <info> (wlp3s0): supplicant
interface state: disabled -> down
Jul 16 17:03:28 ope46 NetworkManager[438]: <info> (wlp3s0): device
state change: disconnected -> unavailable (reason 'supplicant-failed')
[30 20 10]
Jul 16 17:03:28 ope46 NetworkManager[438]: <info> (wlp3s0):
deactivating device (reason 'supplicant-failed') [10]
Jul 16 17:03:28 ope46 dbus-daemon[338]: dbus[338]: [system] Activating
via systemd: service name='fi.w1.wpa_supplicant1'
unit='wpa_supplicant.service'
Jul 16 17:03:28 ope46 dbus[338]: [system] Activating via systemd:
service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Jul 16 17:03:28 ope46 systemd[1]: Starting WPA Supplicant daemon...
Jul 16 17:03:28 ope46 dbus-daemon[338]: dbus[338]: [system]
Successfully activated service 'fi.w1.wpa_supplicant1'
Jul 16 17:03:28 ope46 dbus[338]: [system] Successfully activated
service 'fi.w1.wpa_supplicant1'
Jul 16 17:03:28 ope46 systemd[1]: Started WPA Supplicant daemon.
Jul 16 17:03:28 ope46 NetworkManager[438]: <info> wpa_supplicant started
Jul 16 17:03:28 ope46 kernel: [27885.321311] IPv6:
ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Jul 16 17:03:28 ope46 NetworkManager[438]: <info> (wlp3s0) supports 4 scan SSIDs
Jul 16 17:03:28 ope46 NetworkManager[438]: <warn> Trying to remove a
non-existant call id.
Jul 16 17:03:28 ope46 NetworkManager[438]: <info> (wlp3s0) supports 4 scan SSIDs
Jul 16 17:03:28 ope46 NetworkManager[438]: <info> (wlp3s0) supports 4 scan SSIDs
Jul 16 17:03:28 ope46 NetworkManager[438]: <info> (wlp3s0): supplicant
interface state: starting -> ready

In
/lib/systemd/system/NetworkManager.service
and
/lib/systemd/system/wpa_supplicant.service
I didn't find any option to prevent NM to keep wpa running... is it
hardcoded? How to stop wpa and retry with hostapd?

Thanks
Gianluca