A couple of related details regarding machine-id induced IP collisions:
The duplicate IP caused by duplicate machine-id will not happen with NetworkManager in Focal and later (NetworkManager versions >1.15) by default due to this change[1]. It is still possible to trigger it by setting `ipv4.dhcp-client-id=duid`.
SystemD is unlikely to follow NetworkManager[2], because doing so would only mask the bigger problem (duplicate machine-id on multiple machines).
Therefore, the duplicate IP symptom is limited to distros using systemd-networkd, however the underlying machine-id issue affects all distros.
A couple of related details regarding machine-id induced IP collisions:
The duplicate IP caused by duplicate machine-id will not happen with NetworkManager in Focal and later (NetworkManager versions >1.15) by default due to this change[1]. It is still possible to trigger it by setting `ipv4.dhcp- client- id=duid` .
SystemD is unlikely to follow NetworkManager[2], because doing so would only mask the bigger problem (duplicate machine-id on multiple machines).
Therefore, the duplicate IP symptom is limited to distros using systemd-networkd, however the underlying machine-id issue affects all distros.
[1] https:/ /gitlab. freedesktop. org/NetworkMana ger/NetworkMana ger/-/commit/ cfd696cc3cf43f5 f510046b7579495 46bcee4cdc /github. com/systemd/ systemd/ issues/ 9609#issuecomme nt-776277655
[2] https:/