-
Notifications
You must be signed in to change notification settings - Fork 3k
Add WPA3 support in mbed-os for green tea tests #12472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@praveenCY, thank you for your changes. |
6286ca9
to
8d534da
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one typo request, otherwise looks fine to me
TESTS/network/wifi/README.md
Outdated
@@ -37,6 +37,7 @@ The general test environment consists of DUTs, base stations, a network connecti | |||
- Time protocol, [RFC 868](https://tools.ietf.org/html/rfc868) in both TCP and UDP. Port 37. | |||
- Channels to be used must be different for both APs. For secure on channel number is later referred as `<ch:secure>` and for unsecure on `<ch:unsecure>`. | |||
- MAC addresses of Wi-Fi APs must be known. These are later referred to as `<mac:secure>` and `<mac:unsecure>`. | |||
- WPA3 maynot be supported for all target platforms, Refer to target specifications before updating security protocol to WPA3 or WPA3/WPA2 in `mbed_app.json` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
may not
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done.
Please review
8d534da
to
8b97e4c
Compare
Pull request has been modified.
CI started @ARMmbed/mbed-os-ipcore Please review |
Test run: FAILEDSummary: 1 of 8 test jobs failed Failed test jobs:
|
I can't access the failing logs from the cloud test. Can you provide them to @praveenCY and I? Thank you in advance, Ian |
@@ -58,6 +59,8 @@ Please refer to the following table for priorities of test cases. Priorities are | |||
| | | NSAPI_SECURITY_WPA | SHOULD | | |||
| | | NSAPI_SECURITY_WPA2 | SHOULD | | |||
| | | NSAPI_SECURITY_WPA_WPA2 | MUST | | |||
| | | NSAPI_SECURITY_WPA3_WPA2 | SHOULD | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer NSAPI_SECURITY_WPA2_WPA3 for consistency. But this is just my opinion and can be ignored if no one else feels the same.
@ifyall There's been a known issue with client tests, I restarted it |
CI started |
Test run: FAILEDSummary: 1 of 6 test jobs failed Failed test jobs:
|
TEst restarted |
Device has been power cycled let's see if that fixes the issue |
CI started |
Test run: FAILEDSummary: 1 of 6 test jobs failed Failed test jobs:
|
More CI issues, retrying |
Test run: FAILEDSummary: 1 of 6 test jobs failed Failed test jobs:
|
test restarted |
Summary of changes
WPA3_WPA2 Mode in STA enables to connect to WPA2 AP or WPA3 AP with same SSID and password.
Also added option to support different password WPA2_PSK for above case using below configuration in mbed_app.json
Green tea tests does not have target based filtering added till now and this security mode will fail for targets which does not support WPA3. So user needs to check target specfications before updating mbed_app.json to WPA3 security mode.
NOTE: One more way to support is to add target specific WPA3 support "WIFI_WPA3_SUPPORT" in targets.json and new green tea test in wifi just for WPA3
master...praveenCY:pr/wpa3_new_greentea_test
Impact of changes
Migration actions required
Documentation
Refer to "get_security : NSAPI_SECURITY_WPA3" print in the below logs which confirms the security type used for this test
greentea_CY8CKIT_062S2_43012_WPA3.txt
greentea_CY8CKIT_062_WIFI_BT_WPA3.txt
Pull request type
Test results
Reviewers
@balajicyp @satya1957 @ifyall