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/.
