On Oct 30, 2007, at 10:08, debbie fligor wrote:
On Oct 30, 2007, at 6:48, Matt Ashfield wrote:
Hello:
I’m just wondering if anyone else is seeing problems with the new
mac OS Leopard and having users connect to the wireless network
via 802.1x? There is a patch out for this:
http://docs.info.apple.com/article.html?artnum=306804
However the patch is not fixing the problem according to our
users. Just wondering if anyone else is seeing this. Thanks
I couldn't get the latest development version to work with our
alpha-test of WPA2/802.1x last week when we finally thought to try
it. 10.4.10 is working just fine, so I don't think it's the
wireless side.
After checking with our Apple SE, I was waiting for the release
version to see what, if anything, got fixed and to bring it up via
channels now that it's released. I'm imaging our group's master
DVD right now, and hope to install and have more info later today.
I'm not all that hopeful from the limited info in the update you
posted that it would help. I'll let you know what I find out.
A pleasant surprise, it worked just fine. It was somewhat alarming to
watch the connection process but it turned out to be easier than
expected.
We tested two times, with a test SSID just in my office that is
broadcast (which is how we'll run in production), and also with our
alpha test SSID that is non-broadcast. Both are TTLS/MSCHAPv2 and
also support PEAP. It appeared to choose TTLS both times.
For the broadcast SSID I chose the network out of the list while in
the Network Settings window, It popped up a dialog asking for my
username and password and for me to say what kind of 802.1X I was
using. I left that on "Automatic". It then tried to connect, and
kept flashing between "Authenticated via TTLS" and a message warning
me about self-assigned IP address (my testing with the last developer
version never made it to a real IP address, so this was alarming).
After it did that a few times, it stayed with "Status: Authenticated"
and just worked, indicating it was TTLS and showing the connect
time. Web browsing worked fine. I did have to accept the certificate
sometime during the process even though it's Thawte signed.
For the non-broadcast SSID I pulled down the menu in the Network
Settings window and picked "Join Other Network..."
I typed in the SSID and had to set the security (it defaulted to
"None"). I picked "WPA2 Enterprise" and got the same three boxes:
username, password, and an 802.1X pulldown -- which I left at
"Automatic". When I clicked "Join" after typing that in, it gave me
the same behavior with the IP address and Authenticated message, and
then settled down to "Status: Authenticated" and worked just fine.
I'm sure this is a YMMV thing depending on the authentication methods
used.
-----
-debbie
Debbie Fligor, n9dn Network Engineer, CITES, Univ. of Il
email: [EMAIL PROTECTED] <http://www.uiuc.edu/ph/www/fligor>
"My turn." -River
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
