Hi Meino,
I don't think you need to worry about the "rfkill: Cannot open RFKILL
control device" message.
I believe that's for getting status of rfkill switches (the switches on
laptops to disable the WiFi radio.)
A USB WiFi-dongle doesn't generally have those (at least the ones I've
used) and neither does my custom hardware which also gets that warning
but works fine.
I think the bigger issue is the "WARNING: net.wlan0 has started, but is
inactive.
I think the next step is trying to run wpa_supplicant by hand and see
what it has to say:
wpa_supplicant -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf -dd
(replacing the location of the config file you want to use for the one
after the -c above.) The -dd ups the debugging info displayed.
Regards,
Todd
* meino.cra...@gmx.de <meino.cra...@gmx.de> [150727 14:13]:
> Hi,
>
> shocked from over 1000 lines of configurational stuff in
> wpa_supplicant.conf I have manovered to this point
>
> The USB Wifi-dongle now is a TP-LINK WN722N with Atheros chipset AR9271
> 802.11n
> (thanks for the hint!) which driver is by far easier to compile and
> use as the hassle with this other one...
>
> I started /etc/init.d/hostapd manually and the /etc/init.d/net.wlan0
> and got this here
>
> Successfully initialized wpa_supplicant
> rfkill: Cannot open RFKILL control device
> [ ok ]
> * Starting wpa_cli on wlan0 ...
> [ ok ]
> * Backgrounding ... ...
> * WARNING: net.wlan0 has started, but is inactive
>
>
> I am confused by this...especially by "rfkill: Cannot open RFKILL control
> device...[OK]".
> It's feeling like: "Unexpected ERROR: SUCCESS"
>
>
> What is the above text is trying to tell me?
>
>
> Thank you very much in advance for any help!
> Best regards,
> Meino
>
>
>
>
>
> PS:
> Is there any stripped down version of wpa_supplicant.conf
> for AP use? Sawing that reminds me a little at manually configuring
> sendmail....
>
>
