Am 16.07.2013 17:14, schrieb Gianluca Cecchi:
> Possibly NetworkManager that keeps wpa_supplicant running could
> interfere and prevent hostapd to set AP mode?
>
> [g.cecchi@ope46 ~]$ sudo systemctl status wpa_supplicant
> wpa_supplicant.service - WPA Supplicant daemon
>Loaded: loaded (/usr/
On Tue, Jul 16, 2013 at 5:18 PM, Reindl Harald wrote:
>
>
> Am 16.07.2013 17:14, schrieb Gianluca Cecchi:
>> Possibly NetworkManager that keeps wpa_supplicant running could
>> interfere and prevent hostapd to set AP mode?
>>
>> [g.cecchi@ope46 ~]$ sudo systemctl status wpa_supplicant
>> wpa_suppli
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 thi
On Tue, 16 Jul 2013 15:26:23 +0200
Gianluca Cecchi wrote:
> 1) Any hint to have hostapd running in f19 or making further debug
> actions?
I have been running hostapd successfully for a while going
from f18 to f19, so I don't think anything fundamental
changed, sounds like the new kernel drivers d
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 m
