ok, thanks.<br><br>But if when hostap receive the first response identity, send it to radius server and wait for server response before receive the second response identity? This second response identity will also be sent to radius server? Sorry for this questions, I should search this myself on the state machine.<br>
<br>In fact, i don't have any EAPOL-Start. I have a wimax setup where wpa supplicant runs in background in the subscriber station, so when a SS try to connect to a BS, the BS send a request identity, starting the process.<br>
<br><div class="gmail_quote">On Tue, May 13, 2008 at 5:01 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 04:27:42PM -0300, Douglas Diniz wrote:<br>
<br>
> I'm asking because i have a setup where hostap receive a Start several times<br>
> while in Held State, so i'm afraid that when the quietPeriod goes to 0 the<br>
> following scenario occur:<br>
><br>
> 1-) Hostap goes from held state to restart state, sending a request identity<br>
> 2-) Just after that hostap receive a Start, re-sending a Request Identity<br>
> 3-) In this meanwhile wpa supplicant receive the first request identity and<br>
> send a response identity.<br>
> 4-) The second Request Identity is received by wpa supplicant, which abort<br>
> the authentication.<br>
><br>
> This could occur?<br>
<br>
</div>The steps 1 to 3 can happen and they do indeed happen quite frequently<br>
with many supplicant implementations and if you follow the EAPOL state<br>
machine definitions in 802.1X, both supplicant and authenticator are<br>
trying to initialize authentication at the same time whenever the port<br>
becomes enabled. wpa_supplicant is actually delaying the initial<br>
EAPOL-Start to avoid the extra frames since in case of wireless networks<br>
the AP/Authenticator will always know when a new supplicant appears and<br>
can start new authentication immediately without any need for<br>
EAPOL-Start.<br>
<br>
However, step 4 does not result in supplicant aborting the<br>
authentication. wpa_supplicant will reply to both identity requests and<br>
authenticator will use the second reply since that is for the last<br>
pending request. Authentication continues normally after that so the<br>
only "problem" is the two unnecessary frames due to the duplicated<br>
identity request.<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>