Ivan, Alan,
We now have peap and ttls-pap working. It turns out you were both
right. What tricked us for a long period of time is that we had to
comment out unix because our testing server had the ldap users on it
for other testing purposes. The unix module was thwarting the ldap
module for ttls-pap. If this had not been the case, we probably
would have had ttls - pap working as fast as peap. In our live
environment, we don't have end users on the same server so this
normally wouldn't have been an issue. Commenting out unix allowed
ttls-pap to work properly.
Thanks!
Tim
At 12:56 PM 6/11/2008, Ivan Kalik wrote:
> We just installed freeradius 2.05 on a Centos 5 system. We got
>PEAP working rather quickly against our ldap server against LM/NT
>passwords. We would also like to allow clients using Securew2
>supplicants configured for TTLS -PAP connections against (crypt and
>SSHA) passwords stored in our ldap database.
You have done it. If PEAP works, so will EAP-TTLS/PAP.
Ivan Kalik
Kalik Informatika ISP
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Tim Tyler
Network Engineer - Beloit College
[EMAIL PROTECTED]
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
