Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Windows 7 w/Intel 6205n doesn't work with CCKM enabled on WLAN?

Hello All,

Windows 7 SP1

Intel 6205 - Driver Rev. 15.1.1.1 (just tried updating it, was 14.2)

WLC5508 w/ 7.2 Code

WLAN is configured for WPA+WPA2 with MAC Filtering

WPA2 Policy - Yes w/AES

Auth Key MGMT -  802.1x + CCKM

ACS Server 4.2(1) Build 15 Patch 7

     I'm trying to setup PEAP with MAC-Filtering for a bunch of devices that will be coming in this summer and having some issues.   I can get PEAP w/MAC Filtering to work, but I was hoping to have 802.1x + CCKM enabled for some versatility, but it's not working well with my test laptop.   If I have CCKM turned on the WLAN and try and connect, it will authenticate and show authenticated on ACS, but just keep spinning and spinning on laptop until it finally fails and disconnects.   This is using either the Intel PROSet Client or Windows.  However, if I turned CCKM off and leave it to plain jane 802.1x, it connects just fine.

Here's the client debug and thank you for any help.


   *apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c Adding mobile on LWAPP AP 5c:50:15:e6:63:90(1)

*apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c Association received from mobile on AP 5c:50:15:e6:63:90

*apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c 0.0.0.0 START (0) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1697)

*apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c 0.0.0.0 START (0) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1864)

*apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c Applying site-specific Local Bridging override for station 08:11:96:5a:9b:0c - vapId 7, site 'FHSWIFI', interface 'management'

*apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c Applying Local Bridging Interface Policy for station 08:11:96:5a:9b:0c - vlan 0, interface id 0, interface 'management'

*apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c Applying site-specific override for station 08:11:96:5a:9b:0c - vapId 7, site 'FHSWIFI', interface 'management'

*apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c 0.0.0.0 START (0) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1697)

*apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c 0.0.0.0 START (0) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1864)

*apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c processSsidIE  statusCode is 0 and status is 0

*apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c processSsidIE  ssid_done_flag is 0 finish_flag is 0

*apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c STA - rates (6): 152 36 176 72 96 108 0 0 0 0 0 0 0 0 0 0

*apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c suppRates  statusCode is 0 and gotSuppRatesElement is 1

*apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c Processing RSN IE type 48, length 18 for mobile 08:11:96:5a:9b:0c

*apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c CCKM: Mobile is using CCKM

*apfMsConnTask_4: Jun 01 18:01:03.665: 08:11:96:5a:9b:0c Received RSN IE with 0 PMKIDs from mobile 08:11:96:5a:9b:0c

*apfMsConnTask_4: Jun 01 18:01:03.665: 08:11:96:5a:9b:0c Setting active key cache index 8 ---> 8

*apfMsConnTask_4: Jun 01 18:01:03.665: 08:11:96:5a:9b:0c unsetting PmkIdValidatedByAp

*apfMsConnTask_4: Jun 01 18:01:03.665: 08:11:96:5a:9b:0c apfProcessAssocReq (apf_80211.c:6171) Changing state for mobile 08:11:96:5a:9b:0c on AP 5c:50:15:e6:63:90 from Idle to AAA Pending

*apfMsConnTask_4: Jun 01 18:01:03.665: 08:11:96:5a:9b:0c Scheduling deletion of Mobile Station:  (callerId: 20) in 10 seconds

*apfReceiveTask: Jun 01 18:01:03.667: 08:11:96:5a:9b:0c Received SGT for this Client.

*apfReceiveTask: Jun 01 18:01:03.667: 08:11:96:5a:9b:0c 0.0.0.0 START (0) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1697)

*apfReceiveTask: Jun 01 18:01:03.667: 08:11:96:5a:9b:0c 0.0.0.0 START (0) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1864)

*apfReceiveTask: Jun 01 18:01:03.667: 08:11:96:5a:9b:0c Applying site-specific override for station 08:11:96:5a:9b:0c - vapId 7, site 'FHSWIFI', interface 'management'

*apfReceiveTask: Jun 01 18:01:03.667: 08:11:96:5a:9b:0c 0.0.0.0 START (0) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1697)

*apfReceiveTask: Jun 01 18:01:03.667: 08:11:96:5a:9b:0c 0.0.0.0 START (0) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1864)

*apfReceiveTask: Jun 01 18:01:03.667: 08:11:96:5a:9b:0c Inserting AAA Override struct for mobile

MAC: 08:11:96:5a:9b:0c, source 2

