Re: Troubleshooting NM 1.4.0 (was 'How to activate...randomization?')

[Chris Laprise <tasket openmailbox org>]

On 08/31/2016 01:16 PM, Thomas Haller wrote:
> On Wed, 2016-08-31 at 12:07 -0400, Chris Laprise wrote:
> > I am trying out the new NM in Debian testing by installing the
> > network-manager 1.4.0-3 and network-manager-gnome 1.4.0-2 versions
> > from
> > unstable.
> >
> >
> > NM 1.4 shows up in the systray, but won't display any access points.
> > It
> > does seem to be trying to manage the wifi device, as its MAC address
> > now
> > changes to a random number; I can see this with ifconfig.
> >
> >
> > NM 1.2.4 had been working fine before the upgrade.
> >
> >
> > Any troubleshooting suggestions
> Hi,
>
>
> could be https://bugzilla.gnome.org/show_bug.cgi?id=770456
> or https://bugzilla.gnome.org/show_bug.cgi?id=770504
>
> please send the logfile with level=TRACE. Thanks
>
> Thomas

Hi Thomas,

The patches appear to be working, as the new 1.4.2-1 release that landed 
in Debian testing is able to randomize both scanning and connections now.

However, it doesn't adhere to what is shown on the nm-settings man page. 
The assigned-mac-address setting is described as superceding the 
deprecated cloned-mac-address. But NM will only randomize during 
connections if cloned-mac-address is used.

wifi.assigned-mac-address=random

...has no effect, but

wifi.cloned-mac-address=random

...does work.

Chris