EPA2-Enterpriseで認証がうまくいかない。WLCでデバッグをかけた結果が以下の通り。
*Dot1x_NW_MsgTask_4: Aug 30 02:48:42.983: a4:4e:31:ce:80:4c dot1x – moving mobile a4:4e:31:ce:80:4c into Connecting state
*Dot1x_NW_MsgTask_4: Aug 30 02:48:42.983: a4:4e:31:ce:80:4c Sending EAP-Request/Identity to mobile a4:4e:31:ce:80:4c (EAP Id 1)
*apfMsConnTask_3: Aug 30 02:48:46.503: a4:4e:31:ce:80:4c Processing assoc-req station:a4:4e:31:ce:80:4c AP:00:78:88:29:9a:00-00 thread:15148740
*apfMsConnTask_3: Aug 30 02:48:46.503: a4:4e:31:ce:80:4c Association received from mobile on BSSID 00:78:88:29:9a:17 AP CNORDIBJSCN01AP002
別のラップトップで実施した結果が以下の通り。
*Dot1x_NW_MsgTask_4: Aug 30 02:51:41.937: 58:94:6b:22:88:04 dot1x – moving mobile 58:94:6b:22:88:04 into Connecting state
*Dot1x_NW_MsgTask_4: Aug 30 02:51:41.937: 58:94:6b:22:88:04 Sending EAP-Request/Identity to mobile 58:94:6b:22:88:04 (EAP Id 1)
*Dot1x_NW_MsgTask_4: Aug 30 02:51:41.983: 58:94:6b:22:88:04 Reset the reauth counter since EAPOLSTART has been received!!!
*Dot1x_NW_MsgTask_4: Aug 30 02:51:41.983: 58:94:6b:22:88:04 reauth_sm state transition 1 —> 1 for mobile 58:94:6b:22:88:04 at 1x_reauth_sm.c:47
*Dot1x_NW_MsgTask_4: Aug 30 02:51:41.983: 58:94:6b:22:88:04 Received EAPOL START from mobile 58:94:6b:22:88:0
EAP request/idenitityを送ると、eapol startがクライアントから送られてくるのが正しい処理。おかしいプロセスではクライアントは再度 associationを送ってくる。まるでEAP-request/identifyが送られてこないかのように。