*apfReceiveTask: Jun 01 18:01:03.667: 08:11:96:5a:9b:0c 0.0.0.0 START (0) Initializing policy

*apfReceiveTask: Jun 01 18:01:03.667: 08:11:96:5a:9b:0c 0.0.0.0 START (0) Change state to AUTHCHECK (2) last state AUTHCHECK (2)

*apfReceiveTask: Jun 01 18:01:03.668: 08:11:96:5a:9b:0c 0.0.0.0 AUTHCHECK (2) Change state to 8021X_REQD (3) last state 8021X_REQD (3)

*apfReceiveTask: Jun 01 18:01:03.668: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) DHCP Not required on AP 5c:50:15:e6:63:90 vapId 7 apVapId 1for this client

*apfReceiveTask: Jun 01 18:01:03.668: 08:11:96:5a:9b:0c Not Using WMM Compliance code qosCap 00

*apfReceiveTask: Jun 01 18:01:03.668: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 5c:50:15:e6:63:90 vapId 7 apVapId 1

*apfReceiveTask: Jun 01 18:01:03.668: 08:11:96:5a:9b:0c apfMsAssoStateInc

*apfReceiveTask: Jun 01 18:01:03.668: 08:11:96:5a:9b:0c apfPemAddUser2 (apf_policy.c:268) Changing state for mobile 08:11:96:5a:9b:0c on AP 5c:50:15:e6:63:90 from AAA Pending to Associated

*apfReceiveTask: Jun 01 18:01:03.668: 08:11:96:5a:9b:0c Stopping deletion of Mobile Station: (callerId: 48)

*apfReceiveTask: Jun 01 18:01:03.668: 08:11:96:5a:9b:0c Sending Assoc Response to station on BSSID 5c:50:15:e6:63:90 (status 0) ApVapId 1 Slot 1

*apfReceiveTask: Jun 01 18:01:03.668: 08:11:96:5a:9b:0c apfProcessRadiusAssocResp (apf_80211.c:2504) Changing state for mobile 08:11:96:5a:9b:0c on AP 5c:50:15:e6:63:90 from Associated to Associated

*apfMsConnTask_4: Jun 01 18:01:03.669: 08:11:96:5a:9b:0c Updating AID for REAP AP Client 5c:50:15:e6:63:90 - AID ===> 1

*dot1xMsgTask: Jun 01 18:01:03.670: 08:11:96:5a:9b:0c Station 08:11:96:5a:9b:0c setting dot1x reauth timeout = 0

*dot1xMsgTask: Jun 01 18:01:03.670: 08:11:96:5a:9b:0c Stopping reauth timeout for 08:11:96:5a:9b:0c

*dot1xMsgTask: Jun 01 18:01:03.670: 08:11:96:5a:9b:0c dot1x - moving mobile 08:11:96:5a:9b:0c into Connecting state

