jeltz/hostap
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

tests: Make dpp_pkex_no_responder handle enabled 5 GHz channels

Browse source 
It was possible for the 5 GHz PKEX channels to be enabled, e.g., when
running "ap_ht40_csa2 dpp_pkex_no_responder" test sequence, and that
resulted in a failure in dpp_pkex_no_responder due to the unexpectedly
long wait needed for the DPP-FAIL event. Increase the wait time to allow
for 5 GHz PKEX channels to be probed.

Signed-off-by: Jouni Malinen <j@w1.fi>
This commit is contained in:
Jouni Malinen 2019-01-01 16:17:13 +02:00
parent 32bb47faa1
commit 5a5529c9f4
1 changed files with 9 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
tests/hwsim/test_dpp.py
View file

@ -3262,11 +3262,15 @@ def test_dpp_pkex_no_responder(dev, apdev):
if "FAIL" in res:
raise Exception("Failed to set PKEX data (initiator)")
ev = dev[0].wait_event(["DPP-FAIL"], timeout=15)
if ev is None:
raise Exception("DPP PKEX failure not reported")
if "No response from PKEX peer" not in ev:
raise Exception("Unexpected failure reason: " + ev)
for i in range(15):
ev = dev[0].wait_event(["DPP-TX ", "DPP-FAIL"], timeout=5)
if ev is None:
raise Exception("DPP PKEX failure not reported")
if "DPP-FAIL" not in ev:
continue
if "No response from PKEX peer" not in ev:
raise Exception("Unexpected failure reason: " + ev)
break
def test_dpp_pkex_after_retry(dev, apdev):
"""DPP and PKEX completing after retry"""