Funny that you mention the issues with the HTC… I have spent the last two days trying to figure out why some Droid phones/tablets can get a DHCP address and others cannot. Moreover, if they do get an IP address, some lose their IP address after 10 - 15 minutes and cannot renew it. Because each device is using its own flavor of Android OS, I haven't been able to determine the common denominator. According to the WCS and debugs on WLCs, the devices are not requesting a DHCP address. (see debug below) . The workaround is to give the device a static IP address, have it connect to the network, and then uncheck the static IP box. Is this similar to what you are seeing? I have a case open with Cisco but they are not interested in figuring out the problem because "the problem is with the client. " However, according to the users, these clients work fine at home, in Starbucks, etc. So, to me, it is a client to WLC issue not just a client issue.
> *osapiBsnTimer: Oct 26 16:07:37.114: 00:26:ba:55:4d:55 apfMsExpireCallback > (apf_ms.c:608) Expiring Mobile! > *apfReceiveTask: Oct 26 16:07:37.114: 00:26:ba:55:4d:55 > apfMsExpireMobileStation (apf_ms.c:5009) Changing state for mobile > 00:26:ba:55:4d:55 on AP 00:1d:70:99:fa:40 from Associated to Disassociated > > *apfReceiveTask: Oct 26 16:07:37.114: 00:26:ba:55:4d:55 Scheduling deletion > of Mobile Station: (callerId: 45) in 10 seconds > *apfMsConnTask_0: Oct 26 16:07:39.349: 00:26:ba:55:4d:55 Association received > from mobile on AP 00:1d:70:99:fa:40 > *apfMsConnTask_0: Oct 26 16:07:39.349: 00:26:ba:55:4d:55 0.0.0.0 DHCP_REQD > (7) Changing ACL 'none' (ACL ID 255) ===> 'none' (ACL ID 255) --- (caller > apf_policy.c:1621) > *apfMsConnTask_0: Oct 26 16:07:39.349: 00:26:ba:55:4d:55 Applying > site-specific IPv6 override for station 00:26:ba:55:4d:55 - vapId 1, site > 'default-group', interface 'vlan144' > *apfMsConnTask_0: Oct 26 16:07:39.349: 00:26:ba:55:4d:55 Applying IPv6 > Interface Policy for station 00:26:ba:55:4d:55 - vlan 144, interface id 8, > interface 'vlan144' > *apfMsConnTask_0: Oct 26 16:07:39.349: 00:26:ba:55:4d:55 STA - rates (8): 18 > 150 24 36 48 72 96 108 12 0 0 0 0 0 0 0 > *apfMsConnTask_0: Oct 26 16:07:39.349: 00:26:ba:55:4d:55 STA - rates (9): 18 > 150 24 36 48 72 96 108 12 0 0 0 0 0 0 0 > *apfMsConnTask_0: Oct 26 16:07:39.349: 00:26:ba:55:4d:55 apfMs1xStateDec > *apfMsConnTask_0: Oct 26 16:07:39.349: 00:26:ba:55:4d:55 0.0.0.0 DHCP_REQD > (7) Change state to START (0) last state DHCP_REQD (7) > > *apfMsConnTask_0: Oct 26 16:07:39.349: 00:26:ba:55:4d:55 0.0.0.0 START (0) > Initializing policy > *apfMsConnTask_0: Oct 26 16:07:39.349: 00:26:ba:55:4d:55 0.0.0.0 START (0) > Change state to AUTHCHECK (2) last state DHCP_REQD (7) > > *apfMsConnTask_0: Oct 26 16:07:39.349: 00:26:ba:55:4d:55 0.0.0.0 AUTHCHECK > (2) Change state to L2AUTHCOMPLETE (4) last state DHCP_REQD (7) > > *apfMsConnTask_0: Oct 26 16:07:39.349: 00:26:ba:55:4d:55 0.0.0.0 > L2AUTHCOMPLETE (4) DHCP Not required on AP 00:1d:70:99:fa:40 vapId 1 apVapId > 1for this client > *apfMsConnTask_0: Oct 26 16:07:39.350: 00:26:ba:55:4d:55 Not Using WMM > Compliance code qosCap 00 > *apfMsConnTask_0: Oct 26 16:07:39.350: 00:26:ba:55:4d:55 0.0.0.0 > L2AUTHCOMPLETE (4) Plumbed mobile LWAPP rule on AP 00:1d:70:99:fa:40 vapId 1 > apVapId 1 > *apfMsConnTask_0: Oct 26 16:07:39.350: 00:26:ba:55:4d:55 0.0.0.0 > L2AUTHCOMPLETE (4) Change state to DHCP_REQD (7) last state DHCP_REQD (7) > > *apfMsConnTask_0: Oct 26 16:07:39.350: 00:26:ba:55:4d:55 0.0.0.0 DHCP_REQD > (7) pemApfAddMobileStation2 2744, Adding TMP rule > *apfMsConnTask_0: Oct 26 08:43:55.350: 00:26:ba:55:4d:55 0.0.0.0 DHCP_REQD > (7) Adding Fast Path rule > type = Airespace AP - Learn IP address > on AP 00:1d:70:99:fa:40, slot 0, interface = 29, QOS = 1 > ACL Id = 255, Jumbo F > *apfMsConnTask_0: Oct 26 16:07:39.350: 00:26:ba:55:4d:55 0.0.0.0 DHCP_REQD > (7) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 5006 IPv6 Vlan > = 144, IPv6 intf id = 8 > *apfMsConnTask_0: Oct 26 16:07:39.350: 00:26:ba:55:4d:55 0.0.0.0 DHCP_REQD > (7) Successfully plumbed mobile rule (ACL ID 255) > *apfMsConnTask_0: Oct 26 16:07:39.350: 00:26:ba:55:4d:55 0.0.0.0 DHCP_REQD > (7) pemApfAddMobileStation2 2871, Adding TMP rule > *apfMsConnTask_0: Oct 26 16:07:39.022: 00:26:ba:55:4d:55 0.0.0.0 DHCP_REQD > (7) Replacing Fast Path rule > type = Airespace AP - Learn IP address > on AP 00:1d:70:99:fa:40, slot 0, interface = 29, QOS = 1 > ACL Id = 255, Jumb > *apfMsConnTask_0: Oct 26 16:07:39.350: 00:26:ba:55:4d:55 0.0.0.0 DHCP_REQD > (7) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 5006 IPv6 Vlan > = 144, IPv6 intf id = 8 > *apfMsConnTask_0: Oct 26 16:07:39.350: 00:26:ba:55:4d:55 0.0.0.0 DHCP_REQD > (7) Successfully plumbed mobile rule (ACL ID 255) > *apfMsConnTask_0: Oct 26 16:07:39.350: 00:26:ba:55:4d:55 apfMsAssoStateInc > *apfMsConnTask_0: Oct 26 16:07:39.350: 00:26:ba:55:4d:55 apfPemAddUser2 > (apf_policy.c:223) Changing state for mobile 00:26:ba:55:4d:55 on AP > 00:1d:70:99:fa:40 from Disassociated to Associated > > *apfMsConnTask_0: Oct 26 16:07:39.350: 00:26:ba:55:4d:55 Stopping deletion of > Mobile Station: (callerId: 48) > *apfMsConnTask_0: Oct 26 16:07:39.350: 00:26:ba:55:4d:55 Sending Assoc > Response to station on BSSID 00:1d:70:99:fa:40 (status 0) ApVapId 1 Slot 0 > *apfMsConnTask_0: Oct 26 16:07:39.350: 00:26:ba:55:4d:55 apfProcessAssocReq > (apf_80211.c:5241) Changing state for mobile 00:26:ba:55:4d:55 on AP > 00:1d:70:99:fa:40 from Associated to Associated > > *pemReceiveTask: Oct 26 16:07:39.357: 00:26:ba:55:4d:55 0.0.0.0 Removed NPU > entry. > *pemReceiveTask: Oct 26 16:07:39.363: 00:26:ba:55:4d:55 0.0.0.0 Added NPU > entry of type 9, dtlFlags 0x0 > *pemReceiveTask: Oct 26 16:07:39.369: 00:26:ba:55:4d:55 0.0.0.0 Added NPU > entry of type 9, dtlFlags 0x0 > *apfReceiveTask: Oct 26 16:09:39.333: 00:26:ba:55:4d:55 0.0.0.0 DHCP_REQD (7) > DHCP Policy timeout. Number of DHCP request 0 from client > *apfReceiveTask: Oct 26 16:09:39.333: 00:26:ba:55:4d:55 0.0.0.0 DHCP_REQD (7) > Pem timed out, Try to delete client in 10 secs. > *apfReceiveTask: Oct 26 16:09:39.333: 00:26:ba:55:4d:55 Scheduling deletion > of Mobile Station: (callerId: 12) in 10 seconds > *osapiBsnTimer: Oct 26 16:09:49.333: 00:26:ba:55:4d:55 apfMsExpireCallback > (apf_ms.c:608) Expiring Mobile! > *apfReceiveTask: Oct 26 16:09:49.333: 00:26:ba:55:4d:55 > apfMsExpireMobileStation (apf_ms.c:5009) Changing state for mobile > 00:26:ba:55:4d:55 on AP 00:1d:70:99:fa:40 from Associated to Disassociated > > *apfReceiveTask: Oct 26 16:09:49.333: 00:26:ba:55:4d:55 Scheduling deletion > of Mobile Station: (callerId: 45) in 10 seconds > *osapiBsnTimer: Oct 26 16:09:59.334: 00:26:ba:55:4d:55 apfMsExpireCallback > (apf_ms.c:608) Expiring Mobile! > *apfReceiveTask: Oct 26 16:09:59.336: 00:26:ba:55:4d:55 Sent Deauthenticate > to mobile on BSSID 00:1d:70:99:fa:40 slot 0(caller apf_ms.c:5094) > *apfReceiveTask: Oct 26 16:09:59.336: 00:26:ba:55:4d:55 apfMsAssoStateDec > *apfReceiveTask: Oct 26 16:09:59.336: 00:26:ba:55:4d:55 > apfMsExpireMobileStation (apf_ms.c:5132) Changing state for mobile > 00:26:ba:55:4d:55 on AP 00:1d:70:99:fa:40 from Disassociated to Idle > > *apfReceiveTask: Oct 26 16:09:59.336: 00:26:ba:55:4d:55 0.0.0.0 DHCP_REQD (7) > Deleted mobile LWAPP rule on AP [00:1d:70:99:fa:40] > *apfReceiveTask: Oct 26 16:09:59.336: 00:26:ba:55:4d:55 Deleting mobile on AP > 00:1d:70:99:fa:40(0) > *pemReceiveTask: Oct 26 16:09:59.341: 00:26:ba:55:4d:55 0.0.0.0 Removed NPU > entry. >> >> From: The EDUCAUSE Wireless Issues Constituent Group Listserv = >> =5Bmailto:WIRELESS-LAN=40LISTSERV.EDUCAUSE.EDU=5D On Behalf Of Marcelo Lew >> Sent: Thursday, October 27, 2011 6:08 PM >> To: WIRELESS-LAN=40LISTSERV.EDUCAUSE.EDU >> Subject: =5BWIRELESS-LAN=5D Android 2.3.4 wifi connectivity issue >> >> I worked on an issue with an HTC running Android 2.3.4 and was wondering = >> if you guys seen something similar. Seems this version adds a =93WiFi = >> Proxy=94 setting that I have not seen in previous versions. It was = >> causing the device to stick to an old IP even after enabling / disabling = >> this setting, restarting the phone, flushing user from controller, etc. = >> It also did not matter if it was an open or secured ssid. After some = >> tweaking it is working, but still a bit buggy. >> Thanks, >> >> Marcelo >> >> Marcelo Lew >> Wireless Enterprise Administrator >> University Technology Services >> University of Denver >> Desk: (303) 871-6523 >> Cell: (303) 669-4217 >> Fax: (303) 871-5900 >> Email: mlew=40du.edu<mailto:mlew=40du.edu> >> >> >> =2E ********** Participation and subscription information for this = >> EDUCAUSE Constituent Group discussion list can be found at = >> http://www.educause.edu/groups/. >> ********** Participation and subscription information for this EDUCAUSE = >> Constituent Group discussion list can be found at = >> http://www.educause.edu/groups/. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> =2E= >> >> ********** >> Participation and subscription information for this EDUCAUSE Constituent >> Group discussion list can be found at http://www.educause.edu/groups/. >> >> ------------------------------ >> >> End of WIRELESS-LAN Digest - 26 Oct 2011 to 27 Oct 2011 (#2011-179) >> ******************************************************************* Regards, Christina Klam Network Administrator Institute for Advanced Study Email: [email protected] Einstein Drive Telephone: 609-734-8154 Princeton, NJ 08540 Fax: 609-951-4418 ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