*dot1xMsgTask: Jun 01 18:01:03.670: 08:11:96:5a:9b:0c Sending EAP-Request/Identity to mobile 08:11:96:5a:9b:0c (EAP Id 1)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.673: 08:11:96:5a:9b:0c Received EAPOL START from mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.673: 08:11:96:5a:9b:0c dot1x - moving mobile 08:11:96:5a:9b:0c into Connecting state

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.673: 08:11:96:5a:9b:0c Sending EAP-Request/Identity to mobile 08:11:96:5a:9b:0c (EAP Id 2)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.695: 08:11:96:5a:9b:0c Received EAPOL EAPPKT from mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.695: 08:11:96:5a:9b:0c Received EAP Response packet with mismatching id (currentid=2, eapid=1) from mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.714: 08:11:96:5a:9b:0c Received EAPOL EAPPKT from mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.714: 08:11:96:5a:9b:0c Received Identity Response (count=2) from mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.714: 08:11:96:5a:9b:0c EAP State update from Connecting to Authenticating for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.714: 08:11:96:5a:9b:0c dot1x - moving mobile 08:11:96:5a:9b:0c into Authenticating state

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.714: 08:11:96:5a:9b:0c Entering Backend Auth Response state for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.716: 08:11:96:5a:9b:0c Processing Access-Challenge for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.716: 08:11:96:5a:9b:0c Entering Backend Auth Req state (id=98) for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.716: 08:11:96:5a:9b:0c WARNING: updated EAP-Identifier 2 ===> 98 for STA 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.716: 08:11:96:5a:9b:0c Sending EAP Request from AAA to mobile 08:11:96:5a:9b:0c (EAP Id 98)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.718: 08:11:96:5a:9b:0c Received EAPOL EAPPKT from mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.718: 08:11:96:5a:9b:0c Received EAP Response from mobile 08:11:96:5a:9b:0c (EAP Id 98, EAP Type 3)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.718: 08:11:96:5a:9b:0c Entering Backend Auth Response state for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.719: 08:11:96:5a:9b:0c Processing Access-Challenge for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.719: 08:11:96:5a:9b:0c Entering Backend Auth Req state (id=99) for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.719: 08:11:96:5a:9b:0c Sending EAP Request from AAA to mobile 08:11:96:5a:9b:0c (EAP Id 99)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.722: 08:11:96:5a:9b:0c Received EAPOL EAPPKT from mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.722: 08:11:96:5a:9b:0c Received EAP Response from mobile 08:11:96:5a:9b:0c (EAP Id 99, EAP Type 25)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.722: 08:11:96:5a:9b:0c Entering Backend Auth Response state for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.724: 08:11:96:5a:9b:0c Processing Access-Challenge for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.724: 08:11:96:5a:9b:0c Entering Backend Auth Req state (id=100) for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.724: 08:11:96:5a:9b:0c Sending EAP Request from AAA to mobile 08:11:96:5a:9b:0c (EAP Id 100)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.726: 08:11:96:5a:9b:0c Received EAPOL EAPPKT from mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.726: 08:11:96:5a:9b:0c Received EAP Response from mobile 08:11:96:5a:9b:0c (EAP Id 100, EAP Type 25)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.726: 08:11:96:5a:9b:0c Entering Backend Auth Response state for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.728: 08:11:96:5a:9b:0c Processing Access-Challenge for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.728: 08:11:96:5a:9b:0c Entering Backend Auth Req state (id=101) for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.728: 08:11:96:5a:9b:0c Sending EAP Request from AAA to mobile 08:11:96:5a:9b:0c (EAP Id 101)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.730: 08:11:96:5a:9b:0c Received EAPOL EAPPKT from mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.730: 08:11:96:5a:9b:0c Received EAP Response from mobile 08:11:96:5a:9b:0c (EAP Id 101, EAP Type 25)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.730: 08:11:96:5a:9b:0c Entering Backend Auth Response state for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.732: 08:11:96:5a:9b:0c Processing Access-Challenge for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.732: 08:11:96:5a:9b:0c Entering Backend Auth Req state (id=102) for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.732: 08:11:96:5a:9b:0c Sending EAP Request from AAA to mobile 08:11:96:5a:9b:0c (EAP Id 102)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.734: 08:11:96:5a:9b:0c Received EAPOL EAPPKT from mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.734: 08:11:96:5a:9b:0c Received EAP Response from mobile 08:11:96:5a:9b:0c (EAP Id 102, EAP Type 25)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.734: 08:11:96:5a:9b:0c Entering Backend Auth Response state for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.739: 08:11:96:5a:9b:0c Processing Access-Challenge for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.739: 08:11:96:5a:9b:0c Entering Backend Auth Req state (id=103) for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.739: 08:11:96:5a:9b:0c Sending EAP Request from AAA to mobile 08:11:96:5a:9b:0c (EAP Id 103)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.742: 08:11:96:5a:9b:0c Received EAPOL EAPPKT from mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.742: 08:11:96:5a:9b:0c Received EAP Response from mobile 08:11:96:5a:9b:0c (EAP Id 103, EAP Type 25)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.742: 08:11:96:5a:9b:0c Entering Backend Auth Response state for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.744: 08:11:96:5a:9b:0c Processing Access-Challenge for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.744: 08:11:96:5a:9b:0c Entering Backend Auth Req state (id=104) for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.744: 08:11:96:5a:9b:0c Sending EAP Request from AAA to mobile 08:11:96:5a:9b:0c (EAP Id 104)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.746: 08:11:96:5a:9b:0c Received EAPOL EAPPKT from mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.746: 08:11:96:5a:9b:0c Received EAP Response from mobile 08:11:96:5a:9b:0c (EAP Id 104, EAP Type 25)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.746: 08:11:96:5a:9b:0c Entering Backend Auth Response state for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.748: 08:11:96:5a:9b:0c Processing Access-Challenge for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.748: 08:11:96:5a:9b:0c Entering Backend Auth Req state (id=105) for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.748: 08:11:96:5a:9b:0c Sending EAP Request from AAA to mobile 08:11:96:5a:9b:0c (EAP Id 105)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.750: 08:11:96:5a:9b:0c Received EAPOL EAPPKT from mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.750: 08:11:96:5a:9b:0c Received EAP Response from mobile 08:11:96:5a:9b:0c (EAP Id 105, EAP Type 25)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.750: 08:11:96:5a:9b:0c Entering Backend Auth Response state for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.752: 08:11:96:5a:9b:0c Processing Access-Accept for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c Resetting web IPv4 acl from 255 to 255

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1697)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1864)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c Applying site-specific override for station 08:11:96:5a:9b:0c - vapId 7, site 'FHSWIFI', interface 'management'

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1697)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1864)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c Inserting AAA Override struct for mobile

