(RADIATOR) PEAP problems

Barry Ard barry.ard at ualberta.ca
Mon Sep 17 17:13:28 CDT 2007

Kawakubo, Ken wrote:
> Hi Barry,
> My memory is a bit fuzzy but I think
> "EAPTLS_PEAPVersion 0" under the main handler enabled us to support
> Ken Kawakubo
> -----Original Message-----
> From: owner-radiator at open.com.au [mailto:owner-radiator at open.com.au] On
> Behalf Of Barry Ard
> Sent: Monday, September 17, 2007 9:42 AM
> To: Radiator list
> Subject: (RADIATOR) PEAP problems
> Hello,
> We have a fairly new wireless environment using Cisco lightweight access
> points and multiple WISMs. We are of course using Radiator for radius 
> and support PEAP and EAP-TTLS EAP types. Things are going well except 
> when using PEAP the only clients that work are the Microsoft native PEAP
> clients and the linux wpa_supplicant. The Mac OSX PEAP and a Dell PEAP 
> clients fail. We have wire and air tcpdump captures and observe that 
> Radiator issues an ACCEPT-ACCEPT but fails during the subsequent key 
> exchange. We have played around with         EAPTLS_PEAPVersion and 
> EAPTLS_PEAPBrokenV1Label commands (which were necessary to get the linux
> wpa_supplicant to work) but to no avail.
> Does anyone have any similar experiences? Any pointers would be greatly 
> appreciated.
> Thanks,
> Barry Ard
Perfect. Thanks Ken. I was putting EAPTLS_PEAPVersion 0 in the inner 
handler. It works great now.


Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.

More information about the radiator mailing list