Jouni, 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: channel=161 vht_oper_centr_freq_seg0_idx=155 vht_oper_chwidth=1 ht_capab= vht_capab= In the case of wpa=2, we do have: ht_capab=[HT40-][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1] vht_capab=[MAX-MPDU-11454][RXLDPC][MAX-A-MPDU-LEN-EXP3][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1] After we have fixed the configuration file for WPA1, hostapd works fine. Thanks, Ann On Tue, Feb 6, 2018 at 12:45 AM, Jouni Malinen <j@xxxxx> 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 _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