MAC: 08:11:96:5a:9b:0c, source 4

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1697)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1864)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c Applying Local Bridging Interface Policy for station 08:11:96:5a:9b:0c - vlan 222, interface id 14, interface 'v222'

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c Setting re-auth timeout to 0 seconds, got from WLAN config.

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c Station 08:11:96:5a:9b:0c setting dot1x reauth timeout = 0

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c Stopping reauth timeout for 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c Username entry (rjwilliams) created for mobile, length = 253

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c Username entry (rjwilliams) created in mscb for mobile, length = 253

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c Creating a PKC PMKID Cache entry for station 08:11:96:5a:9b:0c (RSN 2)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c Resetting MSCB PMK Cache Entry 0 for station 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c Setting active key cache index 8 ---> 8

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c Setting active key cache index 8 ---> 0

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c Adding BSSID 5c:50:15:e6:63:9f to PMKID cache at index 0 for station 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: New PMKID: (16)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753:      [0000] 11 de cf c5 16 be 1d 23 31 41 21 d1 38 32 fd 5d

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c Disabling re-auth since PMK lifetime can take care of same.

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.753: 08:11:96:5a:9b:0c CCKM: Create a global PMK cache entry

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.754: 08:11:96:5a:9b:0c unsetting PmkIdValidatedByAp

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.754: 08:11:96:5a:9b:0c Sending EAP-Success to mobile 08:11:96:5a:9b:0c (EAP Id 105)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.754: 08:11:96:5a:9b:0c Found an cache entry for BSSID 5c:50:15:e6:63:9f in PMKID cache at index 0 of station 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.754: 08:11:96:5a:9b:0c Found an cache entry for BSSID 5c:50:15:e6:63:9f in PMKID cache at index 0 of station 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.754: Including PMKID in M1  (16)

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.754:      [0000] 11 de cf c5 16 be 1d 23 31 41 21 d1 38 32 fd 5d

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.754: 08:11:96:5a:9b:0c Starting key exchange to mobile 08:11:96:5a:9b:0c, data packets will be dropped

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.754: 08:11:96:5a:9b:0c Sending EAPOL-Key Message to mobile 08:11:96:5a:9b:0c

   state INITPMK (message 1), replay counter 00.00.00.00.00.00.00.00

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.754: 08:11:96:5a:9b:0c Entering Backend Auth Success state (id=105) for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.754: 08:11:96:5a:9b:0c Received Auth Success while in Authenticating state for mobile 08:11:96:5a:9b:0c

*Dot1x_NW_MsgTask_4: Jun 01 18:01:03.754: 08:11:96:5a:9b:0c dot1x - moving mobile 08:11:96:5a:9b:0c into Authenticated state

*osapiBsnTimer: Jun 01 18:01:04.926: 08:11:96:5a:9b:0c 802.1x 'timeoutEvt' Timer expired for station 08:11:96:5a:9b:0c and for message = M2

*dot1xMsgTask: Jun 01 18:01:04.926: 08:11:96:5a:9b:0c Retransmit 1 of EAPOL-Key M1 (length 121) for mobile 08:11:96:5a:9b:0c

*osapiBsnTimer: Jun 01 18:01:05.926: 08:11:96:5a:9b:0c 802.1x 'timeoutEvt' Timer expired for station 08:11:96:5a:9b:0c and for message = M2

*dot1xMsgTask: Jun 01 18:01:05.926: 08:11:96:5a:9b:0c Retransmit 2 of EAPOL-Key M1 (length 121) for mobile 08:11:96:5a:9b:0c

*osapiBsnTimer: Jun 01 18:01:06.926: 08:11:96:5a:9b:0c 802.1x 'timeoutEvt' Timer expired for station 08:11:96:5a:9b:0c and for message = M2

