<div>Dear Jouni,</div><div>I have also tried with wpa_supplicant-0.8-snapshot.tar.I have seen the same issue.Wrong EAP profile is getting connected using PMKSA caching by skipping EAP authentication.</div><div> </div><div>
>There has been some<br>>recent changes in the PMKSA caching implementation that forces the<br>>cached credentials to be cleared in various cases.</div><div> </div><div>Where can I get these changes done to PMKSA caching implementation.</div>
<div> </div><div>Thanks for your effort,</div><div>Raga Naresh.<br></div><div class="gmail_quote">On Mon, Jan 23, 2012 at 8:18 PM, raga naresh <span dir="ltr"><<a href="mailto:raganaresh.thatha@gmail.com">raganaresh.thatha@gmail.com</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote"><div class="im"><div>>Which version of wpa_supplicant are you using? There has been some<br>
>recent changes in the PMKSA caching implementation that forces the<br>>cached credentials to be cleared in various cases. Without those, this<br>
>type of connection is quite possible using PMKSA caching that does<br>>indeed skip the EAP authentication.</div><div> </div></div><div>Hi Jouni Malinen,</div><div>I am using the latest stable release wpa_supplicant-0.7.3. Is there any patch for the recent changes or should I use any other version?</div>
<div> </div><div>Thanks for the reply,</div><div>Raga Naresh.</div><font color="#888888"><div> </div>
</font></blockquote></div><br>