linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Julien Cubizolles <j.cubizolles@free.fr>
Cc: Amitkumar Karwar <akarwar@marvell.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: mwifiex problem: incompatible network settings
Date: Wed, 28 Oct 2015 09:50:53 -0500	[thread overview]
Message-ID: <1446043853.24757.51.camel@redhat.com> (raw)
In-Reply-To: <87a8r4ugth.fsf@free.fr>

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



  reply	other threads:[~2015-10-28 14:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26 15:51 mwifiex problem: incompatible network settings Julien Cubizolles
2015-10-26 16:10 ` Dan Williams
2015-10-26 21:50   ` Julien Cubizolles
2015-10-27 15:11     ` Dan Williams
2015-10-27 18:55     ` Amitkumar Karwar
2015-10-27 21:44       ` Julien Cubizolles
2015-10-28 14:50         ` Dan Williams [this message]
2015-10-28 21:38           ` Julien Cubizolles
2015-10-29 12:27             ` Amitkumar Karwar
2015-10-29 15:16               ` Dan Williams
2015-10-30 10:34                 ` Amitkumar Karwar
2015-11-04 22:04               ` Julien Cubizolles
2015-11-05  8:59                 ` Amitkumar Karwar
2015-11-07  7:38                   ` Julien Cubizolles
2015-11-25 14:22                     ` Amitkumar Karwar
2015-12-01 10:35                       ` Julien Cubizolles
2015-12-01 10:36                         ` Amitkumar Karwar
  -- strict thread matches above, loose matches on Subject: below --
2015-10-29 14:29 Ujjal Roy
2015-10-30 10:27 ` Amitkumar Karwar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1446043853.24757.51.camel@redhat.com \
    --to=dcbw@redhat.com \
    --cc=akarwar@marvell.com \
    --cc=j.cubizolles@free.fr \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).