*dot1xMsgTask: Jun 01 18:01:06.926: 08:11:96:5a:9b:0c Retransmit failure for EAPOL-Key M1 to mobile 08:11:96:5a:9b:0c, retransmit count 3, mscb deauth count 0

*dot1xMsgTask: Jun 01 18:01:06.926: 08:11:96:5a:9b:0c Resetting MSCB PMK Cache Entry 0 for station 08:11:96:5a:9b:0c

*dot1xMsgTask: Jun 01 18:01:06.926: 08:11:96:5a:9b:0c Removing BSSID 5c:50:15:e6:63:9f from PMKID cache of station 08:11:96:5a:9b:0c

*dot1xMsgTask: Jun 01 18:01:06.926: 08:11:96:5a:9b:0c Setting active key cache index 0 ---> 8

*dot1xMsgTask: Jun 01 18:01:06.928: 08:11:96:5a:9b:0c Sent Deauthenticate to mobile on BSSID 5c:50:15:e6:63:90 slot 1(caller 1x_ptsm.c:534)

*dot1xMsgTask: Jun 01 18:01:06.928: 08:11:96:5a:9b:0c Scheduling deletion of Mobile Station:  (callerId: 57) in 10 seconds

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c Association received from mobile on AP 5c:50:15:e6:63:90

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1697)

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1864)

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c Applying site-specific Local Bridging override for station 08:11:96:5a:9b:0c - vapId 7, site 'FHSWIFI', interface 'management'

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c Applying Local Bridging Interface Policy for station 08:11:96:5a:9b:0c - vlan 0, interface id 0, interface 'management'

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c Applying site-specific override for station 08:11:96:5a:9b:0c - vapId 7, site 'FHSWIFI', interface 'management'

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1697)

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1864)

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c processSsidIE  statusCode is 0 and status is 0

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c processSsidIE  ssid_done_flag is 0 finish_flag is 0

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c STA - rates (6): 152 36 176 72 96 108 0 0 0 0 0 0 0 0 0 0

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c suppRates  statusCode is 0 and gotSuppRatesElement is 1

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c Processing RSN IE type 48, length 18 for mobile 08:11:96:5a:9b:0c

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c CCKM: Mobile is using CCKM

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c Received RSN IE with 0 PMKIDs from mobile 08:11:96:5a:9b:0c

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c Setting active key cache index 8 ---> 8

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c unsetting PmkIdValidatedByAp

*apfMsConnTask_4: Jun 01 18:01:07.091: 08:11:96:5a:9b:0c apfMsAssoStateDec

*apfMsConnTask_4: Jun 01 18:01:07.092: 08:11:96:5a:9b:0c apfProcessAssocReq (apf_80211.c:6171) Changing state for mobile 08:11:96:5a:9b:0c on AP 5c:50:15:e6:63:90 from Associated to AAA Pending

*apfMsConnTask_4: Jun 01 18:01:07.092: 08:11:96:5a:9b:0c Scheduling deletion of Mobile Station:  (callerId: 20) in 10 seconds

*apfReceiveTask: Jun 01 18:01:07.095: 08:11:96:5a:9b:0c Received SGT for this Client.

*apfReceiveTask: Jun 01 18:01:07.095: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1697)

*apfReceiveTask: Jun 01 18:01:07.095: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1864)

*apfReceiveTask: Jun 01 18:01:07.096: 08:11:96:5a:9b:0c Applying site-specific override for station 08:11:96:5a:9b:0c - vapId 7, site 'FHSWIFI', interface 'management'

*apfReceiveTask: Jun 01 18:01:07.096: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1697)

*apfReceiveTask: Jun 01 18:01:07.096: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1864)

*apfReceiveTask: Jun 01 18:01:07.096: 08:11:96:5a:9b:0c Inserting AAA Override struct for mobile

MAC: 08:11:96:5a:9b:0c, source 2

*apfReceiveTask: Jun 01 18:01:07.096: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Changing IPv4 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1697)

*apfReceiveTask: Jun 01 18:01:07.096: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Changing IPv6 ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller apf_policy.c:1864)

*apfReceiveTask: Jun 01 18:01:07.096: 08:11:96:5a:9b:0c Applying Local Bridging Interface Policy for station 08:11:96:5a:9b:0c - vlan 222, interface id 14, interface 'v222'

*apfReceiveTask: Jun 01 18:01:07.096: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Initializing policy

*apfReceiveTask: Jun 01 18:01:07.096: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Change state to AUTHCHECK (2) last state 8021X_REQD (3)

