Right.... Thanks<br><br><div class="gmail_quote">On Tue, May 13, 2008 at 9:34 PM, Jouni Malinen <<a href="mailto:j@w1.fi">j@w1.fi</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Tue, May 13, 2008 at 05:20:06PM -0300, Douglas Diniz wrote:<br>
<br>
> But if when hostap receive the first response identity, send it to radius<br>
> server and wait for server response before receive the second response<br>
> identity? This second response identity will also be sent to radius server?<br>
> Sorry for this questions, I should search this myself on the state machine.<br>
<br>
</div>Authenticator (hostapd) is waiting for a single EAP Identifier in a<br>
response (the one that matches the Identifier used in the last<br>
transmitted EAP Request). If the sequence here would indeed make hostapd<br>
wait for the response from the authentication server before receiving<br>
the second response identity, the challenge received from the<br>
authentication server would have already been sent out to the supplicant<br>
when the second identity response is received. Consequently, the second<br>
identity response would not have a match EAP Identifier and it would be<br>
dropped, i.e., it would not be sent to the authentication server.<br>
<font color="#888888"><br>
--<br>
</font><div><div></div><div class="Wj3C7c">Jouni Malinen PGP id EFC895FA<br>
_______________________________________________<br>
HostAP mailing list<br>
<a href="mailto:HostAP@lists.shmoo.com">HostAP@lists.shmoo.com</a><br>
<a href="http://lists.shmoo.com/mailman/listinfo/hostap" target="_blank">http://lists.shmoo.com/mailman/listinfo/hostap</a><br>
</div></div></blockquote></div><br>