From: Julien Cubizolles <j.cubizolles@free.fr>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: mwifiex won't connect to WPA2 anymore
Date: Sat, 06 May 2017 10:41:51 +0200 [thread overview]
Message-ID: <87mvaq4bsg.fsf@free.fr> (raw)
In-Reply-To: <1493948347.26081.1.camel@redhat.com> (Dan Williams's message of "Thu, 04 May 2017 20:39:07 -0500")
Dan Williams <dcbw@redhat.com> writes:
> Just to test, could you add:
>
> auth_alg=OPEN
> key_mgmt=WPA-PSK
> scan_ssid=1
>
> to the block and retry with the supplicant? I don't know why those
> would make a difference but they might.
They don't: wpa_supplicant still connects with these settings.
next prev parent reply other threads:[~2017-05-06 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 16:09 mwifiex won't connect to WPA2 anymore Julien Cubizolles
2017-05-03 20:33 ` Julien Cubizolles
2017-05-03 20:43 ` Dan Williams
2017-05-04 21:27 ` Julien Cubizolles
2017-05-05 1:39 ` Dan Williams
2017-05-06 8:41 ` Julien Cubizolles [this message]
2017-05-06 15:50 ` Dan Williams
2017-05-06 20:22 ` Julien Cubizolles
2017-05-08 14:08 ` Dan Williams
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=87mvaq4bsg.fsf@free.fr \
--to=j.cubizolles@free.fr \
--cc=dcbw@redhat.com \
--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).