*apfReceiveTask: Jun 01 18:01:07.096: 08:11:96:5a:9b:0c 0.0.0.0 AUTHCHECK (2) Change state to 8021X_REQD (3) last state 8021X_REQD (3)

*apfReceiveTask: Jun 01 18:01:07.096: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) DHCP Not required on AP 5c:50:15:e6:63:90 vapId 7 apVapId 1for this client

*apfReceiveTask: Jun 01 18:01:07.096: 08:11:96:5a:9b:0c Not Using WMM Compliance code qosCap 00

*apfReceiveTask: Jun 01 18:01:07.096: 08:11:96:5a:9b:0c 0.0.0.0 8021X_REQD (3) Plumbed mobile LWAPP rule on AP 5c:50:15:e6:63:90 vapId 7 apVapId 1

*apfReceiveTask: Jun 01 18:01:07.096: 08:11:96:5a:9b:0c apfMsAssoStateInc

*apfReceiveTask: Jun 01 18:01:07.096: 08:11:96:5a:9b:0c apfPemAddUser2 (apf_policy.c:268) Changing state for mobile 08:11:96:5a:9b:0c on AP 5c:50:15:e6:63:90 from AAA Pending to Associated

14 REPLIES

Windows 7 w/Intel 6205n doesn't work with CCKM enabled on WLAN?

Raun:

it is obvious that it is a client issue:

*osapiBsnTimer: Jun 01 18:01:04.926: 08:11:96:5a:9b:0c 802.1x 'timeoutEvt' Timer expired for station 08:11:96:5a:9b:0c and for message = M2

*dot1xMsgTask: Jun 01 18:01:04.926: 08:11:96:5a:9b:0c Retransmit 1 of EAPOL-Key M1 (length 121) for mobile 08:11:96:5a:9b:0c

*osapiBsnTimer: Jun 01 18:01:05.926: 08:11:96:5a:9b:0c 802.1x 'timeoutEvt' Timer expired for station 08:11:96:5a:9b:0c and for message = M2

*dot1xMsgTask: Jun 01 18:01:05.926: 08:11:96:5a:9b:0c Retransmit 2 of EAPOL-Key M1 (length 121) for mobile 08:11:96:5a:9b:0c

*osapiBsnTimer: Jun 01 18:01:06.926: 08:11:96:5a:9b:0c 802.1x 'timeoutEvt' Timer expired for station 08:11:96:5a:9b:0c and for message = M2

After auth success sent from radius to the client the clients enters 4-way handshak phase where 4 messages are being sent.

message 1 is from the AP to the client.

mesasge 2 is from the client to the AP replying to message 1.

In the debugs above it shows that the client did not reply to message 1. so the AP waiting for the message 2 (which is a reply for message 1) but hte client does not send it at all. (M2 in the debug messages refers to message 2 in the handshake).

So I think that you need to double check your adapter, make sure it is compatible with CCKM and upgrade the driver if necessary.

If the problem persists it is wise to contact intel support if everyone else work fine with the WLAN except this type of clients/drivers.

BTW, I can see in your description that your security is 802.1x + CCKM. in this case clients connected will work with CCKM if they support it and those who do not support CCKM will work normally without CCKM support. So even if your device does not support CCKM it should probably work.
Do you have same problem when you choose only 802.1x as a security?

one more tip is to increase the advanced EAP timer on the WLC. maybe the timeout for messages in the handshake it small and the client is a bit slow to reply.

HTH

Amjad

Rating useful replies is more useful than saying "Thank you"
Hall of Fame Super Silver

Windows 7 w/Intel 6205n doesn't work with CCKM enabled on WLAN?

Raun,

Well I think you solved your own issue... you were able to connect with just using 802.1x. I have tried this too in the past and it caused issues with clients that do not support cckm.

-Scott
*** Please rate helpful posts ***
New Member

Re: Windows 7 w/Intel 6205n doesn't work with CCKM enabled on WL

So I think that you need to double check your adapter, make sure it is compatible with CCKM and upgrade the driver if necessary.

If  the problem persists it is wise to contact intel support if everyone  else work fine with the WLAN except this type of clients/drivers.

________________________________

BTW,  I can see in your description that your security is 802.1x + CCKM. in  this case clients connected will work with CCKM if they support it and  those who do not support CCKM will work normally without CCKM support.  So even if your device does not support CCKM it should probably work.
Do you have same problem when you choose only 802.1x as a security?

