Hi Joy,
We are in the process of testing support for MSCHAPv2 on our wireless
network. (We have been supporting only TTLS/PAP up to now.)
I have a radiator/ntlm configuration that works with MSCHAPv2 and
Windows7 and Windows Vista machines. We cannot get it to work with Mac
OS 10.6 or
12 WiSMs running 7.0.98 for the past 8 months.
1 5508 running 7.0.116.0 for over a year.
All stable.
Hector Rios
Louisiana State University
From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU] On Behalf Of Jamie Savage
Sent:
Are you using Aruba's defaults for the dot1x authentication profile? Their
defaults are not very good. Here is an example I received from Washington
Lee University.
!
aaa authentication dot1x Example
timer idrequest_period 10
max-requests 2
timer wpa-key-period 2000
timer
Does anyone who has gone down the ATT We'll be your WiFi service in your
stadium! road feel like entertaining questions off list?
Thanks-
Lee Badman
Lee H. Badman
Wireless/Network Engineer
Information Technology and Services
Adjunct Instructor, iSchool
Syracuse University
315 443-3003
There were several issues with Macs not getting an IP Address on a 802.1x
(MSCHAPv2) SSID a while back. Tweaking with the Aruba dot1x profile worked for
us. There is a pretty good thread about Mac WLAN issues (and this one in
particular) in the Aruba Airheads site (link below):