Larry Finger wrote:
>
> I'm pissed off about the attitude.
>
> A lot of people spend a lot of time making things work. You
> misconfigure your damned system, and then you go off like this!!!!!
>
> Read the fucking error message. You have not enabled RFKILL.
I have now enabled rfkill. The hostapd error message is now:
Hardware does not support configured mode
wlan0: IEEE 802.11 Hardware does not support configured mode (2)
Could not select hw_mode and channel. (-2)
wlan0: Unable to setup interface.
rmdir[ctrl_interface]: No such file or directory
Now what?
On Sat, Jul 30, 2011 at 9:59 PM, Laurence Darby <[email protected]> wrote:
> Larry Finger wrote:
>
>> On 07/30/2011 01:14 PM, Laurence Darby wrote:
>> >
>> > I have now enabled rfkill. ?The hostapd error message is now:
>> >
>> > Hardware does not support configured mode
>> > wlan0: IEEE 802.11 Hardware does not support configured mode (2)
>> > Could not select hw_mode and channel. (-2)
>> > wlan0: Unable to setup interface.
>> > rmdir[ctrl_interface]: No such file or directory
>>
>> Please post your hostapd.conf. I don't have any ath9k hardware and
>> cannot check that it works with, but other wireless devices work with
>>
>> interface=wlan0
>> driver=nl80211
>> hw_mode=g
>> channel=1
>> ssid=test2
>> #wpa=2
>> #wpa_key_mgmt=WPA-PSK
>> #wpa_pairwise=CCMP
>> #wpa_passphrase="deleted"
>>
>> Larry
>
> Ah, thanks, that does work and my other devices can see it now!
>
> I was using the unmodified hostapd.conf, which has hw_mode=a, but
> this device only supports modes b,g & n. ?That is what the error is
> talking about, not the Master/Ad-Hoc mode which I thought it was trying
> to configure (which it is as well, actually). ?Would be good if the
> error message included the mode it's trying to configure, instead of
> "(2)", that would definitely have stopped me getting confused here.
>
> Some more reasons I didn't think this supported AP mode:
> http://linuxwireless.org/en/users/Drivers has 'no' for AP support for
> the ath9k_htc, that conflicts with the driver page, and
>
> ?# iwconfig wlan0 mode Managed
>
> works, while
>
> ?# iwconfig wlan0 mode Master
> always gives:
> Error for wireless request "Set Mode" (8B06) :
> ? ?SET failed on device wlan0 ; Invalid argument.
>
> With hostapd running, iwconfig says:
>
> wlan0 ? ? IEEE 802.11bgn ?Mode:Master ?Frequency:2.412 GHz ?Tx-Power=20
> dBm Retry ?long limit:7 ? RTS thr:off ? Fragment thr:off
> ? ? ? ? ?Power Management:off
>
> and reverts to Mode:Managed if I stop hostapd, so I'm not sure why
> iwconfig can't change it...
>
> Ok, http://linuxwireless.org/en/users/Documentation/hostapd does say
> that hw_mode needs to be set correctly, but it wasn't obvious enough
> that's what the problem was. ?The error and solution could be added to
> where ./hostapd gets started. ?Also, it refers to a
> hostapd-minimal.conf, I couldn't see that anywhere, that's why I used
> the default hostapd.conf.
>
> Laurence
>
"iwconfig wlan0 mode master" means "Set wlan0 to use the in-kernel
master mode implementation." Since mac80211 has no in-kernel support
for master mode (that's why you need hostapd - master mode is
supported from userspace), it will always fail.
Also, iwconfig uses Wireless Extensions (AKA wext) to configure the
wireless card - access to AP mode through wext is intentionally
blocked, to help the migration of userspace utilities to nl80211.
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
Larry Finger wrote:
> On 07/30/2011 01:14 PM, Laurence Darby wrote:
> >
> > I have now enabled rfkill. The hostapd error message is now:
> >
> > Hardware does not support configured mode
> > wlan0: IEEE 802.11 Hardware does not support configured mode (2)
> > Could not select hw_mode and channel. (-2)
> > wlan0: Unable to setup interface.
> > rmdir[ctrl_interface]: No such file or directory
>
> Please post your hostapd.conf. I don't have any ath9k hardware and
> cannot check that it works with, but other wireless devices work with
>
> interface=wlan0
> driver=nl80211
> hw_mode=g
> channel=1
> ssid=test2
> #wpa=2
> #wpa_key_mgmt=WPA-PSK
> #wpa_pairwise=CCMP
> #wpa_passphrase="deleted"
>
> Larry
Ah, thanks, that does work and my other devices can see it now!
I was using the unmodified hostapd.conf, which has hw_mode=a, but
this device only supports modes b,g & n. That is what the error is
talking about, not the Master/Ad-Hoc mode which I thought it was trying
to configure (which it is as well, actually). Would be good if the
error message included the mode it's trying to configure, instead of
"(2)", that would definitely have stopped me getting confused here.
Some more reasons I didn't think this supported AP mode:
http://linuxwireless.org/en/users/Drivers has 'no' for AP support for
the ath9k_htc, that conflicts with the driver page, and
# iwconfig wlan0 mode Managed
works, while
# iwconfig wlan0 mode Master
always gives:
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Invalid argument.
With hostapd running, iwconfig says:
wlan0 IEEE 802.11bgn Mode:Master Frequency:2.412 GHz Tx-Power=20
dBm Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
and reverts to Mode:Managed if I stop hostapd, so I'm not sure why
iwconfig can't change it...
Ok, http://linuxwireless.org/en/users/Documentation/hostapd does say
that hw_mode needs to be set correctly, but it wasn't obvious enough
that's what the problem was. The error and solution could be added to
where ./hostapd gets started. Also, it refers to a
hostapd-minimal.conf, I couldn't see that anywhere, that's why I used
the default hostapd.conf.
Laurence
On 07/30/2011 01:14 PM, Laurence Darby wrote:
>
> I have now enabled rfkill. The hostapd error message is now:
>
> Hardware does not support configured mode
> wlan0: IEEE 802.11 Hardware does not support configured mode (2)
> Could not select hw_mode and channel. (-2)
> wlan0: Unable to setup interface.
> rmdir[ctrl_interface]: No such file or directory
Please post your hostapd.conf. I don't have any ath9k hardware and cannot check
that it works with, but other wireless devices work with
interface=wlan0
driver=nl80211
hw_mode=g
channel=1
ssid=test2
#wpa=2
#wpa_key_mgmt=WPA-PSK
#wpa_pairwise=CCMP
#wpa_passphrase="deleted"
Larry
On Sun, Jul 31, 2011 at 12:08 AM, Larry Finger
<[email protected]> wrote:
> On 07/30/2011 01:14 PM, Laurence Darby wrote:
>>
>> I have now enabled rfkill. ?The hostapd error message is now:
>>
>> Hardware does not support configured mode
>> wlan0: IEEE 802.11 Hardware does not support configured mode (2)
>> Could not select hw_mode and channel. (-2)
>> wlan0: Unable to setup interface.
>> rmdir[ctrl_interface]: No such file or directory
i think you may be trying in 'a' mode while the card supports only 'g'
mode. please post your hostapd.conf.
ath9k_htc does supports AP mode.
>
> Please post your hostapd.conf. I don't have any ath9k hardware and cannot
> check that it works with, but other wireless devices work with
>
> interface=wlan0
> driver=nl80211
> hw_mode=g
> channel=1
> ssid=test2
> #wpa=2
> #wpa_key_mgmt=WPA-PSK
> #wpa_pairwise=CCMP
> #wpa_passphrase="deleted"
>
> Larry
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>
--
shafi