cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
289
Views
0
Helpful
0
Replies

Some I-Pads cannot connect to OEAO602

mlieber
Level 1
Level 1

First of all: I know, OEAP602 is an very old device

but we have the issue that sometimes devices (I-Pads) cannot connect to an OEAP602. We don*t have this issue on OEAP1810.

WE have debugged the client and saw that there is an DEAUTH.

But we don't know why. Client is placed in his HomeOffice in ground Floor without any other WLAN in neighborhood

 


*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: f4:0e:01:7e:9f:e8 0 PMK-update groupcast messages sent
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: f4:0e:01:7e:9f:e8 PMK sent to mobility group
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: f4:0e:01:7e:9f:e8 Disabling re-auth since PMK lifetime can take care of same.
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: f4:0e:01:7e:9f:e8 Sending EAP-Success to mobile f4:0e:01:7e:9f:e8 (EAP Id
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: f4:0e:01:7e:9f:e8 Freeing AAACB from Dot1xCB as AAA auth is done for mobile f4:0e:01:7e:9f:e8
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: f4:0e:01:7e:9f:e8 key Desc Version FT - 0

*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: f4:0e:01:7e:9f:e8 Found an cache entry for BSSID 00:3a:9a:f7:95:09 in PMKID cache at index 0 of station f4:0e:01:7e:9f:e8
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: f4:0e:01:7e:9f:e8 Found an cache entry for BSSID 00:3a:9a:f7:95:09 in PMKID cache at index 0 of station f4:0e:01:7e:9f:e8
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: Including PMKID in M1 (16)

*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: [0000] 45 49 e5 76 61 a5 e7 80 8e bc 0e c9 09 3c 0c 51

*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: M1 - Key Data: (22)

*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: [0000] dd 14 00 0f ac 04 45 49 e5 76 61 a5 e7 80 8e bc

*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: [0016] 0e c9 09 3c 0c 51

*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: f4:0e:01:7e:9f:e8 Starting key exchange to mobile f4:0e:01:7e:9f:e8, data packets will be dropped
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: f4:0e:01:7e:9f:e8 Sending EAPOL-Key Message to mobile f4:0e:01:7e:9f:e8
state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: f4:0e:01:7e:9f:e8 Reusing allocated memory for EAP Pkt for retransmission to mobile f4:0e:01:7e:9f:e8
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: f4:0e:01:7e:9f:e8 Entering Backend Auth Success state (id=8) for mobile f4:0e:01:7e:9f:e8
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.221: f4:0e:01:7e:9f:e8 Received Auth Success while in Authenticating state for mobile f4:0e:01:7e:9f:e8
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.222: f4:0e:01:7e:9f:e8 dot1x - moving mobile f4:0e:01:7e:9f:e8 into Authenticated state
*dot1xSocketTask: Sep 27 15:41:46.241: f4:0e:01:7e:9f:e8 validating eapol pkt: key version = 2
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.241: f4:0e:01:7e:9f:e8 Received EAPOL-Key from mobile f4:0e:01:7e:9f:e8
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.241: f4:0e:01:7e:9f:e8 key Desc Version FT - 0

*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.241: f4:0e:01:7e:9f:e8 Received EAPOL-key in PTK_START state (message 2) from mobile f4:0e:01:7e:9f:e8
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.242: f4:0e:01:7e:9f:e8 Encryption Policy: 4, PTK Key Length: 48
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.242: f4:0e:01:7e:9f:e8 Successfully computed PTK from PMK!!!
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.242: f4:0e:01:7e:9f:e8 Received valid MIC in EAPOL Key Message M2!!!!!
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.242: f4:0e:01:7e:9f:e8 Compare RSN IE in association and EAPOL-M2 frame(Skip pmkIdLen:0,and grpMgmtCipherLen:0)
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.242: f4:0e:01:7e:9f:e8 Dumping RSNIE received in Association request:
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.242: 00000000: 30 14 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 0...............
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.242: 00000010: 00 0f ac 01 0c 00 ......
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.242: f4:0e:01:7e:9f:e8 Dumping RSNIE received in EAPOL M2 :
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.242: 00000000: 01 00 00 0f ac 04 01 00 00 0f ac 04 01 00 00 0f ................
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.242: 00000010: ac 01 0c 00 ....
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.242: f4:0e:01:7e:9f:e8 Not Flex client. Do not distribute PMK Key cache.
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.242: f4:0e:01:7e:9f:e8 Stopping retransmission timer for mobile f4:0e:01:7e:9f:e8
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.242: f4:0e:01:7e:9f:e8 key Desc Version FT - 0

*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.242: f4:0e:01:7e:9f:e8 key Desc Version FT - 0

*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.242: f4:0e:01:7e:9f:e8 Sending EAPOL-Key Message to mobile f4:0e:01:7e:9f:e8
state PTKINITNEGOTIATING (message 3), replay counter 00.00.00.00.00.00.00.01
*Dot1x_NW_MsgTask_0: Sep 27 15:41:46.242: f4:0e:01:7e:9f:e8 Reusing allocated memory for EAP Pkt for retransmission to mobile f4:0e:01:7e:9f:e8
*apfOpenDtlSocket: Sep 27 15:41:46.266: f4:0e:01:7e:9f:e8 Recevied management frame DEAUTH on BSSID 00:3a:9a:f7:95:09 destination addr 00:3a:9a:f7:95:09
*apfOpenDtlSocket: Sep 27 15:41:46.266: f4:0e:01:7e:9f:e8 Recevied management frame DEAUTH on BSSID 00:3a:9a:f7:95:09 destination addr 00:3a:9a:f7:95:09
*apfOpenDtlSocket: Sep 27 15:41:46.267: f4:0e:01:7e:9f:e8 Recevied management frame DEAUTH on BSSID 00:3a:9a:f7:95:09 destination addr 00:3a:9a:f7:95:09
*apfOpenDtlSocket: Sep 27 15:41:46.268: f4:0e:01:7e:9f:e8 Recevied management frame DEAUTH on BSSID 00:3a:9a:f7:95:09 destination addr 00:3a:9a:f7:95:09
*apfOpenDtlSocket: Sep 27 15:41:46.269: f4:0e:01:7e:9f:e8 Recevied management frame DEAUTH on BSSID 00:3a:9a:f7:95:09 destination addr 00:3a:9a:f7:95:09
*apfOpenDtlSocket: Sep 27 15:41:46.269: f4:0e:01:7e:9f:e8 Recevied management frame DEAUTH on BSSID 00:3a:9a:f7:95:09 destination addr 00:3a:9a:f7:95:09
*apfOpenDtlSocket: Sep 27 15:41:46.270: f4:0e:01:7e:9f:e8 Recevied management frame DEAUTH on BSSID 00:3a:9a:f7:95:09 destination addr 00:3a:9a:f7:95:09
*apfOpenDtlSocket: Sep 27 15:41:46.517: f4:0e:01:7e:9f:e8 Recevied management frame ASSOCIATION REQUEST on BSSID 00:3a:9a:f7:95:09 destination addr 00:3a:9a:f7:95:09
*apfMsConnTask_2: Sep 27 15:41:46.517: f4:0e:01:7e:9f:e8 Updating 11r vendor IE

*apfMsConnTask_2: Sep 27 15:41:46.517: f4:0e:01:7e:9f:e8 Processing assoc-req station:f4:0e:01:7e:9f:e8 AP:00:3a:9a:f7:95:00-01 ssid : WiFi-sec thread:1a94a550
*apfMsConnTask_2: Sep 27 15:41:46.517: f4:0e:01:7e:9f:e8 Station: F4:0E:01:7E:9F:E8 trying to join WLAN with RSSI -4. Checking for XOR roam conditions on AP: 00:3A:9A:F7:95:00 Slot: 1
*apfMsConnTask_2: Sep 27 15:41:46.517: f4:0e:01:7e:9f:e8 Station: F4:0E:01:7E:9F:E8 is associating to AP 00:3A:9A:F7:95:00 which is not XOR roam capable
*apfMsConnTask_2: Sep 27 15:41:46.518: f4:0e:01:7e:9f:e8 Association received from mobile on BSSID 00:3a:9a:f7:95:a9 AP OEAP-AP023
*apfMsConnTask_2: Sep 27 15:41:46.518: f4:0e:01:7e:9f:e8 Station: F4:0E:01:7E:9F:E8 trying to join WLAN with RSSI -4. Checking for XOR roam conditions on AP: 00:3A:9A:F7:95:00 Slot: 1
*apfMsConnTask_2: Sep 27 15:41:46.518: f4:0e:01:7e:9f:e8 Station: F4:0E:01:7E:9F:E8 is associating to AP 00:3A:9A:F7:95:00 which is not XOR roam capable
*apfMsConnTask_2: Sep 27 15:41:46.518: f4:0e:01:7e:9f:e8 Global 200 Clients are allowed to AP radio

 

 

We have already changed security from WPA2/AES to WPA/AES because we had the same issue with I-Phones. After this change I-Phones are working well but not the I-Pad.

Does anyone has an idea?

WLC5508 SW 8.3.150.0

 

thanks

Martin

0 Replies 0
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: