Description
Related area
WiFi
Hardware specification
All WiFi capbale SoCs
Is your feature request related to a problem?
The WiFi.begin()
overload for WPA2-Enterprise added in #6398 seems to default to either MSCHAPV2 or MSCHAP as the phase 2 method for EAP-TTLS. There is no parameter to change the TTLS phase 2 method. However, my university network requires using PAP as the phase 2 method. Currently, I am working around this by calling esp_wifi_sta_wpa2_ent_set_ttls_phase2_method(ESP_EAP_TTLS_PHASE2_PAP);
before calling WiFi.begin(...)
I believe similar problems have been reported in #6427 and #5483.
Describe the solution you'd like
It would be nice if an overload of WiFi.begin() can be added that accepts a esp_eap_ttls_phase2_types
as a parameter so the user can select which TTLS phase 2 method they would like to use.
Alternatively, WiFi.begin()
could try all available phase 2 options for TTLS. Which could make it easier to use and more "plug and play". Although I am not sure if that is a good idea since I have very limited knowledge of WPA2-Enterprise.
Describe alternatives you've considered
I have used the following workaround to connect to my school network
esp_wifi_sta_wpa2_ent_set_ttls_phase2_method(ESP_EAP_TTLS_PHASE2_PAP);
WiFi.begin(ssid, WPA2_AUTH_TTLS, EAP_IDENTITY, EAP_USERNAME, EAP_PASSWORD);
This works although it took considerable research to find. I think the WiFi library would be more user-friendly if the option is available in WiFi.begin()
and didn't require a separate call to an ESP-IDF function.
Additional context
No response
I have checked existing list of Feature requests and the Contribution Guide
- I confirm I have checked existing list of Feature requests and Contribution Guide.
Metadata
Metadata
Assignees
Type
Projects
Status