mwifiex problem: incompatible network settings

mwifiex problem: incompatible network settings

[Julien Cubizolles]

I can't connect anymore to my home wifi since upgrading my machine from
Ubuntu 15.04 to Ubuntuy 15.10. I was previously running kernel 4.3.0-rc2
from kernel.org without any problem. After the upgrade, and with the
same kernel, I couldn't connect anymore. I built 4.3.0-rc7, and the
problem remains. However, I can connect to the wifi access point from my
Android phone.

Here are the relevant lines from syslog. Let me know if you need more
information.

--8<---------------cut here---------------start------------->8---
Oct 26 16:11:38 touco wpa_supplicant[734]: wlx6045bdf646b4: Trying to associate with f4:ca:e5:ef:be:18 (SSID='southcentral' freq=2462 MHz)
Oct 26 16:11:38 touco wpa_supplicant[734]: wlx6045bdf646b4: CTRL-EVENT-ASSOC-REJECT status_code=1
Oct 26 16:11:38 touco kernel: [   66.745281] usb 1-3: info: trying to associate to 'southcentral' bssid f4:ca:e5:ef:be:18
Oct 26 16:11:38 touco kernel: [   66.745289] usb 1-3: info: mwifiex_is_network_compatible: failed: wpa_ie=0xdd wpa2_ie=0x0 WEP=d	WPA=d WPA2=d EncMode=0xfac02 privacy=0x1
Oct 26 16:11:38 touco kernel: [   66.745291] usb 1-3: Incompatible network settings
Oct 26 16:11:38 touco kernel: [   66.745294] usb 1-3: info: association to bssid f4:ca:e5:ef:be:18 failed
--8<---------------cut here---------------end--------------->8---


The machine is a Microsoft Surface Pro. I've been having a lot of
problems getting the wifi to work but never this particular one, and
they were all fixed in 4.3.0-rc2.

Julien.

Re: mwifiex problem: incompatible network settings

[Dan Williams]

On Mon, 2015-10-26 at 16:51 +0100, Julien Cubizolles wrote:
> I can't connect anymore to my home wifi since upgrading my machine from
> Ubuntu 15.04 to Ubuntuy 15.10. I was previously running kernel 4.3.0-rc2
> from kernel.org without any problem. After the upgrade, and with the
> same kernel, I couldn't connect anymore. I built 4.3.0-rc7, and the
> problem remains. However, I can connect to the wifi access point from my
> Android phone.
> 
> Here are the relevant lines from syslog. Let me know if you need more
> information.

The AP uses WPA, but the driver has been told that WPA is disabled.  Are
you using wpa_supplicant (or NetworkManager, or something else?) to
control the WiFi, and if so what version is it?

Dan

> --8<---------------cut here---------------start------------->8---
> Oct 26 16:11:38 touco wpa_supplicant[734]: wlx6045bdf646b4: Trying to associate with f4:ca:e5:ef:be:18 (SSID='southcentral' freq=2462 MHz)
> Oct 26 16:11:38 touco wpa_supplicant[734]: wlx6045bdf646b4: CTRL-EVENT-ASSOC-REJECT status_code=1
> Oct 26 16:11:38 touco kernel: [   66.745281] usb 1-3: info: trying to associate to 'southcentral' bssid f4:ca:e5:ef:be:18
> Oct 26 16:11:38 touco kernel: [   66.745289] usb 1-3: info: mwifiex_is_network_compatible: failed: wpa_ie=0xdd wpa2_ie=0x0 WEP=d	WPA=d WPA2=d EncMode=0xfac02 privacy=0x1
> Oct 26 16:11:38 touco kernel: [   66.745291] usb 1-3: Incompatible network settings
> Oct 26 16:11:38 touco kernel: [   66.745294] usb 1-3: info: association to bssid f4:ca:e5:ef:be:18 failed
> --8<---------------cut here---------------end--------------->8---
> 
> 
> The machine is a Microsoft Surface Pro. I've been having a lot of
> problems getting the wifi to work but never this particular one, and
> they were all fixed in 4.3.0-rc2.
> 
> Julien.
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: mwifiex problem: incompatible network settings

[Julien Cubizolles]

Dan Williams <dcbw@redhat.com> writes:

> On Mon, 2015-10-26 at 16:51 +0100, Julien Cubizolles wrote:
>> I can't connect anymore to my home wifi since upgrading my machine from
>> Ubuntu 15.04 to Ubuntuy 15.10. I was previously running kernel 4.3.0-rc2
>> from kernel.org without any problem. After the upgrade, and with the
>> same kernel, I couldn't connect anymore. I built 4.3.0-rc7, and the
>> problem remains. However, I can connect to the wifi access point from my
>> Android phone.
>> 
>> Here are the relevant lines from syslog. Let me know if you need more
>> information.
>
> The AP uses WPA, but the driver has been told that WPA is disabled.  Are
> you using wpa_supplicant (or NetworkManager, or something else?) to
> control the WiFi, and if so what version is it?

Yes, I'm using NetworkManager, version 1.0.4-ubuntu5, and I'm guessing
it's using wpa_supplicant. I deleted the configuration for this network
and created it again. The network is configured for WPA in
NetworkManager but I still get the same error message.

Thanks for your help.

Re: mwifiex problem: incompatible network settings

[Dan Williams]

On Mon, 2015-10-26 at 22:50 +0100, Julien Cubizolles wrote:
> Dan Williams <dcbw@redhat.com> writes:
> 
> > On Mon, 2015-10-26 at 16:51 +0100, Julien Cubizolles wrote:
> >> I can't connect anymore to my home wifi since upgrading my machine from
> >> Ubuntu 15.04 to Ubuntuy 15.10. I was previously running kernel 4.3.0-rc2
> >> from kernel.org without any problem. After the upgrade, and with the
> >> same kernel, I couldn't connect anymore. I built 4.3.0-rc7, and the
> >> problem remains. However, I can connect to the wifi access point from my
> >> Android phone.
> >> 
> >> Here are the relevant lines from syslog. Let me know if you need more
> >> information.
> >
> > The AP uses WPA, but the driver has been told that WPA is disabled.  Are
> > you using wpa_supplicant (or NetworkManager, or something else?) to
> > control the WiFi, and if so what version is it?
> 
> Yes, I'm using NetworkManager, version 1.0.4-ubuntu5, and I'm guessing
> it's using wpa_supplicant. I deleted the configuration for this network
> and created it again. The network is configured for WPA in
> NetworkManager but I still get the same error message.

Ok, I think it's a problem with the driver not correctly handling the
wpa_supplicant configuration requests.  Clearly wpa_supplicant is
sending WPA-enabled configuration, but the driver isn't interpreting it
correctly.  I'll leave it up to the mwifiex maintainers to figure that
out though.

Dan

Re: mwifiex problem: incompatible network settings

[Amitkumar Karwar]

Hi Julien,

>Yes, I'm using NetworkManager, version 1.0.4-ubuntu5, and I'm guessing
>it's using wpa_supplicant. I deleted the configuration for this network
>and created it again. The network is configured for WPA in
>NetworkManager but I still get the same error message.

Looks like driver has received encryption mode as TKIP, but didn't receive WPA ie. Hence the configuration didn't match with AP. Could you share wpa_supplicant configuration file if possible? Also, check if "sme->ie" is received in mwifiex_cfg80211_assoc() routine. Enable driver debug for the test using "echo 0xffffffff > /sys/kernel/debug/mwifiex/mlan0/debug_mask" and share dmesg logs.

Regards,
Amitkumar

Re: mwifiex problem: incompatible network settings

[Julien Cubizolles]

