It is WMP54G PCI card which doesn't support WPA2 as per the datasheet. But I could connect to AP configured with WPA2-personal using the same card. I think to make the set_pmkid succeed the card/driver must support WPA2. right?
<br><br><div class="gmail_quote">On Nov 27, 2007 9:40 AM, 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><div></div><div class="Wj3C7c">On Mon, Nov 26, 2007 at 01:08:59PM +0530, Paresh Sawant wrote:<br><br>> I'm running WPA supplicant compiled with CONFIG_USE_NDISUIO on WIN XP. I'm<br>> using Linksys PCI card on WIN XP. I observe that set_pmkid fails all the
<br>> time with this PCI card and hence (Re)association fails to carry pmkid in<br>> it. The same binary runs fine with Intel 3945abg card , carrying pmkid in<br>> its (Re)association request. Is set_pmkid failure a known issue with NDISUIO
<br>> on this PCI card on WIN XP ?<br><br></div></div>Are you sure the Linksys PCI card driver supports WPA2 with PMKSA<br>caching? Which card is this (Linksys has large number of completely<br>different cards) and which driver version are you using?
<br><font color="#888888"><br>--<br>Jouni Malinen PGP id EFC895FA<br>_______________________________________________<br>HostAP mailing list<br><a href="mailto:HostAP@shmoo.com">HostAP@shmoo.com
</a><br><a href="http://lists.shmoo.com/mailman/listinfo/hostap" target="_blank">http://lists.shmoo.com/mailman/listinfo/hostap</a><br></font></blockquote></div><br>