We've been doing similar kinds of testing so I hope this helps. We use 802.1X/WEP but we didn't want different SSIDs for n and for a/b/g so we created a new WLAN for n with a different profile name but the same SSID as for a/b/g. In limited testing so far this seems to work fine. All clients see the same SSID, but users who can do n will get to do n on the new WLAN, and all the old clients who can't do n will still get to do WEP without any client configuration changes.
-----Original Message----- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:[EMAIL PROTECTED] On Behalf Of Hector J Rios Sent: Wednesday, June 18, 2008 1:06 PM To: [email protected] Subject: [WIRELESS-LAN] 802.11n and WPA/WPA2... So, we've been testing 802.11n with a couple of Cisco 1250 radios. In order to support it on our 802.1X/WPA/TKIP WLAN, we had to add WPA2 to our layer 2 security parameters. So now we support either WPA or WPA2. We are finding out that some systems don't like this. Specifically, Windows Vista and Windows Mobile 5.0. We have tested this with controllers running 4.2.130 and 4.2.61 and we get the same issue. Since we don't want to broadcast another SSID, we decided to turn off WPA2 for right now. Is anybody else experiencing this? If so, did you opt for broadcasting a separate SSID with WPA2 only, and still keep your WPA SSID? Or did you just decide to support WPA2 only? How about those using Aruba, Trapeze, etc. are you having a similar issue with the combination of WPA/WPA2 in the same WLAN? Thanks, Hector Rios Louisiana State University ********** 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/.
