Skip to content

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

Merged
merged 1 commit into from
Mar 31, 2020

Conversation

praveenCY
Copy link
Contributor

Summary of changes

  • Add WPA3, WPA3_WPA2 Security type support in mbed-os
  • Add WPA3, WPA3_WPA2 Security changes in green tea tests
  • Add WPA3_WPA2 Security changes for Cypress Kits

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

    "wifi-password-wpa2psk": {
        "help": "WiFi WPA2 PSK Password for WPA3_WPA2 Mode",
        "value": "\"test12345678\""
    }

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

[] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[*] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[] No Tests required for this change (E.g docs only update)
[*] Covered by existing mbed-os tests (Greentea or Unittest)
[*] Tests / results supplied as part of this PR

Reviewers

@balajicyp @satya1957 @ifyall

@mergify mergify bot added the needs: work label Feb 19, 2020
@ciarmcom ciarmcom requested review from satya1957 and a team February 19, 2020 20:00
@ciarmcom
Copy link
Member

@praveenCY, thank you for your changes.
@satya1957 @ARMmbed/mbed-os-ipcore @ARMmbed/mbed-os-test @ARMmbed/mbed-os-maintainers please review.

Copy link
Contributor

@0xc0170 0xc0170 left a 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

@@ -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`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

may not

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.
Please review

@praveenCY praveenCY force-pushed the pr/wpa3_support_merge branch from 8d534da to 8b97e4c Compare February 25, 2020 18:15
@mergify mergify bot dismissed 0xc0170’s stale review February 25, 2020 18:16

Pull request has been modified.

@0xc0170 0xc0170 removed the request for review from a team February 26, 2020 15:46
@0xc0170
Copy link
Contributor

0xc0170 commented Feb 26, 2020

CI started

@ARMmbed/mbed-os-ipcore Please review

@mergify mergify bot added needs: CI and removed needs: work labels Feb 26, 2020
@mbed-ci
Copy link

mbed-ci commented Feb 26, 2020

Test run: FAILED

Summary: 1 of 8 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_cloud-client-pytest

@mergify mergify bot added needs: work and removed needs: CI labels Feb 26, 2020
@ifyall
Copy link

ifyall commented Feb 26, 2020

@0xc0170,

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 |
Copy link
Contributor

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.

@0xc0170
Copy link
Contributor

0xc0170 commented Mar 2, 2020

@ifyall There's been a known issue with client tests, I restarted it

@adbridge
Copy link
Contributor

CI started

@mbed-ci
Copy link

mbed-ci commented Mar 26, 2020

Test run: FAILED

Summary: 1 of 6 test jobs failed
Build number : 3
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_greentea-test

@mergify mergify bot added needs: work and removed needs: CI labels Mar 26, 2020
@0xc0170
Copy link
Contributor

0xc0170 commented Mar 26, 2020

TEst restarted

@adbridge
Copy link
Contributor

Device has been power cycled let's see if that fixes the issue

@adbridge
Copy link
Contributor

CI started

@mbed-ci
Copy link

mbed-ci commented Mar 27, 2020

Test run: FAILED

Summary: 1 of 6 test jobs failed
Build number : 4
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_greentea-test

@mergify mergify bot added needs: work and removed needs: CI labels Mar 27, 2020
@adbridge
Copy link
Contributor

More CI issues, retrying

@mergify mergify bot added needs: CI and removed needs: work labels Mar 27, 2020
@mbed-ci
Copy link

mbed-ci commented Mar 27, 2020

Test run: FAILED

Summary: 1 of 6 test jobs failed
Build number : 5
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_greentea-test

@0xc0170
Copy link
Contributor

0xc0170 commented Mar 30, 2020

test restarted

@0xc0170 0xc0170 merged commit fea7c1a into ARMmbed:master Mar 31, 2020
@mergify mergify bot removed the ready for merge label Mar 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants