Turn off WiFi MAC address randomisation

[shawaj]

From here
https://discord.com/channels/404106811252408320/796070988118360094/854134999880171550

Seems like a NetworkManager bug or configuration error perhaps?

Seems similar to...https://www.raspberrypi.org/forums/viewtopic.php?t=196348&start=25

To disable the MAC address randomization create the file
/etc/NetworkManager/conf.d/100-disable-wifi-mac-randomization.conf

with the content

[connection]
wifi.mac-address-randomization=1
 
[device]
wifi.scan-rand-mac-address=no

[shawaj]

This article suggests it should actually be:

wifi.cloned-mac-address=permanent

Confirmed here that the old way is deprecated...
https://developer.gnome.org/NetworkManager/stable/NetworkManager.conf.html#id-1.2.5.11

[warturtle99]

My miner is constantly changing MAC Addresses every time I pug it in. I am not sure what you mean by, create a file? Do I create it on the miner? Do I plug the miner into my PC?

[warturtle99]

See attached image. As you can see, every time I powered it on or restart it the miner gets a new mac address. How do I stop this?

[LTDenver]

Same. New wifi MAC address at each power up. Router thinks it's a new device each time, thus port forwarding to avoid relay needs to be reestablished each time.

[ryanteck]

I believe it's possibly because the adaptors don't have a MAC address programmed in @shawaj rather than further randomisation. However I'll try and implement it.

But at the same time it depends on if I can add this file in the correct place seeing how it's most likely required on the Host OS which is under Balena's control and not ours.

[warturtle99]

It would have to be a setting in the miner to keep it the same MAC address. As seen in the attached photo, for windows 10, there is a setting in the Wifi properties that can make it so that my PC always has the same MAC address or a different MAC address.

[shawaj]

@warturtle99 @LTDenver this isn't something you can adjust yourself on the miner. We will need to implement it directly on our side

[LTDenver]

Understood,. Thanks for looking into this. You guys are great!

[shawaj]

@ryanteck I think this is possibly related to #57 and the FF:FF WiFi issue. Seems to be all 3 issues on any device that has this issue? (Check out cool-haze for example)