I my case it did. The 4-way handshake was failing because the supplicant was requesting the AES crypto service from the kernel and since it hadn't been built it the handshake failed. It was on the 4th step though.<div>
.<br><br><div class="gmail_quote">On Wed, Dec 5, 2012 at 3:00 PM, Sven Neumann <span dir="ltr"><<a href="mailto:s.neumann@raumfeld.com" target="_blank">s.neumann@raumfeld.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<div class="im"><br>
On Wed, 2012-12-05 at 12:48 -0600, Jemiah Aitch wrote:<br>
> Check that your kernel has all of the required<br>
> encryption components included. I had a similar issue and it turned<br>
> out that CRYPTO_AES hadn't been included. This was on an ARM processor<br>
> for an embedded kernel from TI. I'm not sure what it would be for<br>
> Ubuntu.<br>
<br>
</div>Does wpa-supplicant actually use the kernel crypto API or is this driver<br>
dependent?<br>
<br>
<br>
Regards,<br>
Sven<br>
<br>
<br>
<br>
</blockquote></div><br></div>