By checking the radius log, I found this: rad_check_password: Found Auth-Type EAP auth: type "EAP" Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 7 rlm_eap: Request found, released from the list rlm_eap: EAP/mschapv2 rlm_eap: processing type mschapv2 ERROR: Unknown value specified for Auth-Type. Cannot perform requested action. rlm_eap: Freeing handler modcall[authenticate]: module "eap" returns reject for request 7 modcall: group authenticate returns reject for request 7 auth: Failed to validate the user. Bin Chen wrote:
Hi,
I want to deploy the EAP-PEAP in our WLAN hotspot, we are using EAP-TLS before and it works fine with our AP. But a PKI is very inconvenient so we want to migrate to EAP-PEAP.
Any changes need to be done to radiusd.conf? The client will provide the user-name and password, the file 'users' will used to match the user-name and password? And is it enough? I mean, in EAP-TLS it also need user-name and password, just left the same as EAP-TLS?
And, I also want to know when the AP or Windows client encounter obstacle to cooperate with this change, which client should I use to verify in freeradius side the configuration is work but not the windows client's problem? Can radclient be used and how can I do?
I am newbie to this area and may be silly question, any help appreciated.
Thanks in advance. Bin Chen