Default to supporting both, TKIP and CCMP on WPA2 AP #1

Closed
TobleMiner wants to merge 1 commits from feature/wpa2-tkip-ccmp-ap into old_version
TobleMiner commented 2022-09-14 16:15:40 +02:00 (Migrated from github.com)

From testing it seems that some clients might have problems connecting to CCMP-only WPA2 APs.
While not optimal from a security perspective his commit enables TKIP support. This might allow a broader range of devices to connect to the chargers AP.

From testing it seems that some clients might have problems connecting to CCMP-only WPA2 APs. While not optimal from a security perspective his commit enables TKIP support. This might allow a broader range of devices to connect to the chargers AP.
TobleMiner commented 2022-09-15 08:49:29 +02:00 (Migrated from github.com)

Nvm, I think this is not a problem and should be working correctly out of the box (https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/network/esp_wifi.html#_CPPv416wifi_ap_config_t describes how pairwise cipher behaves if set up with invalid value)

Nvm, I think this is not a problem and should be working correctly out of the box (https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/network/esp_wifi.html#_CPPv416wifi_ap_config_t describes how pairwise cipher behaves if set up with invalid value)

Pull request closed

Sign in to join this conversation.
No description provided.