Hi all,<div>This may be an old trouble, because I googled it and found someone else had met this one even with the newest wpa_supplicant & hostapd(I use 0.5.9 in my test).The AP & CPE both use the same board with Atheros chips(AR9283, use madwifi as driver).I set the AP & CPE both in WPA + RADIUS(the EAP method is PEAP, and WPA2 have this problem too) mode and the reauthentication time is 100s(of couse u can set a less one to find it soon).</div>
<div><br></div><div>hostapd config file :</div><div>---------------------------------------------------</div><div>ieee8021x=1</div><div>eapol_key_index_workaround=0</div><div>own_ip_addr=192.168.1.2</div><div>wpa=1</div>
<div>
wpa_parwise=TKIP</div><div>ssid=test</div><div>wpa_key_mgmt=WPA-EAP</div><div>auth_server_addr=192.168.1.22</div><div>auth_server_port=1812</div><div>auth_server_shared_secret=testtest</div><div>eap_reauth_period=100</div>
<div>wpa_group_rekey=0</div><div>--------------------------------------------------</div><div>wpa_supplicant config file:</div><div>----------------------------------------------------</div><div><div>network={</div><div>
ssid="test"</div>
<div> proto=WPA</div><div> key_mgmt=WPA-EAP</div><div> pairwise=TKIP</div><div> group=TKIP</div><div> eap=PEAP</div><div> identity="test"</div><div> password="test"</div>
<div> phase1="peaplabel=0"</div><div> phase2="auth=MSCHAPV2"</div><div>}</div></div><div>----------------------------------------------------</div><div>The trouble is that when CPE need to reauthen, sometimes AP may send deauthen frame to CPE.I checked my debug log finding out that sometimes AP couldn't get the correct fourth handshake packet of 4 way handshake, so AP decide to deauthen the CPE, but what shot me is that I can sniffer the fourth packet in the air(judge from their packet length though I didn't know anything about the TKIP data).</div>
<div>So here is the question, whether the CPE/wpa_supplicant send a wrong fourth handshake packet or the AP(madwifi) decode the packet incorrectly coused this problem. I can comfirm that the 4th handshake packet is correct before sending to the l2 layer and the key matched with the AP's before sending.</div>
<div>If this problem had been solved in the newest version , please give me a hand and show me howto, thanks a lot.</div><div>PS: this problem is unpredictable, it means u may wait 10 or more than 30 minutes to find it.</div>
<div>Yours,</div><div>C.Alex</div>