Re: MAC address randomization prevents connecting to some wifi AP

On Sun, 2017-05-07 at 16:18 +0200, Julien Cubizolles wrote:
Thomas Haller <thaller redhat com> writes:

From the logfile it's not clear why it would fail. There is also no
<warn> message about NM being unable to change the MAC address --
I would expect to see when the driver cannot change the MAC
But then it's unclear why you say "wifi.scan-rand-mac-address=no"
the issue.

You'd have to enable level=TRACE logging , see

I enabled logging and now have a 3000+ lines file and I don't know
parts are relevant. It's too big for paste.bin so please find it
as a gzipped attachment.


The logfile shows that you didn't disable MAC address randomization
during activation. Ok, that is helpful to see that NM is able to change
the MAC address. So, if it's related to MAC address randomization, it's
either a supplicant or a driver bug.

-- note, your AP might be configured to filter by MAC address. But
since you configured cloned-mac-address=permanent, that doesn't seem to
be problem either. "wifi.scan-rand-mac-address" only matters while
scanning. That should not matter while associating (where "wifi.cloned-
mac-address" comes into play).

From the logfile it is not clear what the problem is. It doesn't seem
to be related to changing the MAC address (as the original email
claims). But even if that would be the case, it would be easy to rule
out by configuring NM not to ever change the MAC address. Since you
apparently tried to do that (without fixing your issue), it seems that
MAC address randomization is the problem.

I would still suggest you disable MAC address randomization to rule
that out and dig more.

Look at the logfiles from supplicant
 ( ).


Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]