Hi Dan,
> From: linux-wireless-ow...@vger.kernel.org [mailto:linux-wireless-
> ow...@vger.kernel.org] On Behalf Of Dan Williams
> Sent: Thursday, October 29, 2015 8:47 PM
> To: Amitkumar Karwar
> Cc: Julien Cubizolles; linux-wireless@vger.kernel.org; Nishant
> Sarmukadam
> Subject: Re: mwifiex problem: incompatible network settings
>
> On Thu, 2015-10-29 at 12:27 +0000, Amitkumar Karwar wrote:
> > Hi Julien,
> >
> > > From: Julien Cubizolles [mailto:j.cubizol...@free.fr]
> > > Sent: Thursday, October 29, 2015 3:09 AM
> > > To: Dan Williams
> > > Cc: Amitkumar Karwar; linux-wireless@vger.kernel.org
> > > Subject: Re: mwifiex problem: incompatible network settings
> > >
> > > Dan Williams <d...@redhat.com> writes:
> > >
> > > > He actually meant the wpa_supplicant configuration file, not the
> > > > supplicant's dbus config file. But when driven by NetworkManager,
> > > > there is no supplicant configuration file.
> > >
> > > Sorry about that.
> > >
> > > > Instead, you can find out what config NM is pushing to the
> > > > supplicant by checking the NetworkManager logs, where NM will log
> lines like:
> > >
> > > Here are the relevant entries from the syslog file:
> > >
> > > I included the failed attempt to connect to the WPA protected
> > > network named "southcentral" and the successful one to a non
> > > protected one named "FreeWifi".
> > >
> >
> > 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.
>
> NetworkManager leaves the 'protos' field empty, which allows the
> supplicant to choose the correct WPA/WPA2 mode depending on driver
> support. What you see in the NM logs is exactly what gets pushed to the
> supplicant in the network block. So if you don't see "proto" or
> "pairwise" or "group" in the NM logs, then it doesn't get pushed to the
> supplicant, and the supplicant uses its default behavior, which should
> be:
>
> proto=WPA RSN
> pairwise=CCMP TKIP
> group=CCMP TKIP WEP104 WEP40
>
Thanks for the inputs. I wasn't aware about this. Log with debug patch would
make the picture clear by dumping exact configuration received by driver.
Regards,
Amitkumar
N�����r��y����b�X��ǧv�^�){.n�+����{��*ޕ�,�{ay� ʇڙ�,j��f���h���z� �w���
���j:+v���w�j�m��������zZ+�����ݢj"��!�i
