hostapd terminates with WPA HT/VHT configuration

Ann Lo at
Tue Feb 6 18:54:41 PST 2018


Thanks very much for your information. We have double-checked our
configuration files and have found that in the case of wpa=1, our
script generates a configuration file that does not provide ht_capab
and vht_capab:


In the case of wpa=2, we do have:

After we have fixed the configuration file for WPA1, hostapd works fine.


On Tue, Feb 6, 2018 at 12:45 AM, Jouni Malinen <j at> wrote:
> On Mon, Feb 05, 2018 at 04:04:31PM -0800, Ann Lo wrote:
>> When we configure hostapd v2.6 with 802.11ac, 802.11n using channel
>> 161, 20 MHz, and WPA AES security, hostapd v2.6 is able to come up
>> fine.
>> If we increase channel width to 40 MHz or 80MHz, hostapd terminates
>> with the log:
>> "Could not set channel for kernel driver".
>> Would you advise how hostapd deals with such configurations? If WPA is
>> not supposed to be used for 802.11ac and 802.11n, why is channel width
>> 20 MHz OK?
>> If we use the same configurations except that WPA (wpa=1) is replaced
>> by WPA2 (wpa=2), then all configurations work fine.
> There should be no difference to channel configuration between wpa=1 and
> wpa=2. Could you please post the two configuration files you used and
> hostapd debug log (-dd on command line) from these working (wpa=1) and
> not-working (wpa=2) cases?
> --
> Jouni Malinen                                            PGP id EFC895FA

More information about the Hostap mailing list