On Mon, Aug 22, 2016 at 9:40 AM <vendor@billoblog.com> wrote:
On Mon, 22 Aug 2016, David Timms wrote:

> On 22/08/16 15:38, vendor@billoblog.com wrote:
> ...
>> So, I know I could disconnect and type in a mac address using the gui
>> for network manager, but I'd like to be able to script this.  What am I
>> doing wrong?  How can I get NetworkManager to scarf up a mac address I
>> generate either by editing a config file or by using nmcli?
>
> Maybe try using the GUI to see if it actually works. If it does, work
> out which files get changed and therefore what needs to be changed from
> scripting?
> --
>

Yes, it works using the gui, though it really does change the mac on a
per-connection basis.  Changing the mac for ssid attwifi, for instance
doesn't affect the mac for my home network.

I don't know where these files are to monitor them, but if I did, I'd
stumble through that way.


... but I'd rather make the change at the interface level rather than
the connection level.


I had a similar experience, when I noticed my custom systemd unit to call macchanger on boot stopped having any effect. For now, I'm doing things through the GUI. It looks like the "clone" address in the GUI corresponds to a new MACADDR= line in the ifcfg scripts (Fedora uses ifcfg-rh NM plugin by default). The HWADDR= line still refers to the actual hardware, while the apparently new MACADDR field is the MAC to use for the connection.

Like you, I can't find a way to do this in a per-interface way. It seems it has to be per-connection. This might be related to the new MAC_ADDRESS_RANDOMIZATION field in the ifcfg scripts, also. If a new feature to do randomization during passive hotspot detection has been added, it'd be harder to preserve the override at the interface level, I imagine.