Hi Julien,
> From: Julien Cubizolles [mailto:[email protected]]
> Sent: Thursday, November 05, 2015 3:34 AM
> To: Amitkumar Karwar
> Cc: Dan Williams; [email protected]; Nishant Sarmukadam
> Subject: Re: mwifiex problem: incompatible network settings
>
> Amitkumar Karwar <[email protected]> writes:
>
> > Thanks for the logs. I compared your network manager log with the one
> > on my setup. Both are same. Basically network manager log doesn't show
> > security info (WPA/WPA2, encryption mode etc). So we can't rely on
> > that.
> > I checked your kernel log shared in previous email. It's incomplete.
> > It didn't include information when connection was actually attempted.
> > Probably you can run "dmesg -c >> dmesg.log" in loop with some delay
> > to capture complete info. Otherwise sharing "/var/log/messages" is
> > also an option.
> > I have created a driver debug patch(attached). Could you please apply
> it and share complete dmesg log?
>
> I applied your patch. Here are the dmesg logs when logging to a WPA
> network with authentification (dmesg-WPA.log, ssid southcentral) and a
> network without authentification (dmesg-noWPA.log, ssid FreeWifi).
>
> Let me know if you need anything else.
>
> > Btw, do you see the problem if AP is configured in WPA2 security mode?
>
> Good catch, I changed my access point to WPA2 and now I can connect to
> it ! I attached the corresponding dmesg logs (dmesg-WPA2.log, ssid
> southcentral).
Thanks for the logs. We found one bug in our code. We expect vendor specific IE
at the beginning of IE buffer otherwise connection is rejected.
We will prepare a fix and get back.
Regards,
Amitkumar
N�����r��y����b�X��ǧv�^�){.n�+����{��*ޕ�,�{ay� ʇڙ�,j��f���h���z� �w���
���j:+v���w�j�m��������zZ+�����ݢj"��!�i
