I'm not sure about your immediate problem, but I do know that if and when you upgrade to the 5.0+ code on your controllers, the LWAPP 1000 series access points won't be supported at all. --------------- Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 5.0.148.0 Access Point Changes * Cisco Aironet 1000 Series Access Points - The 1000 series access points are not supported for use with controller software release 5.0.148.0 or later. --------------- We phased all of the 1000 series out and are currently on the 6 code with no problems.
Kevin Semrau Network Specialist Tel: (717) 871-5883 Fax: (717) 871-2048 -------------------------- Millersville University Boyer Computer Center 37 W. Frederick St. Millersville, PA 17551-1909 www.millersville.edu -----Original Message----- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Todd Gould Sent: Friday, August 14, 2009 12:37 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: [WIRELESS-LAN] 802.1x/LWAPP 1000 Series APs/OS X SSH This problem is an odd one. Below is essentially what I wrote in my Cisco TAC case. I intentionally kept the technical talk to a minimum, as to not confuse or overwhelm TAC. Has anyone encountered this? --brief overview of our wireless network-- We support wireless users that use any and all operating systems. From OS X, Ubuntu, Redhat, XP, Vista, you name it, we have to support it...it's politics. With that said, here is a description of our wireless network. We have (10) WLC4404 controllers. We have a Location Appliance 2700. These devices connect via Gig copper, to (2)2970 Cisco switches, LAG is enabled. These switches are then port channeled to our Cisco 6509 core. It works EXTREMELY WELL. We have just deployed a Cisco ACS box to enable us to use 802.1x with WPA rotating keys. This ACS checks user credentials against our AD environment, and places people into the appropriate wireless vlan. Works GREAT. So, with a little overview of how we are set up, here's the issue. ONLY Users that use Mac OS X's built-in SSH client cannot complete the login process, when trying to connect to any ssh server. They get a login prompt for their username, and then password. Their session freezes right after they hit return to submit their password. This happens only when using (802.1x,WPA2/PEAP/ACS)while connected to LWAPP 1000 series access point. If they initially connect or roam to a 1100 series, 1242, 1252, 1300 LWAPP access point it works fine. If Mac OS X users connect to anyone of our LWAPP access points via non-encrypted captive portal,and ssh to some server, it works fine. It's some odd connection between OS X build of ssh, LWAPP 1000 series APs and 802.1x via ACS. Using a different ssh client on OS X does remedy the issue, but why is this happening. Has anyone else seen this? Other OS's are not impacted, just OS X 4.xx & 5.xx. Help and insight is appreciated. ********** 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/.
