WLAN Syslog Message. Ver. 1.0

Transcription

1 WLAN Syslog Message Ver. 1.0 IPN: Inprocomm RTL: RealTek ATH: Atheros Notes: 1. if not specified, the syslog message is the same for all WLAN cards. 2. words in ( ) are notes for this syslog message. Authentication & Association Message IPN: WLAN_DBG - kal_auth_request: STA(%x:%x:%x:%x:%x:%x). RTL: WLAN_DBG - rtl8185_auth_request: STA(%x:%x:%x:%x:%x:%x). ATH: none. Access Control blocks request from %x:%x:%x:%x:%x:%x. (If Access Control is enabled, you may see the above message) IPN: WLAN_DBG - kal_assoc_request: STA(%x:%x:%x:%x:%x:%x) RTL: WLAN_DBG - rtl8185_assoc_request: STA(%x:%x:%x:%x:%x:%x) ATH: WLAN_DBG - MLME Associate MAC %x:%x:%x:%x:%x:%x (If WPA/WPA2 is enabled, you will see the following message) 1.1: WLAN_DBG - WPA capable client (this STA will connect via WPA). 1.2: WLAN_DBG - WPA2 capable client (this STA will connect via WPA2). 1.3: WLAN_DBG - Non-WPA capable client (this STA will connect via WEP). (You will see one of the above message) 2.1: WLAN_DBG - Wpa_capability_check: ok. 2.2: WLAN_DBG - Wpa_capability_check: fail (You will see one of the above message and message below for 2.2 case) - WLAN_DBG - WPA status code: %d (WPA, code is 40, WPA2, code is 40~46). - WLAN_DBG - WPA IE parse fails. - Note: to overcome this failure problem do the following check: I. Check WPA/WPA2 settings in STA. If you see message 1.1, make sure the setting in STA is WPA. If you see message 1.2, make sure the setting in STA

2 II. is WPA2. If the setting in STA is correct but the failure problem still exists, the STA may not be able to support WPA+WPA2 mode. Update the STA driver or set Vigor in WPA Only or WPA2 Only mode instead. Disassociation Message Initiated by client: IPN: WLAN_DBG - kal_disassoc_indicate: STA(%x:%x:%x:%x:%x:%x) RTL: WLAN_DBG - rtl8185_disassoc_indicate: STA(%x:%x:%x:%x:%x:%x) ATH: WLAN_DBG - MLME Disassoc MAC %x:%x:%x:%x:%x:%x Initiated by router: IPN: WLAN_DBG - ipn_deauth_client %x:%x:%x:%x:%x:% RTL: none. ATH: WLAN_DBG - athg_deauth_client %x:%x:%x:%x:%x:%x.

3 WPA/PSK Message WLAN_DBG - EAPOL_START (Message above may be missing based on the STA s WPA implement) WLAN_DBG - WPA handshake start for %x:%x:%x:%x:%x:%x WPA: WLAN_DBG - TSN, Send key to: %x:%x:%x:%x:%x:%x WLAN_DBG - send 1st packet in 4-way handshake WLAN_DBG - Rx message 2 in 4-way handshake WLAN_DBG - TSN, Send key to: %x:%x:%x:%x:%x:%x WLAN_DBG - send 3rd packet in 4-way handshake WLAN_DBG - Rx message 4 in 4-way handshake WLAN_DBG - send group key WLAN_DBG - Rx group key response WLAN_DBG - WPA handshake finish for %x:%x:%x:%x:%x:%x

4 WPA2/PSK Message WLAN_DBG - EAPOL_START (Message above may be missing based on the STA s WPA implement) WLAN_DBG - WPA handshake start for %x:%x:%x:%x:%x:%x WPA: WLAN_DBG - RSN, Send key to: %x:%x:%x:%x:%x:%x WLAN_DBG - send 1st packet in 4-way handshake WLAN_DBG - Rx message 2 in 4-way handshake WLAN_DBG - RSN, Send key to: %x:%x:%x:%x:%x:%x WLAN_DBG - send 3rd packet in 4-way handshake WLAN_DBG - Rx message 4 in 4-way handshake WLAN_DBG - WPA handshake finish for %x:%x:%x:%x:%x:%x (In WPA2, group key handshake is not necessary)

5 WPA/WPA2 PSK Error Message & Possible Cause 1. WLAN_DBG - WPA frame error (MIC) from %x:%x:%x:%x:%x:%x. Cause: PSK is wrong. Fix: Set PSKt again in STA and Vigor. 2. WLAN_DBG - WPA frame error (reply counter) from %x:%x:%x:%x:%x:%x. Cause: STA s driver problem. Fix: Find and update the newest driver for STA if possible. 3. some packets are sent repeatly for a few time and then see - WLAN_DBG - Wpa_timeout_handler - WLAN_DBG - WPA handshake timeout, disconnect %x:%x:%x:%x:%x:%x Cause: STA don t receive the packets sent by Vigor or process them fast enough. Fix: the same as 1&2 or reboot STA. 4. WLAN_DBG - WLAN_DBG - EAPoL_handler: EAPOL frame from an unknown/blocked client??? Casuse: STA has been deauthenticated by Vigor but still tries to do WPA with Vigor. Fix: reboot STA or Vigor. 5. WLAN_DBG - Warning: drop EAPOL packet. Cause: the same as 4. Fix: the same as 4.

6 802.1x Message WLAN_DBG - Dot1x_EAPOL_handler: EAP_Start WLAN_DBG - Dot1x_session_start WLAN_DBG x handshake start for %x:%x:%x:%x:%x:%x WLAN_DBG - send_eapol WLAN_DBG - Dot1x_EAPOL_handler: EAP_Packet WLAN_DBG - send_radius WLAN_DBG - ACCESS CHALLENGE WLAN_DBG - send_eapol...(repeat the above message) WLAN_DBG - ACCESS ACCEPT WLAN_DBG x handshake finish for %x:%x:%x:%x:%x:%x 802.1x Error Message and Possible Cause 1. WLAN_DBG - Dot1x_session_start: RADIUS server IP is not set! Cause: RADIUS server IP in Vigor is not set. Fix: check RADIUS settings in Vigor. 2. no reponse after "WLAN_DBG - send_eapol" & then see deauthentication message. Cause: STA don t response correctly. Fix: Check 802.1x settings in STA. 3. no response after "WLAN_DBG - send_radius" & then see deauthentication message. Cause: RADIUS server don t respose correctly. Fix: Check the connection between Vigor and RADIUS server. Also check the log message on RADIUS server. 4. WLAN_DBG - Dot1x_EAPOL_handler: EAP_Logoff. 5. WLAN_DBG - ACCESS REJECT. Cause: RADIUS server reject STA s request. Fix: check STA s settings. Also check the log message on RADIUS server.