[-- Attachment #1: Type: text/plain, Size: 2798 bytes --]

Amitkumar Karwar <akarwar@marvell.com> writes:

> Hi Julien,
>
>>Yes, I'm using NetworkManager, version 1.0.4-ubuntu5, and I'm guessing
>>it's using wpa_supplicant. I deleted the configuration for this network
>>and created it again. The network is configured for WPA in
>>NetworkManager but I still get the same error message.
>
> Looks like driver has received encryption mode as TKIP, but didn't
> receive WPA ie. Hence the configuration didn't match with AP. Could
> you share wpa_supplicant configuration file if possible? 

Here is /etc/dbus-1/system.d/wpa_supplicant.conf, is this the one you
need ?

--8<---------------cut here---------------start------------->8---
<!DOCTYPE busconfig PUBLIC
 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
        <policy user="root">
                <allow own="fi.epitest.hostap.WPASupplicant"/>

                <allow send_destination="fi.epitest.hostap.WPASupplicant"/>
                <allow send_interface="fi.epitest.hostap.WPASupplicant"/>

                <allow own="fi.w1.wpa_supplicant1"/>

                <allow send_destination="fi.w1.wpa_supplicant1"/>
                <allow send_interface="fi.w1.wpa_supplicant1"/>
                <allow receive_sender="fi.w1.wpa_supplicant1" receive_type="signal"/>
        </policy>
        <policy group="netdev">
                <allow send_destination="fi.epitest.hostap.WPASupplicant"/>
                <allow send_interface="fi.epitest.hostap.WPASupplicant"/>

                <allow send_destination="fi.w1.wpa_supplicant1"/>
                <allow send_interface="fi.w1.wpa_supplicant1"/>
                <allow receive_sender="fi.w1.wpa_supplicant1" receive_type="signal"/>
        </policy>
        <policy context="default">
                <deny own="fi.epitest.hostap.WPASupplicant"/>
                <deny send_destination="fi.epitest.hostap.WPASupplicant"/>
                <deny send_interface="fi.epitest.hostap.WPASupplicant"/>

                <deny own="fi.w1.wpa_supplicant1"/>
                <deny send_destination="fi.w1.wpa_supplicant1"/>
                <deny send_interface="fi.w1.wpa_supplicant1"/>
                <deny receive_sender="fi.w1.wpa_supplicant1" receive_type="signal"/>
        </policy>
</busconfig>

--8<---------------cut here---------------end--------------->8---

> Also, check if "sme->ie" is received in mwifiex_cfg80211_assoc()
> routine.

Is that what the following debugging is for ? Or should I do something
else ?

> Enable driver debug for the test using "echo 0xffffffff >
> /sys/kernel/debug/mwifiex/mlan0/debug_mask" and share dmesg logs.

Please find them attached.

Regards,

Julien.


[-- Attachment #2: mwifiex-dmesg.txt.gz --]
[-- Type: application/gzip, Size: 25209 bytes --]

Re: mwifiex problem: incompatible network settings

[Dan Williams]

On Tue, 2015-10-27 at 22:44 +0100, Julien Cubizolles wrote:
> Amitkumar Karwar <akarwar@marvell.com> writes:
> 
> > Hi Julien,
> >
> >>Yes, I'm using NetworkManager, version 1.0.4-ubuntu5, and I'm guessing
> >>it's using wpa_supplicant. I deleted the configuration for this network
> >>and created it again. The network is configured for WPA in
> >>NetworkManager but I still get the same error message.
> >
> > Looks like driver has received encryption mode as TKIP, but didn't
> > receive WPA ie. Hence the configuration didn't match with AP. Could
> > you share wpa_supplicant configuration file if possible? 
> 
> Here is /etc/dbus-1/system.d/wpa_supplicant.conf, is this the one you
> need ?

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.

Instead, you can find out what config NM is pushing to the supplicant by
checking the NetworkManager logs, where NM will log lines like:

NetworkManager[1163]: <info>  (wlp4s0): Activation: (wifi) connection
'homewifi' has security, and secrets exist.  No new secrets needed.
NetworkManager[1163]: <info>  Config: added 'ssid' value 'homewifi'
NetworkManager[1163]: <info>  Config: added 'scan_ssid' value '1'
NetworkManager[1163]: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
NetworkManager[1163]: <info>  Config: added 'psk' value '<omitted>'
NetworkManager[1163]: <info>  Config: added 'proto' value 'WPA RSN'
NetworkManager[1163]: <info>  Config: set interface ap_scan to 1

That is almost exactly what would be in the wpa_supplicant config file.
Can you grab this info from your machine for Julien?

Dan

> --8<---------------cut here---------------start------------->8---
> <!DOCTYPE busconfig PUBLIC
>  "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
>  "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
> <busconfig>
>         <policy user="root">
>                 <allow own="fi.epitest.hostap.WPASupplicant"/>
> 
>                 <allow send_destination="fi.epitest.hostap.WPASupplicant"/>
>                 <allow send_interface="fi.epitest.hostap.WPASupplicant"/>
> 
>                 <allow own="fi.w1.wpa_supplicant1"/>
> 
>                 <allow send_destination="fi.w1.wpa_supplicant1"/>
>                 <allow send_interface="fi.w1.wpa_supplicant1"/>
>                 <allow receive_sender="fi.w1.wpa_supplicant1" receive_type="signal"/>
>         </policy>
>         <policy group="netdev">
>                 <allow send_destination="fi.epitest.hostap.WPASupplicant"/>
>                 <allow send_interface="fi.epitest.hostap.WPASupplicant"/>
> 
>                 <allow send_destination="fi.w1.wpa_supplicant1"/>
>                 <allow send_interface="fi.w1.wpa_supplicant1"/>
>                 <allow receive_sender="fi.w1.wpa_supplicant1" receive_type="signal"/>
>         </policy>
>         <policy context="default">
>                 <deny own="fi.epitest.hostap.WPASupplicant"/>
>                 <deny send_destination="fi.epitest.hostap.WPASupplicant"/>
>                 <deny send_interface="fi.epitest.hostap.WPASupplicant"/>
> 
>                 <deny own="fi.w1.wpa_supplicant1"/>
>                 <deny send_destination="fi.w1.wpa_supplicant1"/>
>                 <deny send_interface="fi.w1.wpa_supplicant1"/>
>                 <deny receive_sender="fi.w1.wpa_supplicant1" receive_type="signal"/>
>         </policy>
> </busconfig>
> 
> --8<---------------cut here---------------end--------------->8---
> 
> > Also, check if "sme->ie" is received in mwifiex_cfg80211_assoc()
> > routine.
> 
> Is that what the following debugging is for ? Or should I do something
> else ?
> 
> > Enable driver debug for the test using "echo 0xffffffff >
> > /sys/kernel/debug/mwifiex/mlan0/debug_mask" and share dmesg logs.
> 
> Please find them attached.
> 
> Regards,
> 
> Julien.
> 

Re: mwifiex problem: incompatible network settings

[Julien Cubizolles]

Dan Williams <dcbw@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".

--8<---------------cut here---------------start------------->8---
Oct 28 22:27:17 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): Activation: starting connection 'southcentral' (4c475300-8ffd-4dda-8445-bbd3a9cdc538)
Oct 28 22:27:17 touco dbus[675]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Oct 28 22:27:17 touco NetworkManager[656]: <warn>  Connection disconnected (reason -3)
Oct 28 22:27:17 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): supplicant interface state: completed -> disconnected
Oct 28 22:27:17 touco systemd[1]: Starting Network Manager Script Dispatcher Service...
Oct 28 22:27:17 touco NetworkManager[656]: <warn>  Connection disconnected (reason 3)
Oct 28 22:27:17 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct 28 22:27:17 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 28 22:27:17 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): Activation: (wifi) access point 'southcentral' has security, but secrets are required.
Oct 28 22:27:17 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): device state change: config -> need-auth (reason 'none') [50 60 0]
Oct 28 22:27:17 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Oct 28 22:27:17 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 28 22:27:17 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): Activation: (wifi) connection 'southcentral' has security, and secrets exist.  No new secrets needed.
Oct 28 22:27:17 touco NetworkManager[656]: <info>  Config: added 'ssid' value 'southcentral'
Oct 28 22:27:17 touco NetworkManager[656]: <info>  Config: added 'scan_ssid' value '1'
Oct 28 22:27:17 touco NetworkManager[656]: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Oct 28 22:27:17 touco NetworkManager[656]: <info>  Config: added 'psk' value '<omitted>'
Oct 28 22:27:17 touco NetworkManager[656]: <info>  Config: set interface ap_scan to 1
Oct 28 22:27:17 touco dbus[675]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Oct 28 22:27:17 touco nm-dispatcher: Dispatching action 'down' for wlx6045bdf646b4
Oct 28 22:27:17 touco systemd[1]: Started Network Manager Script Dispatcher Service.
Oct 28 22:27:19 touco ntpd[5268]: Deleting interface #7 wlx6045bdf646b4, fe80::6245:bdff:fef6:46b4#123, interface stats: received=0, sent=0, dropped=0, active_time=732 secs
Oct 28 22:27:19 touco ntpd[5268]: Deleting interface #3 wlx6045bdf646b4, 10.2.45.69#123, interface stats: received=0, sent=0, dropped=0, active_time=732 secs
Oct 28 22:27:19 touco ntpd[5268]: peers refreshed
Oct 28 22:27:21 touco wpa_supplicant[800]: wlx6045bdf646b4: Trying to associate with f4:ca:e5:ef:be:18 (SSID='southcentral' freq=2462 MHz)
Oct 28 22:27:21 touco wpa_supplicant[800]: wlx6045bdf646b4: CTRL-EVENT-ASSOC-REJECT status_code=1
Oct 28 22:27:21 touco kernel: [ 1755.971734] usb 1-3: info: trying to associate to 'southcentral' bssid f4:ca:e5:ef:be:18
Oct 28 22:27:21 touco kernel: [ 1755.971755] usb 1-3: info: mwifiex_is_network_compatible: failed: wpa_ie=0xdd wpa2_ie=0x0 WEP=d	WPA=d WPA2=d EncMode=0xfac02 privacy=0x1
Oct 28 22:27:21 touco kernel: [ 1755.971760] usb 1-3: Incompatible network settings
Oct 28 22:27:21 touco kernel: [ 1755.971766] usb 1-3: info: association to bssid f4:ca:e5:ef:be:18 failed
Oct 28 22:27:21 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): supplicant interface state: disconnected -> scanning
Oct 28 22:27:22 touco wpa_supplicant[800]: wlx6045bdf646b4: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Oct 28 22:27:25 touco wpa_supplicant[800]: wlx6045bdf646b4: Trying to associate with f4:ca:e5:ef:be:18 (SSID='southcentral' freq=2462 MHz)
Oct 28 22:27:25 touco wpa_supplicant[800]: wlx6045bdf646b4: CTRL-EVENT-ASSOC-REJECT status_code=1
Oct 28 22:27:25 touco kernel: [ 1760.400746] usb 1-3: info: trying to associate to 'southcentral' bssid f4:ca:e5:ef:be:18
Oct 28 22:27:25 touco kernel: [ 1760.400757] usb 1-3: info: mwifiex_is_network_compatible: failed: wpa_ie=0xdd wpa2_ie=0x0 WEP=d	WPA=d WPA2=d EncMode=0xfac02 privacy=0x1
Oct 28 22:27:25 touco kernel: [ 1760.400759] usb 1-3: Incompatible network settings
Oct 28 22:27:25 touco kernel: [ 1760.400762] usb 1-3: info: association to bssid f4:ca:e5:ef:be:18 failed
Oct 28 22:27:25 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): supplicant interface state: scanning -> disconnected
Oct 28 22:27:26 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): supplicant interface state: disconnected -> scanning
Oct 28 22:27:30 touco wpa_supplicant[800]: wlx6045bdf646b4: Trying to associate with f4:ca:e5:ef:be:18 (SSID='southcentral' freq=2462 MHz)
Oct 28 22:27:30 touco wpa_supplicant[800]: wlx6045bdf646b4: CTRL-EVENT-ASSOC-REJECT status_code=1
Oct 28 22:27:30 touco wpa_supplicant[800]: wlx6045bdf646b4: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="southcentral" auth_failures=1 duration=10 reason=CONN_FAILED
Oct 28 22:27:30 touco kernel: [ 1765.252338] usb 1-3: info: trying to associate to 'southcentral' bssid f4:ca:e5:ef:be:18
Oct 28 22:27:30 touco kernel: [ 1765.252355] usb 1-3: info: mwifiex_is_network_compatible: failed: wpa_ie=0xdd wpa2_ie=0x0 WEP=d	WPA=d WPA2=d EncMode=0xfac02 privacy=0x1
Oct 28 22:27:30 touco kernel: [ 1765.252359] usb 1-3: Incompatible network settings
Oct 28 22:27:30 touco kernel: [ 1765.252362] usb 1-3: info: association to bssid f4:ca:e5:ef:be:18 failed
Oct 28 22:27:30 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): supplicant interface state: scanning -> disconnected
Oct 28 22:27:35 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): supplicant interface state: disconnected -> scanning
Oct 28 22:27:42 touco NetworkManager[656]: <warn>  (wlx6045bdf646b4): Activation: (wifi) association took too long, failing activation
Oct 28 22:27:42 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): device state change: config -> failed (reason 'ssid-not-found') [50 120 53]
Oct 28 22:27:42 touco NetworkManager[656]: <info>  Connection 'southcentral' failed to autoconnect; 3 tries left
Oct 28 22:27:42 touco NetworkManager[656]: <warn>  (wlx6045bdf646b4): Activation: failed for connection 'southcentral'
Oct 28 22:27:42 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): device state change: failed -> disconnected (reason 'none') [120 30 0]
Oct 28 22:27:42 touco kernel: [ 1777.784238] IPv6: ADDRCONF(NETDEV_UP): wlx6045bdf646b4: link is not ready
Oct 28 22:27:42 touco NetworkManager[656]: <info>  Device 'wlx6045bdf646b4' has no connection; scheduling activate_check in 0 seconds.
Oct 28 22:27:42 touco NetworkManager[656]: <warn>  Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect.
Oct 28 22:27:42 touco NetworkManager[656]: (NetworkManager:656): GLib-CRITICAL **: Source ID 2796 was not found when attempting to remove it
Oct 28 22:27:42 touco NetworkManager[656]: <info>  Auto-activating connection 'FreeWifi'.
Oct 28 22:27:42 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): Activation: starting connection 'FreeWifi' (0d348d83-b3b0-4ea0-894d-7b3a9e295392)
Oct 28 22:27:42 touco NetworkManager[656]: <warn>  Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect.
Oct 28 22:27:42 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct 28 22:27:42 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 28 22:27:42 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): Activation: (wifi) connection 'FreeWifi' requires no security.  No secrets needed.
Oct 28 22:27:42 touco NetworkManager[656]: <info>  Config: added 'ssid' value 'FreeWifi'
Oct 28 22:27:42 touco NetworkManager[656]: <info>  Config: added 'scan_ssid' value '1'
Oct 28 22:27:42 touco NetworkManager[656]: <info>  Config: added 'key_mgmt' value 'NONE'
Oct 28 22:27:42 touco NetworkManager[656]: <warn>  Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect.
Oct 28 22:27:42 touco NetworkManager[656]: <info>  Config: set interface ap_scan to 1
Oct 28 22:27:46 touco wpa_supplicant[800]: wlx6045bdf646b4: Trying to associate with f4:ca:e5:ef:be:19 (SSID='FreeWifi' freq=2462 MHz)
Oct 28 22:27:46 touco kernel: [ 1781.642487] usb 1-3: info: trying to associate to 'FreeWifi' bssid f4:ca:e5:ef:be:19
Oct 28 22:27:46 touco kernel: [ 1781.657394] usb 1-3: info: associated to bssid f4:ca:e5:ef:be:19 successfully
Oct 28 22:27:46 touco kernel: [ 1781.657454] IPv6: ADDRCONF(NETDEV_CHANGE): wlx6045bdf646b4: link becomes ready
Oct 28 22:27:46 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): supplicant interface state: scanning -> associating
Oct 28 22:27:46 touco wpa_supplicant[800]: wlx6045bdf646b4: Associated with f4:ca:e5:ef:be:19
Oct 28 22:27:46 touco wpa_supplicant[800]: wlx6045bdf646b4: CTRL-EVENT-CONNECTED - Connection to f4:ca:e5:ef:be:19 completed [id=0 id_str=]
Oct 28 22:27:46 touco wpa_supplicant[800]: WMM AC: Missing IEs
Oct 28 22:27:46 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): supplicant interface state: associating -> completed
Oct 28 22:27:46 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'FreeWifi'.
Oct 28 22:27:46 touco NetworkManager[656]: <info>  (wlx6045bdf646b4): device state change: config -> ip-config (reason 'none') [50 70 0]
Oct 28 22:27:46 touco NetworkManager[656]: <info>  Activation (wlx6045bdf646b4) Beginning DHCPv4 transaction (timeout in 45 seconds)
Oct 28 22:27:46 touco NetworkManager[656]: <info>  dhclient started with pid 5557
Oct 28 22:27:46 touco dhclient: DHCPREQUEST of 10.2.45.69 on wlx6045bdf646b4 to 255.255.255.255 port 67 (xid=0x4a227e1)
Oct 28 22:27:46 touco dhclient: DHCPACK of 10.2.45.69 from 10.7.255.252
Oct 28 22:27:46 touco NetworkManager[656]: <info>    address 10.2.45.69
Oct 28 22:27:46 touco NetworkManager[656]: <info>    plen 13 (255.248.0.0)
Oct 28 22:27:46 touco NetworkManager[656]: <info>    gateway 10.7.255.254
Oct 28 22:27:46 touco NetworkManager[656]: <info>    server identifier 10.7.255.254
Oct 28 22:27:46 touco NetworkManager[656]: <info>    lease time 3600
Oct 28 22:27:46 touco NetworkManager[656]: <info>    nameserver '212.27.40.241'
Oct 28 22:27:46 touco NetworkManager[656]: <info>    nameserver '212.27.40.240'
Oct 28 22:27:46 touco NetworkManager[656]: <info>  (wlx6045bdf646b4):
DHCPv4 state changed unknown -> bound
--8<---------------cut here---------------end--------------->8---

