Hi, All Radiuse rever's default EAP method is MD5. However, we only support PEAP/TTLS/TLS now, when the connect start, server will send the EAP method type to client, if the client do not support it, it will send NAK to reponse, if we don not have any other method to use, we will set the type to zero. However, there is another way to do is include the EAP method we want in the type. We will add it in 8266 soon. Thank you for your continuous attention

That is great news. As I'm sure you're aware (from all the posts on the various github repo's) there are a lot of people that are *very* interested in this! Could you give us any indication on how long it will take to implement? Forgive me my bluntness, but I'd really be disappointed to wait another 10 months to hear something...

The latest commits seem to force the device to try multiple auth modes automatically; first EAP-TLS (even if no certificates were defined by the developer - as it is my case -), thus making the authentication fail. Then, on a second try, the device seems to keep forcing the mode until the server just ignores it:

...the supplicant said 'I don't like X, please use X instead... The supplicant software is broken and does not work properly...

Not very encouraging.

In a final attempt, the device seems to suggest a different type MS-CHAP, but this one is also failing; I'm not sure why yet, It could be our server configuration.

Interesting enough, the device never suggests PEAP or perhaps, it never gets the chance to, since it seems to stay stuck in the mschapv2 mode and just keeps printing every few seconds on the serial monitor:

Rather than allowing the device to try multiple auth methods, wouldn't it be easier for all of us if the SDK included methods to allow the developers to use the correct auth method rather than trying multiple ones hoping one will work?

I will continue testing (still haven't tested EAP-TLS using certificates) and keep you all updated.

Pfff it was so long ago I really had to read all my old posts to remind myself on how to do this :-S

I made a new build environment:* Arduino 1.8.5* git version of ESP8266 core for Arduino* updated libwpa2.a and wpa2_enterprise.h from the latest commit of ESP8266_NONOS_SDK.* uploaded the same code as in the original post (but edited to use actual credentials of course).

No success. Esp8266 keeps resetting itself. I Enabled Wifi debug, serial output follows below.It does look like it is attempting mschapv2 authentication, which is what it should be doing in my case. I don't know what is causing the fatal exception.

Documentation

About Us

Espressif Systems is a fabless semiconductor company providing cutting-edge low power WiFi SoCs and wireless solutions for wireless communications and Internet of Things applications. We are the manufacturer of ESP8266EX.