path: root/wpa_supplicant/mesh_mpm.c
diff options
authorTamizh chelvam <c_traja@qti.qualcomm.com>2016-08-31 14:15:47 (GMT)
committerJouni Malinen <j@w1.fi>2016-09-05 18:14:40 (GMT)
commitfc72a48a632146b042637f376f9c887f783f0a08 (patch)
tree0a97111b70fd33215605bba30c3c847d8eba8b24 /wpa_supplicant/mesh_mpm.c
parent22950d0568fddd9fcd11562d5a38c8e595ab5c99 (diff)
hostapd: Use stations nsts capability in (Re)Association Response frame
Some deployed stations incorrectly consider nsts capability in (Re)Association Response frame as required capability instead of maximum capability and if it is greater than station's capability then beamform will not happen in uplink traffic. This commit adds support for an optional workaround to use station's nsts capability in (Re)Association Response frame if the station's nsts is less than AP by using the use_sta_nsts=1 configuration parameter. This configuration is introduced in this commit and it is disabled by default. Signed-off-by: Tamizh chelvam <c_traja@qti.qualcomm.com>
Diffstat (limited to 'wpa_supplicant/mesh_mpm.c')
1 files changed, 1 insertions, 1 deletions
diff --git a/wpa_supplicant/mesh_mpm.c b/wpa_supplicant/mesh_mpm.c
index 7ffdefe..d14c7e3 100644
--- a/wpa_supplicant/mesh_mpm.c
+++ b/wpa_supplicant/mesh_mpm.c
@@ -348,7 +348,7 @@ static void mesh_mpm_send_plink_action(struct wpa_supplicant *wpa_s,
if (type != PLINK_CLOSE && wpa_s->mesh_vht_enabled) {
u8 vht_capa_oper[2 + 12 + 2 + 5];
- pos = hostapd_eid_vht_capabilities(bss, vht_capa_oper);
+ pos = hostapd_eid_vht_capabilities(bss, vht_capa_oper, 0);
pos = hostapd_eid_vht_operation(bss, pos);
wpabuf_put_data(buf, vht_capa_oper, pos - vht_capa_oper);