Skip to content

ESP32 Fails to Connect to Enterprise WiFi (PEAP) Due to TLS 1.0 Incompatibility — WL_NO_SSID_AVAIL Reported #11364

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

Open
1 task done
Tahir-Innok opened this issue May 14, 2025 · 0 comments
Labels
Status: Awaiting triage Issue is waiting for triage

Comments

@Tahir-Innok
Copy link

Board

ESP32 Dev Module

Device Description

DevKit

Hardware Configuration

NO

Version

latest stable Release (if not listed below)

IDE Name

VSCode

Operating System

Ubuntu

Flash frequency

40MHz

PSRAM enabled

no

Upload speed

115200

Description

I'm attempting to connect an ESP32-based board to an enterprise WiFi network using WPA2-Enterprise with PEAP (Protected EAP) and MSCHAPv2 authentication. However, the connection fails.

The enterprise network supports only TLS 1.0, which is now deprecated and appears to be unsupported by current ESP32 firmware (ESP-IDF / Arduino core).

When initiating a connection, the ESP32 reports a WL_DISCONNECTED status for several seconds, then transitions to WL_NO_SSID_AVAIL, even though the network is visible and broadcasting.

Sketch

status = WiFi.begin(
      network_config.ssid.c_str(),
      WPA2_AUTH_PEAP,
      network_config.identity.c_str(),
      network_config.username.c_str(),
      network_config.password.c_str()
    );

Debug Message

After debugging alittle I understand The TLS version negotiation is handled internally by the ESP-IDF WPA2 Enterprise stack (based on wpa_supplicant), and it uses the highest possible TLS version supported by both the client and server. 

But still my question is it possible to change the TLS version to 1.0 only for WiFi stack. As for my use case its almost impossible to change/upgrade the hardware.

Other Steps to Reproduce

No response

I have checked existing issues, online documentation and the Troubleshooting Guide

  • I confirm I have checked existing issues, online documentation and Troubleshooting guide.
@Tahir-Innok Tahir-Innok added the Status: Awaiting triage Issue is waiting for triage label May 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Awaiting triage Issue is waiting for triage
Projects
None yet
Development

No branches or pull requests

1 participant