my goal is to simulate the roaming environment. So I'm just changing the ssid name and not turning off the power.<br><br>But I guess as you pointed out, even the change of ssid may be flushing the pmksa cache.<br><br>Any better ideas to simulate roaming?<br>
<br><div class="gmail_quote">On Sat, Dec 27, 2008 at 12:03 AM, Jouni Malinen <span dir="ltr"><<a href="mailto:j@w1.fi">j@w1.fi</a>></span> 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, Dec 23, 2008 at 02:09:58PM +0530, Paresh Sawant wrote:<br>
<br>
> 2.2>I start AP2(ssid = "linksis-wpa2-ttls"), and after AP2 is up and<br>
> running, I stop AP1. wpa_supp receives "media connect" for AP2, and it<br>
> performs RSNA with AP2 successfully.<br>
><br>
> 2.3> I start AP1 again (without any change in configuration), and after AP1<br>
> is up and running, I stop AP2. wpa_supp receives "media connect" for AP1,<br>
> and it performs RSNA with AP1 successfully.<br>
><br>
> Conclusion: I see an issue in <2.3>, since AP1 does not honor the pmkid in<br>
> association request, it performs the full EAP again. Since wpa_supp sends<br>
> correct PMKID in association, I was expecting AP1 to directly jump to PTKSA,<br>
> but it does not happen that way.<br>
<br>
</div>How exactly did you "stop AP1"? If you just power cycled it, the PMKSA<br>
cache was cleared and the AP won't recognize the PMKID anymore. This is<br>
expected behavior. PMKs are unlikely to be cached in non-volatile<br>
memory (and really shouldn't be from security view point).<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>