The Silence Map

Asked on Super User by tbhaxor, 1 year ago. No reply there for at least a week.

Getting reason=2 when connecting to hostapd AP using wpa_supplicant via EAP-MD5

I am learning EAP-MD5 and trying to break it manually (like rfc says). But unable to get to the EAP negotiation. The supplicant is getting successfully associated with the AP but then its getting deauth just after open authentication with reason code 2. Logs from wpa_supplicant ( sudo wpa_supplicant -i wlo1 -P wpa_md5.pid -c wpa_md5.conf ) wlo1: CTRL-EVENT-EAP-STARTED EAP authentication started wlo1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 wlo1: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=4 wlo1: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 4 (MD5) selected wlo1: CTRL-EVENT-EAP-SUCCESS EAP au

This question is one of 1 report of the same problem:

Getting reason=2 when connecting to hostapd AP using wpa_supplicant via EAP-MD5

Nobody has answered it yet, here or anywhere.

Related problems

Question by tbhaxor on Super User, licensed CC BY-SA. We show a short excerpt and link to the original thread as credit.