Jens Riecken <[EMAIL PROTECTED]> wrote: > modcall: entering group authenticate for request 1 > rlm_eap: EAP packet type notification id 1 length 42 > rlm_eap: EAP Start not found > rlm_eap: Request found, released from the list > rlm_eap: EAP_TYPE - leap > rlm_eap: processing type leap > rlm_eap_leap: Stage 4 > rlm_eap_leap: NtChallengeResponse from AP is valid > rlm_eap: Underlying EAP-Type set EAP ID to 2 > rlm_eap: Saving LEAP state > modcall[authenticate]: module "eap" returns ok for request 1
That looks OK so far. ... > Sending Access-Challenge of id 1 to 10.0.1.1:2075 > EAP-Message = 0x03020004 That should be OK. The server is saying "please continue with LEAP". > rad_recv: Access-Request packet from host 10.0.1.1:2075, id=3, length=208 > Message-Authenticator = 0x3e4f369f3e6f08679f4f0792f6da8120 ... > EAP-Message = 0x0203000f016d79757365726e616d65 ... > modcall: entering group authenticate for request 2 > rlm_eap: EAP packet type notification id 3 length 15 > rlm_eap: EAP Start not found > rlm_eap: EAP Identity > rlm_eap: processing type leap > rlm_eap_leap: Stage 2 And the client is re-starting EAP. That isn't good. Are you sure this is a debug trace with only *one* client trying to authenticate? Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
