On 2016年08月01日 19:03, Johannes Berg wrote:
But why is that behaviour *correct*? We still support 40 MHz bandwidth
things, we just don't use them if we disable HT40.
Or do you mean difference between "hardware capability" and "software
capability" ?
Do you think IEEE80211_HT_CAP_SUP_WIDTH_20_40 bit should be 1 if the
hardware capable of HT40 even though HT40 is disabled by
wpa_supplicant/hostapd ?
I have tested with hostapd. I compared these 2 configfiles.
hostapd0.conf
ht_capab=[HT40-]
hostapd1.conf
#ht_capab=[HT40-]
The IEEE80211_HT_CAP_SUP_WIDTH_20_40 bit in beacon was below.
hostapd0.conf
IEEE80211_HT_CAP_SUP_WIDTH_20_40 = 1
hostapd1.conf
IEEE80211_HT_CAP_SUP_WIDTH_20_40 = 0
So I think the bit should be zero if disabled also for mesh peer.
Masashi Honma.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
