Welcome to the MacNN Forums.

sinebubble · Apr 30, 2004, 12:00 AM

Anyone successfully using LEAP with airport? I have the latest airport drivers (3.4.1) using the latest 10.3.3. I'm trying to connect to a LEAP network and it's not working. Supposedly airport (this is not the extreme card, btw) does support LEAP.

Applefreak01 · Apr 30, 2004, 12:20 AM

Were you able to connect to the LEAP network with older Airport software versions and now it doesn't work under 3.4.1 or haven't you tried to connect to a LEAP network until you installed 3.4.1?

sinebubble · Apr 30, 2004, 12:34 AM

Originally posted by Applefreak01:
Were you able to connect to the LEAP network with older Airport software versions and now it doesn't work under 3.4.1 or haven't you tried to connect to a LEAP network until you installed 3.4.1?

This is my first attempt to connect to a LEAP network.

Applefreak01 · Apr 30, 2004, 01:04 AM

It might be the Airport 3.4.1 update. The 3.4 update caused a lot of problems for users and maybe this didn't get fixed in 3.4.1. Your right though it should work with the 802.11b airport card.

I really can't help more with this because I haven't tried to connect to a LEAP network. Just thought I would ask if you were able to connect before or not so that someone else might be able to help. I wish I could help you more.

Switched2Mac · May 2, 2004, 02:46 AM

Originally posted by sinebubble:
Anyone successfully using LEAP with airport? I have the latest airport drivers (3.4.1) using the latest 10.3.3. I'm trying to connect to a LEAP network and it's not working. Supposedly airport (this is not the extreme card, btw) does support LEAP.

LEAP is a Cisco proprietary authentication mechanism.

You must have an account to authenticate against as well.

http://www.itc.virginia.edu/desktop/...port.html#LEAP

kampl · May 4, 2004, 06:50 PM

I have yet to have a problem with LEAP authentication on Mac OS X since its (LEAP compatiblity) introduction. All patches are installed and it works without a hitch. The only thing that does not seem to work is storing credentials for LEAP in Keychain so that you do not have to supply them everytime you encounter the LEAP network.

Not that I would not recommend moving off of LEAP due to its vulnerability.

And of course THC has some code to crack it as well.

Perhaps I'm missing your point in so far as the question though.

sinebubble · May 5, 2004, 02:33 AM

Originally posted by kampl:
Perhaps I'm missing your point in so far as the question though. [/B]

Well, the point is actually pretty simple. My employer, a large wireless communications company, uses LEAP for its internal 8011b network. I'm an engineer and I use my Mac at work. Sometimes it is convenient to use the wireless network for meetings, etc. I have an account to access the network and the help desk guys tell me that they do not see me trying to access the LEAP network (and I have to believe them cos they aren't nearby for me to look over their shoulders). They claim to have done no special configuration for the wireless network. So, the implication is that I am either configuring my card incorrectly or my card cannot connect to the network. I have used Kismac to verify that the signal exists.

My next task is to dig up a 350 and stick it in my Mac and try to reach the network using Cisco's hardware/software.

kampl · May 6, 2004, 04:37 PM

Then I guess I answered you. There is nothing special to be done other than to specify LEAP authentication and supply credentials. I don't recall having to make any kind of config change on the Aironet in order to cater to Mac OS clients.

Were you able to find an Aironet card to try with the network instead?