使用wpa_supplicant通过EAP-MD5连接hostapd AP时出现reason=2断开问题求助

我最近在学习EAP-MD5协议，打算按照RFC文档的说明手动拆解它的认证流程，但现在卡在了EAP协商这一步。我的wpa_supplicant客户端已经成功和AP关联上了，但完成开放认证后马上就收到了Deauth帧，原因码是2。

我执行的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 authentication completed successfully
wlo1: CTRL-EVENT-DISCONNECTED bssid=42:f2:d5:36:72:f0 reason=2
wlo1: Added BSSID 42:f2:d5:36:72:f0 into ignore list, ignoring for 10 seconds
wlo1: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MyEAP" auth_failures=1 duration=10 reason=CONN_FAILED
wlo1: CTRL-EVENT-SSID-REENABLED id=0 ssid="MyEAP"
wlo1: BSSID 42:f2:d5:36:72:f0 ignore list count incre...

从日志看EAP认证已经显示成功了，但紧接着就触发了断开，reason=2对应的是“Previous authentication no longer valid”。我检查过wpa_md5.conf的EAP-MD5配置参数，也确认了AP端hostapd已经开启EAP-MD5认证，但还是找不到问题根源。有没有大佬遇到过类似情况？或者能给我一些排查方向的建议？

备注：内容来源于stack exchange，提问作者tbhaxor