RE: mwifiex problem: incompatible network settings

[Amitkumar Karwar]

Hi Julien,

> From: Julien Cubizolles [mailto:j.cubizolles@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 <dcbw@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.
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?

Btw, do you see the problem if AP is configured in WPA2 security mode?

Regards,
Amitkumar

Re: mwifiex problem: incompatible network settings

[Dan Williams]

On Thu, 2015-10-29 at 12:27 +0000, Amitkumar Karwar wrote:
> Hi Julien,
> 
> > From: Julien Cubizolles [mailto:j.cubizolles@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 <dcbw@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

Dan

RE: mwifiex problem: incompatible network settings

[Amitkumar Karwar]

SGkgRGFuLA0KDQo+IEZyb206IGxpbnV4LXdpcmVsZXNzLW93bmVyQHZnZXIua2VybmVsLm9yZyBb
bWFpbHRvOmxpbnV4LXdpcmVsZXNzLQ0KPiBvd25lckB2Z2VyLmtlcm5lbC5vcmddIE9uIEJlaGFs
ZiBPZiBEYW4gV2lsbGlhbXMNCj4gU2VudDogVGh1cnNkYXksIE9jdG9iZXIgMjksIDIwMTUgODo0
NyBQTQ0KPiBUbzogQW1pdGt1bWFyIEthcndhcg0KPiBDYzogSnVsaWVuIEN1Yml6b2xsZXM7IGxp
bnV4LXdpcmVsZXNzQHZnZXIua2VybmVsLm9yZzsgTmlzaGFudA0KPiBTYXJtdWthZGFtDQo+IFN1
YmplY3Q6IFJlOiBtd2lmaWV4IHByb2JsZW06IGluY29tcGF0aWJsZSBuZXR3b3JrIHNldHRpbmdz
DQo+IA0KPiBPbiBUaHUsIDIwMTUtMTAtMjkgYXQgMTI6MjcgKzAwMDAsIEFtaXRrdW1hciBLYXJ3
YXIgd3JvdGU6DQo+ID4gSGkgSnVsaWVuLA0KPiA+DQo+ID4gPiBGcm9tOiBKdWxpZW4gQ3ViaXpv
bGxlcyBbbWFpbHRvOmouY3ViaXpvbGxlc0BmcmVlLmZyXQ0KPiA+ID4gU2VudDogVGh1cnNkYXks
IE9jdG9iZXIgMjksIDIwMTUgMzowOSBBTQ0KPiA+ID4gVG86IERhbiBXaWxsaWFtcw0KPiA+ID4g
Q2M6IEFtaXRrdW1hciBLYXJ3YXI7IGxpbnV4LXdpcmVsZXNzQHZnZXIua2VybmVsLm9yZw0KPiA+
ID4gU3ViamVjdDogUmU6IG13aWZpZXggcHJvYmxlbTogaW5jb21wYXRpYmxlIG5ldHdvcmsgc2V0
dGluZ3MNCj4gPiA+DQo+ID4gPiBEYW4gV2lsbGlhbXMgPGRjYndAcmVkaGF0LmNvbT4gd3JpdGVz
Og0KPiA+ID4NCj4gPiA+ID4gSGUgYWN0dWFsbHkgbWVhbnQgdGhlIHdwYV9zdXBwbGljYW50IGNv
bmZpZ3VyYXRpb24gZmlsZSwgbm90IHRoZQ0KPiA+ID4gPiBzdXBwbGljYW50J3MgZGJ1cyBjb25m
aWcgZmlsZS4gIEJ1dCB3aGVuIGRyaXZlbiBieSBOZXR3b3JrTWFuYWdlciwNCj4gPiA+ID4gdGhl
cmUgaXMgbm8gc3VwcGxpY2FudCBjb25maWd1cmF0aW9uIGZpbGUuDQo+ID4gPg0KPiA+ID4gU29y
cnkgYWJvdXQgdGhhdC4NCj4gPiA+DQo+ID4gPiA+IEluc3RlYWQsIHlvdSBjYW4gZmluZCBvdXQg
d2hhdCBjb25maWcgTk0gaXMgcHVzaGluZyB0byB0aGUNCj4gPiA+ID4gc3VwcGxpY2FudCBieSBj
aGVja2luZyB0aGUgTmV0d29ya01hbmFnZXIgbG9ncywgd2hlcmUgTk0gd2lsbCBsb2cNCj4gbGlu
ZXMgbGlrZToNCj4gPiA+DQo+ID4gPiBIZXJlIGFyZSB0aGUgcmVsZXZhbnQgZW50cmllcyBmcm9t
IHRoZSBzeXNsb2cgZmlsZToNCj4gPiA+DQo+ID4gPiBJIGluY2x1ZGVkIHRoZSBmYWlsZWQgYXR0
ZW1wdCB0byBjb25uZWN0IHRvIHRoZSBXUEEgcHJvdGVjdGVkDQo+ID4gPiBuZXR3b3JrIG5hbWVk
ICJzb3V0aGNlbnRyYWwiIGFuZCB0aGUgc3VjY2Vzc2Z1bCBvbmUgdG8gYSBub24NCj4gPiA+IHBy
b3RlY3RlZCBvbmUgbmFtZWQgIkZyZWVXaWZpIi4NCj4gPiA+DQo+ID4NCj4gPiBUaGFua3MgZm9y
IHRoZSBsb2dzLiBJIGNvbXBhcmVkIHlvdXIgbmV0d29yayBtYW5hZ2VyIGxvZyB3aXRoIHRoZSBv
bmUNCj4gb24gbXkgc2V0dXAuIEJvdGggYXJlIHNhbWUuIEJhc2ljYWxseSBuZXR3b3JrIG1hbmFn
ZXIgbG9nIGRvZXNuJ3Qgc2hvdw0KPiBzZWN1cml0eSBpbmZvIChXUEEvV1BBMiwgZW5jcnlwdGlv
biBtb2RlIGV0YykuIFNvIHdlIGNhbid0IHJlbHkgb24gdGhhdC4NCj4gDQo+IE5ldHdvcmtNYW5h
Z2VyIGxlYXZlcyB0aGUgJ3Byb3RvcycgZmllbGQgZW1wdHksIHdoaWNoIGFsbG93cyB0aGUNCj4g
c3VwcGxpY2FudCB0byBjaG9vc2UgdGhlIGNvcnJlY3QgV1BBL1dQQTIgbW9kZSBkZXBlbmRpbmcg
b24gZHJpdmVyDQo+IHN1cHBvcnQuICBXaGF0IHlvdSBzZWUgaW4gdGhlIE5NIGxvZ3MgaXMgZXhh
Y3RseSB3aGF0IGdldHMgcHVzaGVkIHRvIHRoZQ0KPiBzdXBwbGljYW50IGluIHRoZSBuZXR3b3Jr
IGJsb2NrLiAgU28gaWYgeW91IGRvbid0IHNlZSAicHJvdG8iIG9yDQo+ICJwYWlyd2lzZSIgb3Ig
Imdyb3VwIiBpbiB0aGUgTk0gbG9ncywgdGhlbiBpdCBkb2Vzbid0IGdldCBwdXNoZWQgdG8gdGhl
DQo+IHN1cHBsaWNhbnQsIGFuZCB0aGUgc3VwcGxpY2FudCB1c2VzIGl0cyBkZWZhdWx0IGJlaGF2
aW9yLCB3aGljaCBzaG91bGQNCj4gYmU6DQo+IA0KPiBwcm90bz1XUEEgUlNODQo+IHBhaXJ3aXNl
PUNDTVAgVEtJUA0KPiBncm91cD1DQ01QIFRLSVAgV0VQMTA0IFdFUDQwDQo+IA0KDQpUaGFua3Mg
Zm9yIHRoZSBpbnB1dHMuIEkgd2Fzbid0IGF3YXJlIGFib3V0IHRoaXMuIExvZyB3aXRoIGRlYnVn
IHBhdGNoIHdvdWxkIG1ha2UgdGhlIHBpY3R1cmUgY2xlYXIgYnkgZHVtcGluZyBleGFjdCBjb25m
aWd1cmF0aW9uIHJlY2VpdmVkIGJ5IGRyaXZlci4NCg0KUmVnYXJkcywNCkFtaXRrdW1hcg0K

Re: mwifiex problem: incompatible network settings

[Julien Cubizolles]

[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]

Amitkumar Karwar <akarwar@marvell.com> 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).

> Regards,
> Amitkumar

[-- Attachment #2: dmesg-WPA.log --]
[-- Type: application/octet-stream, Size: 3138 bytes --]

[  408.658220] IPv6: ADDRCONF(NETDEV_UP): wlx6045bdf646b4: link is not ready
[  408.706137] IPv6: ADDRCONF(NETDEV_UP): wlx6045bdf646b4: link is not ready
[  421.728415] MWIFIEX: auth_type = 0
[  421.728424] MWIFIEX: pairwise enc_mode = 1
[  421.728428] MWIFIEX: groupwise enc_mode = fac02
[  421.728436] IE:00000000: 7f 04 00 00 0a 02 dd 16 00 50 f2 01 01 00 00 50
[  421.728442] IE:00000010: f2 02 01 00 00 50 f2 04 01 00 00 50 f2 02
[  421.728456] usb 1-3: info: trying to associate to 'southcentral' bssid f4:ca:e5:ef:be:18
[  421.728476] usb 1-3: info: mwifiex_is_network_compatible: failed: wpa_ie=0xdd wpa2_ie=0x0 WEP=d	WPA=d WPA2=d EncMode=0xfac02 privacy=0x1
[  421.728483] usb 1-3: Incompatible network settings
[  421.728490] usb 1-3: info: association to bssid f4:ca:e5:ef:be:18 failed
[  425.675580] MWIFIEX: auth_type = 0
[  425.675590] MWIFIEX: pairwise enc_mode = 1
[  425.675595] MWIFIEX: groupwise enc_mode = fac02
[  425.675604] IE:00000000: 7f 04 00 00 0a 02 dd 16 00 50 f2 01 01 00 00 50
[  425.675610] IE:00000010: f2 02 01 00 00 50 f2 04 01 00 00 50 f2 02
[  425.675624] usb 1-3: info: trying to associate to 'southcentral' bssid f4:ca:e5:ef:be:18
[  425.675645] usb 1-3: info: mwifiex_is_network_compatible: failed: wpa_ie=0xdd wpa2_ie=0x0 WEP=d	WPA=d WPA2=d EncMode=0xfac02 privacy=0x1
[  425.675652] usb 1-3: Incompatible network settings
[  425.675660] usb 1-3: info: association to bssid f4:ca:e5:ef:be:18 failed
[  430.023460] MWIFIEX: auth_type = 0
[  430.023468] MWIFIEX: pairwise enc_mode = 1
[  430.023472] MWIFIEX: groupwise enc_mode = fac02
[  430.023480] IE:00000000: 7f 04 00 00 0a 02 dd 16 00 50 f2 01 01 00 00 50
[  430.023485] IE:00000010: f2 02 01 00 00 50 f2 04 01 00 00 50 f2 02
[  430.023497] usb 1-3: info: trying to associate to 'southcentral' bssid f4:ca:e5:ef:be:18
[  430.023513] usb 1-3: info: mwifiex_is_network_compatible: failed: wpa_ie=0xdd wpa2_ie=0x0 WEP=d	WPA=d WPA2=d EncMode=0xfac02 privacy=0x1
[  430.023517] usb 1-3: Incompatible network settings
[  430.023521] usb 1-3: info: association to bssid f4:ca:e5:ef:be:18 failed
[  434.874343] MWIFIEX: auth_type = 0
[  434.874351] MWIFIEX: pairwise enc_mode = 1
[  434.874356] MWIFIEX: groupwise enc_mode = fac02
[  434.874365] IE:00000000: 7f 04 00 00 0a 02 dd 16 00 50 f2 01 01 00 00 50
[  434.874370] IE:00000010: f2 02 01 00 00 50 f2 04 01 00 00 50 f2 02
[  434.874385] usb 1-3: info: trying to associate to 'southcentral' bssid f4:ca:e5:ef:be:18
[  434.874404] usb 1-3: info: mwifiex_is_network_compatible: failed: wpa_ie=0xdd wpa2_ie=0x0 WEP=d	WPA=d WPA2=d EncMode=0xfac02 privacy=0x1
[  434.874411] usb 1-3: Incompatible network settings
[  434.874419] usb 1-3: info: association to bssid f4:ca:e5:ef:be:18 failed
[  443.099983] IPv6: ADDRCONF(NETDEV_UP): wlx6045bdf646b4: link is not ready
[  443.725739] MWIFIEX: auth_type = 0
[  443.725753] IE:00000000: 7f 04 00 00 0a 02
[  443.725768] usb 1-3: info: trying to associate to 'FreeWifi' bssid f4:ca:e5:ef:be:19
[  443.740830] usb 1-3: info: associated to bssid f4:ca:e5:ef:be:19 successfully
[  443.740978] IPv6: ADDRCONF(NETDEV_CHANGE): wlx6045bdf646b4: link becomes ready

[-- Attachment #3: dmesg-noWPA.log --]
[-- Type: application/octet-stream, Size: 302 bytes --]

[  571.959634] MWIFIEX: auth_type = 0
[  571.959647] IE:00000000: 7f 04 00 00 0a 02
[  571.959661] usb 1-3: info: trying to associate to 'FreeWifi' bssid f4:ca:e5:ef:be:19
[  571.972941] usb 1-3: info: associated to bssid f4:ca:e5:ef:be:19 successfully
[  577.161064] usb 1-3: Rx of mgmt packet failed

[-- Attachment #4: dmesg-WPA2.log --]
[-- Type: application/octet-stream, Size: 539 bytes --]

[  282.545909] MWIFIEX: auth_type = 0
[  282.545912] MWIFIEX: pairwise enc_mode = 1
[  282.545914] MWIFIEX: groupwise enc_mode = fac02
[  282.545916] MWIFIEX: wpa = 0, wpa2 = 1
[  282.545919] IE:00000000: 30 14 01 00 00 0f ac 02 01 00 00 0f ac 04 01 00
[  282.545922] IE:00000010: 00 0f ac 02 00 00 7f 04 00 00 0a 02
[  282.545927] usb 1-3: info: trying to associate to 'southcentral' bssid f4:ca:e5:ef:be:18
[  282.560325] usb 1-3: info: associated to bssid f4:ca:e5:ef:be:18 successfully
[  283.268231] usb 1-3: Rx of mgmt packet failed

RE: mwifiex problem: incompatible network settings

[Amitkumar Karwar]

SGkgSnVsaWVuLA0KDQo+IEZyb206IEp1bGllbiBDdWJpem9sbGVzIFttYWlsdG86ai5jdWJpem9s
bGVzQGZyZWUuZnJdDQo+IFNlbnQ6IFRodXJzZGF5LCBOb3ZlbWJlciAwNSwgMjAxNSAzOjM0IEFN
DQo+IFRvOiBBbWl0a3VtYXIgS2Fyd2FyDQo+IENjOiBEYW4gV2lsbGlhbXM7IGxpbnV4LXdpcmVs
ZXNzQHZnZXIua2VybmVsLm9yZzsgTmlzaGFudCBTYXJtdWthZGFtDQo+IFN1YmplY3Q6IFJlOiBt
d2lmaWV4IHByb2JsZW06IGluY29tcGF0aWJsZSBuZXR3b3JrIHNldHRpbmdzDQo+IA0KPiBBbWl0
a3VtYXIgS2Fyd2FyIDxha2Fyd2FyQG1hcnZlbGwuY29tPiB3cml0ZXM6DQo+IA0KPiA+IFRoYW5r
cyBmb3IgdGhlIGxvZ3MuIEkgY29tcGFyZWQgeW91ciBuZXR3b3JrIG1hbmFnZXIgbG9nIHdpdGgg
dGhlIG9uZQ0KPiA+IG9uIG15IHNldHVwLiBCb3RoIGFyZSBzYW1lLiBCYXNpY2FsbHkgbmV0d29y
ayBtYW5hZ2VyIGxvZyBkb2Vzbid0IHNob3cNCj4gPiBzZWN1cml0eSBpbmZvIChXUEEvV1BBMiwg
ZW5jcnlwdGlvbiBtb2RlIGV0YykuIFNvIHdlIGNhbid0IHJlbHkgb24NCj4gPiB0aGF0Lg0KPiA+
IEkgY2hlY2tlZCB5b3VyIGtlcm5lbCBsb2cgc2hhcmVkIGluIHByZXZpb3VzIGVtYWlsLiBJdCdz
IGluY29tcGxldGUuDQo+ID4gSXQgZGlkbid0IGluY2x1ZGUgaW5mb3JtYXRpb24gd2hlbiBjb25u
ZWN0aW9uIHdhcyBhY3R1YWxseSBhdHRlbXB0ZWQuDQo+ID4gUHJvYmFibHkgeW91IGNhbiBydW4g
ImRtZXNnIC1jID4+IGRtZXNnLmxvZyIgaW4gbG9vcCB3aXRoIHNvbWUgZGVsYXkNCj4gPiB0byBj
YXB0dXJlIGNvbXBsZXRlIGluZm8uIE90aGVyd2lzZSBzaGFyaW5nICIvdmFyL2xvZy9tZXNzYWdl
cyIgaXMNCj4gPiBhbHNvIGFuIG9wdGlvbi4NCj4gPiBJIGhhdmUgY3JlYXRlZCBhIGRyaXZlciBk
ZWJ1ZyBwYXRjaChhdHRhY2hlZCkuIENvdWxkIHlvdSBwbGVhc2UgYXBwbHkNCj4gaXQgYW5kIHNo
YXJlIGNvbXBsZXRlIGRtZXNnIGxvZz8NCj4gDQo+IEkgYXBwbGllZCB5b3VyIHBhdGNoLiBIZXJl
IGFyZSB0aGUgZG1lc2cgbG9ncyB3aGVuIGxvZ2dpbmcgdG8gYSBXUEENCj4gbmV0d29yayB3aXRo
IGF1dGhlbnRpZmljYXRpb24gKGRtZXNnLVdQQS5sb2csIHNzaWQgc291dGhjZW50cmFsKSBhbmQg
YQ0KPiBuZXR3b3JrIHdpdGhvdXQgYXV0aGVudGlmaWNhdGlvbiAoZG1lc2ctbm9XUEEubG9nLCBz
c2lkIEZyZWVXaWZpKS4NCj4gDQo+IExldCBtZSBrbm93IGlmIHlvdSBuZWVkIGFueXRoaW5nIGVs
c2UuDQo+IA0KPiA+IEJ0dywgZG8geW91IHNlZSB0aGUgcHJvYmxlbSBpZiBBUCBpcyBjb25maWd1
cmVkIGluIFdQQTIgc2VjdXJpdHkgbW9kZT8NCj4gDQo+IEdvb2QgY2F0Y2gsIEkgY2hhbmdlZCBt
eSBhY2Nlc3MgcG9pbnQgdG8gV1BBMiBhbmQgbm93IEkgY2FuIGNvbm5lY3QgdG8NCj4gaXTCoCEg
SSBhdHRhY2hlZCB0aGUgY29ycmVzcG9uZGluZyBkbWVzZyBsb2dzIChkbWVzZy1XUEEyLmxvZywg
c3NpZA0KPiBzb3V0aGNlbnRyYWwpLg0KDQpUaGFua3MgZm9yIHRoZSBsb2dzLiBXZSBmb3VuZCBv
bmUgYnVnIGluIG91ciBjb2RlLiBXZSBleHBlY3QgdmVuZG9yIHNwZWNpZmljIElFIGF0IHRoZSBi
ZWdpbm5pbmcgb2YgSUUgYnVmZmVyIG90aGVyd2lzZSBjb25uZWN0aW9uIGlzIHJlamVjdGVkLg0K
V2Ugd2lsbCBwcmVwYXJlIGEgZml4IGFuZCBnZXQgYmFjay4NCg0KUmVnYXJkcywNCkFtaXRrdW1h
cg0K

Re: mwifiex problem: incompatible network settings

[Julien Cubizolles]

Amitkumar Karwar <akarwar@marvell.com> writes:


> 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.

Thanks a lot for making my laptop usable again. I'll be happy to test
the fix when it's ready.

RE: mwifiex problem: incompatible network settings

[Amitkumar Karwar]

[-- Attachment #1: Type: text/plain, Size: 747 bytes --]

Hi Julien,

> From: Julien Cubizolles [mailto:j.cubizolles@free.fr]
> Sent: Saturday, November 07, 2015 1:08 PM
> To: Amitkumar Karwar
> Cc: Dan Williams; linux-wireless@vger.kernel.org; Nishant Sarmukadam
> Subject: Re: mwifiex problem: incompatible network settings
> 
> Amitkumar Karwar <akarwar@marvell.com> writes:
> 
> 
> > 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.
> 
> Thanks a lot for making my laptop usable again. I'll be happy to test
> the fix when it's ready.


Could you check if attached patch fixes your connection problem with WPA AP?

Regards,
Amitkumar

[-- Attachment #2: 0001-mwifiex-fix-wpa_ie_not_at_beginning.patch --]
[-- Type: application/octet-stream, Size: 4164 bytes --]

From e2e75b9f2f3035b0e5b4d896e45adc58c12c20a9 Mon Sep 17 00:00:00 2001
From: chunfan chen <jeffc@marvell.com>
Date: Wed, 25 Nov 2015 21:21:02 +0800
Subject: [PATCH] mwifiex: modify parsing logic for IE buffer from cfg80211

This patch modify logic to parse IE buffer from cfg80211 and
fix the following issue.
WPA IE can not be found if it is not at the beginning of IE buffer
received from cfg80211.

Signed-off-by: chunfan chen <jeffc@marvell.com>
---
 drivers/net/wireless/mwifiex/sta_ioctl.c |   75 +++++++++++++++++++++---------
 1 file changed, 53 insertions(+), 22 deletions(-)

diff --git a/drivers/net/wireless/mwifiex/sta_ioctl.c b/drivers/net/wireless/mwifiex/sta_ioctl.c
index a6c8a4f..3ffe8f9 100644
--- a/drivers/net/wireless/mwifiex/sta_ioctl.c
+++ b/drivers/net/wireless/mwifiex/sta_ioctl.c
@@ -1293,6 +1293,8 @@ mwifiex_set_gen_ie_helper(struct mwifiex_private *priv, u8 *ie_data_ptr,
 	struct ieee_types_vendor_header *pvendor_ie;
 	const u8 wpa_oui[] = { 0x00, 0x50, 0xf2, 0x01 };
 	const u8 wps_oui[] = { 0x00, 0x50, 0xf2, 0x04 };
+	u16 unparsed_len = ie_len;
+	int find_wpa_ie = 0;
 
 	/* If the passed length is zero, reset the buffer */
 	if (!ie_len) {
@@ -1304,40 +1306,69 @@ mwifiex_set_gen_ie_helper(struct mwifiex_private *priv, u8 *ie_data_ptr,
 		return -1;
 	}
 	pvendor_ie = (struct ieee_types_vendor_header *) ie_data_ptr;
-	/* Test to see if it is a WPA IE, if not, then it is a gen IE */
-	if (((pvendor_ie->element_id == WLAN_EID_VENDOR_SPECIFIC) &&
-	     (!memcmp(pvendor_ie->oui, wpa_oui, sizeof(wpa_oui)))) ||
-	    (pvendor_ie->element_id == WLAN_EID_RSN)) {
 
-		/* IE is a WPA/WPA2 IE so call set_wpa function */
-		ret = mwifiex_set_wpa_ie_helper(priv, ie_data_ptr, ie_len);
-		priv->wps.session_enable = false;
+	while (pvendor_ie) {
+		if (pvendor_ie->element_id == WLAN_EID_VENDOR_SPECIFIC) {
+			/* Test to see if it is a WPA IE, if not, then it is a
+			 * gen IE
+			 */
+			if (!memcmp(pvendor_ie->oui, wpa_oui,
+				    sizeof(wpa_oui))) {
+				find_wpa_ie = 1;
+				break;
+			}
 
-		return ret;
-	} else if (pvendor_ie->element_id == WLAN_EID_BSS_AC_ACCESS_DELAY) {
+			/* Test to see if it is a WPS IE, if so, enable
+			 * wps session flag
+			 */
+			if (!memcmp(pvendor_ie->oui, wps_oui,
+				    sizeof(wps_oui))) {
+				priv->wps.session_enable = true;
+				mwifiex_dbg(priv->adapter, MSG,
+					    "info: WPS Session Enabled.\n");
+				ret = mwifiex_set_wps_ie(priv,
+							 (u8 *)pvendor_ie,
+							 unparsed_len);
+			}
+		}
+
+		if (pvendor_ie->element_id == WLAN_EID_RSN) {
+			find_wpa_ie = 1;
+			break;
+		}
+
+		if (pvendor_ie->element_id == WLAN_EID_BSS_AC_ACCESS_DELAY) {
 		/* IE is a WAPI IE so call set_wapi function */
-		ret = mwifiex_set_wapi_ie(priv, ie_data_ptr, ie_len);
+			ret = mwifiex_set_wapi_ie(priv, (u8 *)pvendor_ie,
+						  unparsed_len);
+			return ret;
+		}
+
+		unparsed_len -= (pvendor_ie->len +
+				 sizeof(struct ieee_types_header));
+
+		if (unparsed_len <= sizeof(struct ieee_types_header))
+			pvendor_ie = NULL;
+		else
+			pvendor_ie = (struct ieee_types_vendor_header *)
+				(((u8 *)pvendor_ie) + pvendor_ie->len +
+				 sizeof(struct ieee_types_header));
+	}
 
+	if (find_wpa_ie) {
+		/* IE is a WPA/WPA2 IE so call set_wpa function */
+		ret = mwifiex_set_wpa_ie_helper(priv, (u8 *)pvendor_ie,
+						unparsed_len);
+		priv->wps.session_enable = false;
 		return ret;
 	}
+
 	/*
 	 * Verify that the passed length is not larger than the
 	 * available space remaining in the buffer
 	 */
 	if (ie_len < (sizeof(priv->gen_ie_buf) - priv->gen_ie_buf_len)) {
 
-		/* Test to see if it is a WPS IE, if so, enable
-		 * wps session flag
-		 */
-		pvendor_ie = (struct ieee_types_vendor_header *) ie_data_ptr;
-		if ((pvendor_ie->element_id == WLAN_EID_VENDOR_SPECIFIC) &&
-		    (!memcmp(pvendor_ie->oui, wps_oui, sizeof(wps_oui)))) {
-			priv->wps.session_enable = true;
-			mwifiex_dbg(priv->adapter, INFO,
-				    "info: WPS Session Enabled.\n");
-			ret = mwifiex_set_wps_ie(priv, ie_data_ptr, ie_len);
-		}
-
 		/* Append the passed data to the end of the
 		   genIeBuffer */
 		memcpy(priv->gen_ie_buf + priv->gen_ie_buf_len, ie_data_ptr,
-- 
1.7.9.5

Re: mwifiex problem: incompatible network settings

[Julien Cubizolles]

Amitkumar Karwar <akarwar@marvell.com> writes:


> Could you check if attached patch fixes your connection problem with WPA AP?

It seems ok so far. I have set my home router back from WPA2 to WPA and
I can successfully connect. I'll let you know if I experience some
problems with it.

Thanks for your help.

Regards,

Julien.

RE: mwifiex problem: incompatible network settings

[Amitkumar Karwar]

Hi Julien,

> From: Julien Cubizolles [mailto:j.cubizolles@free.fr]
> Sent: Tuesday, December 01, 2015 4:05 PM
> To: Amitkumar Karwar
> Cc: Dan Williams; linux-wireless@vger.kernel.org; Nishant Sarmukadam;
> Jeff CF Chen
> Subject: Re: mwifiex problem: incompatible network settings
> 
> Amitkumar Karwar <akarwar@marvell.com> writes:
> 
> 
> > Could you check if attached patch fixes your connection problem with
> WPA AP?
> 
> It seems ok so far. I have set my home router back from WPA2 to WPA and
> I can successfully connect. I'll let you know if I experience some
> problems with it.
> 

Thanks for confirmation.

Regards,
Amitkumar

Re: mwifiex problem: incompatible network settings

[Ujjal Roy]

Hi Amit/Julien,

On Thu, Oct 29, 2015 at 5:57 PM, Amitkumar Karwar <akarwar@marvell.com> wrote:
>
> Hi Julien,
>
> > From: Julien Cubizolles [mailto:j.cubizolles@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 <dcbw@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.
> 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?
>
> Btw, do you see the problem if AP is configured in WPA2 security mode?
>

You could check it by disabling the NetworkManager and connect using
wpa_supplicant manually. Sometimes NetworkManager does some problem
which is solved by disabling the NetworkManager.

Thanks,
UjjaL

RE: mwifiex problem: incompatible network settings

[Amitkumar Karwar]

PiBGcm9tOiBsaW51eC13aXJlbGVzcy1vd25lckB2Z2VyLmtlcm5lbC5vcmcgW21haWx0bzpsaW51
eC13aXJlbGVzcy0NCj4gb3duZXJAdmdlci5rZXJuZWwub3JnXSBPbiBCZWhhbGYgT2YgVWpqYWwg
Um95DQo+IFNlbnQ6IFRodXJzZGF5LCBPY3RvYmVyIDI5LCAyMDE1IDc6NTkgUE0NCj4gVG86IEFt
aXRrdW1hciBLYXJ3YXINCj4gQ2M6IEp1bGllbiBDdWJpem9sbGVzOyBEYW4gV2lsbGlhbXM7IGxp
bnV4LXdpcmVsZXNzQHZnZXIua2VybmVsLm9yZzsNCj4gTmlzaGFudCBTYXJtdWthZGFtDQo+IFN1
YmplY3Q6IFJlOiBtd2lmaWV4IHByb2JsZW06IGluY29tcGF0aWJsZSBuZXR3b3JrIHNldHRpbmdz
DQo+IA0KPiBIaSBBbWl0L0p1bGllbiwNCj4gDQo+IE9uIFRodSwgT2N0IDI5LCAyMDE1IGF0IDU6
NTcgUE0sIEFtaXRrdW1hciBLYXJ3YXIgPGFrYXJ3YXJAbWFydmVsbC5jb20+DQo+IHdyb3RlOg0K
PiA+DQo+ID4gSGkgSnVsaWVuLA0KPiA+DQo+ID4gPiBGcm9tOiBKdWxpZW4gQ3ViaXpvbGxlcyBb
bWFpbHRvOmouY3ViaXpvbGxlc0BmcmVlLmZyXQ0KPiA+ID4gU2VudDogVGh1cnNkYXksIE9jdG9i
ZXIgMjksIDIwMTUgMzowOSBBTQ0KPiA+ID4gVG86IERhbiBXaWxsaWFtcw0KPiA+ID4gQ2M6IEFt
aXRrdW1hciBLYXJ3YXI7IGxpbnV4LXdpcmVsZXNzQHZnZXIua2VybmVsLm9yZw0KPiA+ID4gU3Vi
amVjdDogUmU6IG13aWZpZXggcHJvYmxlbTogaW5jb21wYXRpYmxlIG5ldHdvcmsgc2V0dGluZ3MN
Cj4gPiA+DQo+ID4gPiBEYW4gV2lsbGlhbXMgPGRjYndAcmVkaGF0LmNvbT4gd3JpdGVzOg0KPiA+
ID4NCj4gPiA+ID4gSGUgYWN0dWFsbHkgbWVhbnQgdGhlIHdwYV9zdXBwbGljYW50IGNvbmZpZ3Vy
YXRpb24gZmlsZSwgbm90IHRoZQ0KPiA+ID4gPiBzdXBwbGljYW50J3MgZGJ1cyBjb25maWcgZmls
ZS4gIEJ1dCB3aGVuIGRyaXZlbiBieSBOZXR3b3JrTWFuYWdlciwNCj4gPiA+ID4gdGhlcmUgaXMg
bm8gc3VwcGxpY2FudCBjb25maWd1cmF0aW9uIGZpbGUuDQo+ID4gPg0KPiA+ID4gU29ycnkgYWJv
dXQgdGhhdC4NCj4gPiA+DQo+ID4gPiA+IEluc3RlYWQsIHlvdSBjYW4gZmluZCBvdXQgd2hhdCBj
b25maWcgTk0gaXMgcHVzaGluZyB0byB0aGUNCj4gPiA+ID4gc3VwcGxpY2FudCBieSBjaGVja2lu
ZyB0aGUgTmV0d29ya01hbmFnZXIgbG9ncywgd2hlcmUgTk0gd2lsbCBsb2cNCj4gbGluZXMgbGlr
ZToNCj4gPiA+DQo+ID4gPiBIZXJlIGFyZSB0aGUgcmVsZXZhbnQgZW50cmllcyBmcm9tIHRoZSBz
eXNsb2cgZmlsZToNCj4gPiA+DQo+ID4gPiBJIGluY2x1ZGVkIHRoZSBmYWlsZWQgYXR0ZW1wdCB0
byBjb25uZWN0IHRvIHRoZSBXUEEgcHJvdGVjdGVkDQo+ID4gPiBuZXR3b3JrIG5hbWVkICJzb3V0
aGNlbnRyYWwiIGFuZCB0aGUgc3VjY2Vzc2Z1bCBvbmUgdG8gYSBub24NCj4gPiA+IHByb3RlY3Rl
ZCBvbmUgbmFtZWQgIkZyZWVXaWZpIi4NCj4gPiA+DQo+ID4NCj4gPiBUaGFua3MgZm9yIHRoZSBs
b2dzLiBJIGNvbXBhcmVkIHlvdXIgbmV0d29yayBtYW5hZ2VyIGxvZyB3aXRoIHRoZSBvbmUNCj4g
b24gbXkgc2V0dXAuIEJvdGggYXJlIHNhbWUuIEJhc2ljYWxseSBuZXR3b3JrIG1hbmFnZXIgbG9n
IGRvZXNuJ3Qgc2hvdw0KPiBzZWN1cml0eSBpbmZvIChXUEEvV1BBMiwgZW5jcnlwdGlvbiBtb2Rl
IGV0YykuIFNvIHdlIGNhbid0IHJlbHkgb24gdGhhdC4NCj4gPiBJIGNoZWNrZWQgeW91ciBrZXJu
ZWwgbG9nIHNoYXJlZCBpbiBwcmV2aW91cyBlbWFpbC4gSXQncyBpbmNvbXBsZXRlLg0KPiBJdCBk
aWRuJ3QgaW5jbHVkZSBpbmZvcm1hdGlvbiB3aGVuIGNvbm5lY3Rpb24gd2FzIGFjdHVhbGx5IGF0
dGVtcHRlZC4NCj4gUHJvYmFibHkgeW91IGNhbiBydW4gImRtZXNnIC1jID4+IGRtZXNnLmxvZyIg
aW4gbG9vcCB3aXRoIHNvbWUgZGVsYXkgdG8NCj4gY2FwdHVyZSBjb21wbGV0ZSBpbmZvLiBPdGhl
cndpc2Ugc2hhcmluZyAiL3Zhci9sb2cvbWVzc2FnZXMiIGlzIGFsc28gYW4NCj4gb3B0aW9uLg0K
PiA+IEkgaGF2ZSBjcmVhdGVkIGEgZHJpdmVyIGRlYnVnIHBhdGNoKGF0dGFjaGVkKS4gQ291bGQg
eW91IHBsZWFzZSBhcHBseQ0KPiBpdCBhbmQgc2hhcmUgY29tcGxldGUgZG1lc2cgbG9nPw0KPiA+
DQo+ID4gQnR3LCBkbyB5b3Ugc2VlIHRoZSBwcm9ibGVtIGlmIEFQIGlzIGNvbmZpZ3VyZWQgaW4g
V1BBMiBzZWN1cml0eSBtb2RlPw0KPiA+DQo+IA0KPiBZb3UgY291bGQgY2hlY2sgaXQgYnkgZGlz
YWJsaW5nIHRoZSBOZXR3b3JrTWFuYWdlciBhbmQgY29ubmVjdCB1c2luZw0KPiB3cGFfc3VwcGxp
Y2FudCBtYW51YWxseS4gU29tZXRpbWVzIE5ldHdvcmtNYW5hZ2VyIGRvZXMgc29tZSBwcm9ibGVt
DQo+IHdoaWNoIGlzIHNvbHZlZCBieSBkaXNhYmxpbmcgdGhlIE5ldHdvcmtNYW5hZ2VyLg0KPiAN
Cg0KTWFrZXMgc2Vuc2UuIFRoaXMgd2lsbCBuYXJyb3cgZG93biB0aGUgaXNzdWUgZnVydGhlci4N
Ckp1bGllbiwgbGV0IG1lIGtub3cgaWYgYW55IGhlbHAgaXMgbmVlZGVkIGZvciB0aGlzLg0KDQpS
ZWdhcmRzLA0KQW1pdGt1bWFyDQo=