Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

[radius auth] non-cisco cards

hi,

is it posible to implement simple user/pass radius authentication between a cisco 352 and a non-cisco pcmcia card (say a lucent card)?

i just want this thing to use 802.1x-based eap authentication, but i have several non-cisco wireless cards. i read somewhere a long time ago that leap is cisco-proprietary, so...

i think i can use eap-tls, but i don't wanna deal with certificates.

anyone out there know a viable solution to my problem?

regards,

c.

4 REPLIES
Anonymous
N/A

Re: [radius auth] non-cisco cards

Cisco supports numerous EAP types on the Access Point. For the client, you might see if Funk Software (http://www.funk.com/) or Meeting House software (http://www.mtghouse.com/) have a shim for the lucent client for LEAP or other EAP types. I believe they do, but not certain if they support the Lucent client.

Community Member

Re: [radius auth] non-cisco cards

It can also depend on what OS you are running. We are authenticating XP users with PEAP to our IAS servers. We are simply using their UN/PW that is in Active Directory.

If you have XP machines then you wont need the clients above. I believe you need SP1 on them since that is when the client was added.

All said, it is a pretty easy thing to setup.

Don Hickey

Community Member

Re: [radius auth] non-cisco cards

yeah, actually i think i got working, because i get authenticated, but...

dhcp is not passing through the ap. i read in the discussion forums that this is because 3rd party and xp supplicant is not supported in csacs3.1. it has to be 3.2.

anyone know this for a fact?

regards,

c.

Community Member

Re: [radius auth] non-cisco cards

That is true....

From:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_soft/csacs4nt/acs32/rnwin321.htm#1009618

PEAP support for Microsoft Windows clients—Cisco Secure ACS 3.2 adds support for Microsoft PEAP supplicants available today for Windows 98, NT, 2000, and XP. The Microsoft PEAP supplicant supports client authentication by only MS-CHAPv2 compared to Cisco PEAP supplicant (available through Cisco Aironet wireless adapters) which supports client authentication by logon passwords or one-time passwords (OTPs). Unlike Microsoft PEAP supplicant, Cisco PEAP supplicant provides support for one-time token authentication and powerful extensibility of non-MSCHAP end-user databases such as LDAP, NDS, and ODBC. Cisco Secure ACS 3.2 will allow selection of Microsoft PEAP and/or Cisco PEAP from its EAP Configuration page. PEAP is an Internet draft standard in the IETF PPP working group.

Don

147
Views
0
Helpful
4
Replies
CreatePlease to create content