This is for example useful so that you get the same IP address from DHCP, which might not be the case with “random”. However, each connection generates a different address. This way every time the connection activates, the same address is generated. In a way it is similar to “random”, but instead it generates a stable, hashed value. The “stable” method warrants more explanation. In that case, I would suggest to use nmcli to configure the per-connection settings: $ nmcli connection show It is likely that your favorite NetworkManager client does not expose these options in the UI. On the other hand, in nmcli, libnm.so, and keyfile-format the properties are indeed called “cloned-mac-address”. That is why on D-Bus there are new fields “ethernet.assigned-mac-address” and “wifi.assigned-mac-address” instead. Note that in the D-Bus API, the “cloned-mac-address” field is not a string and thus could not be extended in a backward compatible way. Update-: with 1.6 release and newer, the default value changed from “permanent” to “preserve”. In case no global override exists, NetworkManager falls back to “permanent”, like it did before. NULL/unset: this is the default value which allows fallback to a globally configured default, see below.“stable”: generate a stable, hashed MAC address.“random”: generate a randomized value upon each connect.“preserve”: don’t change the MAC address of the device upon activation.Before 1.4.0, the permanent MAC address was used if the “cloned-mac-address” property was left empty, thus it was the default. ![]()
0 Comments
Leave a Reply. |