Exactly!! That's what's ticking me off about this.  The client certainly has options pertaining to CCKM (granted Intel drivers/tools are generic across the spectrum for all cards) but I would have thought the 6205 would be fine and why it cares one way or the other is weird.  As I mentioned, I tried the 14.x series drivers and now up to the 15.1.x drivers.  802.1x works fine.  But don't I lose a lot of functionality for fast roaming with out CCKM?

one  more tip is to increase the advanced EAP timer on the WLC. maybe the  timeout for messages in the handshake it small and the client is a bit  slow to reply.

I'll take a look at that, didn't think about it, thank you.   This is a test network so no other clients currently on it, but most of my clients are going to be the Intel 6205 card.  I'll have to wrangle up some other devices to see what happens. Has anyone used Windows 7 with CCKM?   I had found a post from someone on the net in regards to having this issue with Vista and a reply was that CCKM does not work with Vista?

Bronze

Re: Windows 7 w/Intel 6205n doesn't work with CCKM enabled on WL

Even without CCKM, yuu should still be able to do fast roaming with PKC. Check the following link:

http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a00808b4c61.shtml

"

PKC is enabled by default with WPA2. Therefore, when you enable WPA2 as Layer 2 security under the WLAN configuration of the WLC, PKC is enabled on the WLC.

"

About the EAP timeout values, TAC always suggest following configurations:

config advanced eap identity-request-timeout 120

config advanced eap identity-request-retries 20

config advanced eap request-timeout 120

config advanced eap request-retries 20

Zhenning

Windows 7 w/Intel 6205n doesn't work with CCKM enabled on WLAN?

Ruan:


Your client does support CCKM.

*apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c Processing RSN IE type 48, length 18 for mobile 08:11:96:5a:9b:0c

*apfMsConnTask_4: Jun 01 18:01:03.664: 08:11:96:5a:9b:0c CCKM: Mobile is using CCKM

and this is what the WLC offer for it when it connects because it tells WLC that it supports CCKM. Howeber, although it says it supports CCKM it does not seem to play well with it.

For your roaming question, if you do not have real-time applications on your laptops then the roaming should not be an issue. You can usually roam fine without disconneciton if you roam without CCKM.

CCKM is intended to roam faster and this is usually for time-sensitive applications like voice.

HTH

Amjad

Rating useful replies is more useful than saying "Thank you"
New Member

Windows 7 w/Intel 6205n doesn't work with CCKM enabled on WLAN?

For your roaming question, if you do not have real-time applications  on your laptops then the roaming should not be an issue. You can usually  roam fine without disconneciton if you roam without CCKM.

CCKM is intended to roam faster and this is usually for time-sensitive applications like voice.

_____________________________________________________________________________________________________

Or, a really poor client / server applications such as medical apps.  I'm going to try changing the EAP timers tomorrow and see what happens.  Thank you for your help, shall post back with results.

Windows 7 w/Intel 6205n doesn't work with CCKM enabled on WLAN?

I expereinced this same problem. I have a WLAN that is 802.1X + CCKM andmy GE carts wouldnt connect. Only till i removed the CCKM and only allowed 802.1X it worked.

Im surprised, Intel is having this issue. Isnt there a CCKM check box in the supplicant config ? I know in the many intel clients that I have configured there is ..

__________________________________________________________________________________________ "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin ___________________________________________________________
New Member

Re: Windows 7 w/Intel 6205n doesn't work with CCKM enabled on WL

Your correct George, there is.  The intel client is the most versatile client and my preferred.   Which makes me wonder why this is happening.  NOW, I was sitting here thinking and something I had forgot about as I didn't think it would make a difference is the fact my test ap is configured as FlexConnect, no special settings, just a FlexConnect instead of Local.  Why?  In the grand scheme of things a site will be FlexConnect only and need to support the same thing we use anywhere else so it's my default test environment.  I also need to try a few other clients tomorrow, including other intel 6205 clients to see what happens.

What card was in your GE carts?

Re: Windows 7 w/Intel 6205n doesn't work with CCKM enabled on WL

Hreap (Flex connect) requires HREAP groups for CCKM to work, as memory serves me right. I could be off base on that comment, so dont cash that check!

The GE devices were using older Slyx Bridges. But, I have run into this issue from time to time on one offs. We have over 6k+ devices, so we see most everything at some point.

__________________________________________________________________________________________ "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin ___________________________________________________________

Re: Windows 7 w/Intel 6205n doesn't work with CCKM enabled on WL

You know, cash that check - see below

H REAP Design and Functional Limitations

H REAP WAN Considerations

