aboutsummaryrefslogtreecommitdiffstats
path: root/wpa_supplicant/sme.h
diff options
context:
space:
mode:
authorMathy Vanhoef <Mathy.Vanhoef@cs.kuleuven.be>2018-08-06 19:46:34 (GMT)
committerJouni Malinen <j@w1.fi>2018-12-17 13:42:23 (GMT)
commitf9da7505bfbcc1f4a1302c97750befd3c1b8ba84 (patch)
treebd7be8df5f2a198026d926732b3afa8461f1ebd2 /wpa_supplicant/sme.h
parente63d8837ddf282e3b08b7ffd450f17523e2c8b6b (diff)
downloadhostap-f9da7505bfbcc1f4a1302c97750befd3c1b8ba84.zip
hostap-f9da7505bfbcc1f4a1302c97750befd3c1b8ba84.tar.gz
hostap-f9da7505bfbcc1f4a1302c97750befd3c1b8ba84.tar.bz2
OCV: Include and verify OCI in SA Query frames
Include an OCI element in SA Query Request and Response frames if OCV has been negotiated. On Linux, a kernel patch is needed to let clients correctly handle SA Query Requests that contain an OCI element. Without this patch, the kernel will reply to the SA Query Request itself, without verifying the included OCI. Additionally, the SA Query Response sent by the kernel will not include an OCI element. The correct operation of the AP does not require a kernel patch. Without the corresponding kernel patch, SA Query Requests sent by the client are still valid, meaning they do include an OCI element. Note that an AP does not require any kernel patches. In other words, SA Query frames sent and received by the AP are properly handled, even without a kernel patch. As a result, the kernel patch is only required to make the client properly process and respond to a SA Query Request from the AP. Without this patch, the client will send a SA Query Response without an OCI element, causing the AP to silently ignore the response and eventually disconnect the client from the network if OCV has been negotiated to be used. Signed-off-by: Mathy Vanhoef <Mathy.Vanhoef@cs.kuleuven.be>
Diffstat (limited to 'wpa_supplicant/sme.h')
0 files changed, 0 insertions, 0 deletions