On Sep 29, 2010, at 12:55 PM, 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 are using EAP-TLS and have seen issues with both 2.1 and 2.2. In some cases phones that were connecting OK stopped connecting at all, other phones connected only sometimes so they couldn't connect reliably. Also sometimes when the phone connects it seems to take a lot longer than it should. One issue that is specific to EAP-TLS is that when you turn your phone off and back on the phone won't connect to the SSID with WPA2 until you re-enter your password to enable access to the certificate store. If other EAP types are set to verify the RADIUS server certificate that could also be an issue requiring re-entry of the password for the certificate store. It's not always obvious that the problem is lack of access to the certificate store, you don't always get an indication that that is the problem. Another thing we are trying is to use an App to more narrowly specify the options configured on the phone for our WPA2 SSID. For example only WPA2/RSN (not WPA), only WPA_EAP for key management (not IEEE802.1x), only CCMP (not TKIP or WEP) etc. We don't have enough data yet to say that this has helped a lot but the idea is to streamline the negotiation to enable faster connects and fewer timeouts during the connection setup process. > -Lee Badman > > > > > > ********** Participation and subscription information for this EDUCAUSE > Constituent Group discussion list can be found at > http://www.educause.edu/groups/. --- Bruce Curtis [email protected] Certified NetAnalyst II 701-231-8527 North Dakota State University
