From: Dan Williams <dcbw@redhat.com>
To: Julien Cubizolles <j.cubizolles@free.fr>
Cc: linux-wireless@vger.kernel.org
Subject: Re: mwifiex won't connect to WPA2 anymore
Date: Mon, 08 May 2017 09:08:24 -0500 [thread overview]
Message-ID: <1494252504.8248.2.camel@redhat.com> (raw)
In-Reply-To: <8737chpwfx.fsf@free.fr>
On Sat, 2017-05-06 at 22:22 +0200, Julien Cubizolles wrote:
> Dan Williams <dcbw@redhat.com> writes:
>
>
> > Ok, at this point the only thing I can think of is the MAC
> > randomization that NM has. Please see:
> >
> > https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
> > networkmanager-1-4-0/
> >
> > and look at the section "Randomization during Wi-Fi scanning" where
> > it
> > says:
> >
> > ----
> > This default behavior can be disabled with a global configuration
> > option in NetworkManager.conf:
> >
> > [device]
> > wifi.scan-rand-mac-address=no
> > ----
> >
> > if you set that, and restart NetworkManager, does that magically
> > make
> > things work?
>
> Yes! It's now working fine, thanks a lot. I have my wifi AP set to
> only
> accept a whitelist of MAC addresses so it makes sense that I can't
> connect if the MAC address is random. I'll disable the randomization
> for
> now on.
Well, ideally you wouldn't have to do this, but we haven't quite
figured out whether it's a bug in the way NM does randomization or
whether the drivers that require this switch (there are a few) are just
broken somehow.
Dan
prev parent reply other threads:[~2017-05-08 14:08 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
2017-05-06 15:50 ` Dan Williams
2017-05-06 20:22 ` Julien Cubizolles
2017-05-08 14:08 ` Dan Williams [this message]
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=1494252504.8248.2.camel@redhat.com \
--to=dcbw@redhat.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).