Because the H REAP has been designed specifically to operate across  WAN links, it has been optimized for such installations. Though H REAP  is flexible when it comes to these remote network design scenarios,  there are still a few guidelines that need to be honored when  architecting a network with H REAP functionality.

  • An H REAP access point can be deployed with either a static IP  address or a DHCP address. In the case of DHCP, a DHCP server must be  available locally and must be able to provide the IP address for the  access point at bootup.

  • H REAP supports up to four fragmented packets or a minimum 500-byte maximum transmission unit (MTU) WAN link.

  • Roundtrip latency must not exceed 300 milliseconds (ms) for data and  100 ms for voice and data between the access point and the controller,  and CAPWAP control packets must be prioritized over all other traffic.

  • The controller can send multicast packets in the form of unicast or  multicast packets to the access point. In H REAP mode, the access point  can receive multicast packets only in unicast form.

  • In order to use CCKM fast roaming with H REAP access points, you need to configure H REAP groups.

  • H REAP access points support multiple SSIDs.

  • NAC out-of-band integration is supported only on WLANs configured for  H REAP central switching. It is not supported for use on WLANs  configured for H REAP local switching.

__________________________________________________________________________________________ "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin ___________________________________________________________
New Member

Re: Windows 7 w/Intel 6205n doesn't work with CCKM enabled on WL

Well, it's a member of a group 'FlexTestGRP', but no special settings, just defaults.   Off of the WLC it's self there are options for local auth of course, but I don't have that setup and no options for CCKM anywhere in the group that I see.  Maybe I'll run in and kick it out of FlexConnect mode and try it real quick.

Re: Windows 7 w/Intel 6205n doesn't work with CCKM enabled on WL

What code are you on?

There has been some resent bugs with CCKM.  This was posted by one of the TAC guys resently.. These may not be your issue, but since we are on the subject of CCKM

There are several  bugs that can cause CCKM clients to be periodically  disconnected in WLC  7.0/7.2.  This tip explains the bugs, and how  different 7.0/7.2 builds  are vulnerable to them.

CSCtt70290 -  this bug causes a CCKM client to be disconnected if the session  timeout  occurs after the client has roamed.  Workaround: disable the   session-timeout on the WLAN.  This bug affects 7.0.98.0 through   7.0.220.0.

Unfortunately, the "fix" for the CSCtt70290 problem, which was committed in 7.0.230.0 and 7.2.103.0, caused:

CSCty07036  - this bug causes a CCKM client to be disconnected if the group key   (broadcast key) rotation occurs after the client is roamed.  Partial   workaround: increase the broadcast key rotation timer to its maximum   (one day.)

The real fix for both of these problems is  being  addressed via CSCty07036, which fix will be in the 7.2 "MR1"  release  (i.e. the next 7.2 CCO release after 7.0.103.0), and in the 7.0  "MR4"  release (i.e. the next 7.0 CCO release after 7.0.235.0.)  These   releases will be available on CCO in CY2012.

Because  the group  key rotation problem is considered to be more severe than the  session  timeout, for the 7.0.235.0 "MR3.5" release, the CSCtt70290 bad  codefix  was backed out via CSCtz19309.   Consequently, the 7.0.235.0 behavior  reverts to the pre-7.0.230.0  behavior, i.e. group key rotatation works,  but session timeout causes  client disconnects.

This table  shows, for the various  releases in 7.0/7.2, whether broadcast key  rotation or session timeout  is broken for CCKM clients:

Release    Group Key Rotation

Session Timeout

7.0.98.0 - 7.0.220.0    Working    Broken

7.0.230.0    Broken    Working

7.0.235.0    Working    Broken

7.2.130.0    Broken    Working

7.2 MR1    Working    Working

7.0 MR4    Working    Working

__________________________________________________________________________________________ "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin ___________________________________________________________
New Member

Re: Windows 7 w/Intel 6205n doesn't work with CCKM enabled on WL

Well crap.   There's a hitch no matter where you turn isn't there?  I'm testing on 7.2.130 right now, other WLC's are on 7.0.98.0, but we have to goto 7.2 because I'm replacing about a 100 AP's with 3602's this summer.  grr.

Is this from the bug kit?

New Member

Windows 7 w/Intel 6205n doesn't work with CCKM enabled on WLAN?

Raun,

How were you able to select the CCKM options with the Intel ProSet Wireless utility on Windows 7?  I have a 32-bit system, Win7 and when I install the latest drivers with the utility I only get options WiFi Advanced Statistics, WiFi Event Viewer, WiFi Manual Diagnostics, and Import a Profile from the Utility interface screen.

1978
Views
0
Helpful
14
Replies