Hello! > I think the better solution is .... to learn/understand how it works ! > Anyway thanks for your answer !
The answer why there are so many "requests" is that during an EAP session, lots of data has to be exchanged, not just some small attributes that fit into a single RADIUS packet. The important content is sent in an attribute named EAP-Message, which is of limited length. So, if more data has to be exchanged, the message is split in chunks and a lengthy EAP "conversation" takes place. This has to be done for example when it comes to exchanging server or client certificates as these tend to be long. In that case, one party sends the first chunk of data and the other replies with a "go ahead" until one side is finished. Since the RADIUS protocol only has the two message types "Request" and "Reply", one of the two sides of the conversation has to be labelled a Request and the other the Reply. As Alan said, do not confuse that Request message with an all-new "Request from a user to authenticate". So, don't worry, everything will be okay. Stefan Winter -- Stefan WINTER Fondation RESTENA - R�seau T�l�informatique de l'Education Nationale et de la Recherche Ing�nieur r�seau et syst�me 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg email: [EMAIL PROTECTED] � � t�l.: � � �+352 424409-33 http://www.restena.lu � � � � � � � � � � fax: � � �+352 422473 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
