hi > I am not sure, but I thing that is a problem with the EAP Id field in > the EAP-Success frame. Here you have a resume of the conversation > writing into parenthesis the eap id. > > NAS RADIUS > --> RAD-Req/EAP-Resp(id=1) --------> > <-- RAD-Chall/EAP-Req (id=c1) <---- > --> RAD-Req/EAP-Resp (id=c1) ------> > <-- RAD-Acept/EAP-Success (id=c2)--> > > I have checked with other radius rervers and the conversation is as > follows. > > NAS RADIUS > --> RAD-Req/EAP-Resp(id=1) --------> > <-- RAD-Chall/EAP-Req (id=c1) <---- > --> RAD-Req/EAP-Resp (id=c1) ------> > <-- RAD-Acept/EAP-Success (id=c1)-->
i know what you want to say, i.e. i see these c1 and c2 differencies, but where have you got it from? what is this c1, c2 stuff anyway? just two different variables? can you point out exactly these differencies in the server log or is it impossible to see? can you see it when sniffing the traffic between server and client? > PS. I don't know if it is necessary, but here there is a copy of > ./radiusd -X log. Regards. server-log looks very good and if i understand what you are saying, we could even conclude that the radius part works out great, right? the NAS opens the port on the receive of the RADIUS Access-Accept packet. so, you say the included EAP message is kind of wrong. can you see the logs of your AP or sniff the traffic between the supplicant and the client? ciao artur -- Artur Hecker artur[at]hecker.info - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
