Thanks! We upgraded to 5.0.3.1 over the weekend. It solved our "memory leak" problem. There was also a "catch all" acl in validuser for udp 68 that once removed our Androids worked.
However, we have had a few mac users complain about poor connection. I'm going to give this a try. -----Original Message----- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[email protected]] On Behalf Of Osborne, Bruce W Sent: Wednesday, March 23, 2011 8:02 AM To: [email protected] Subject: Re: [WIRELESS-LAN] Android 2.2 disappointing on the secure WLAN- is it just us? Sorry to resurrect an old thread, but there was no clear solution at the time. Since then, I have been working with setting up 802.1X WPA2-Enterprise in our Aruba wireless environment. I believe that I have found a reasonable solution. By default, Aruba enables Opportunistic Key Caching (OKC) that enables a cached pairwise master key (PMK) to be used when roaming to a new AP, enabling faster roaming. In Aruba systems, if opp-key-caching is enabled, validate-pmkid (disabled by default) tells the controller to check the PMK ID sent by the client. The client must send the PMKID to indicate that it supports PKC. Otherwise, a full 802.1X authentication takes place. I was personally seeing similar issues to those discussed in this thread. After I enabled the validate-pmkid setting, the issues vanished. This change should have no impact on clients that properly use OKC. People with other vendor's systems likely have similar configuration options. Bruce Osborne Wireless Network Engineer IT Network Services (434) 592-4229 LIBERTY UNIVERSITY 40 Years of Training Champions for Christ: 1971-2011 -----Original Message----- From: Daniel Bidwell [mailto:[email protected]] Sent: Wednesday, September 29, 2010 2:00 PM Subject: Re: Android 2.2 disappointing on the secure WLAN- is it just us? On Wed, 2010-09-29 at 13:55 -0400, Lee H Badman wrote: > We have three cases of Droid smartphones that worked wonderfully on > our 802.1x/WPA2 WLAN on Android 2.1 operating system. Since going to > 2.2 with the devices, getting them to connect to the secure wireless > network is almost impossible. Open networks are OK. > > > > Anyone else seeing this? > We have the same there here. We can get the to connect for a short time (2-30 minutes) and then they drop the connection and mark it as disabled. I was hoping that 2.2.1 would fix it, but alas, no such luck. > > > -Lee Badman > > ********** Participation and subscription information for this > EDUCAUSE Constituent Group discussion list can be found at > http://www.educause.edu/groups/. > -- Daniel R. Bidwell | [email protected] Andrews University | Information Technology Services If two always agree, one of them is unnecessary "Friends don't let friends do DOS" "In theory, theory and practice are the same. In practice, however, they are not." ********** 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/. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
