The cause of the problem is that sometimes the built-in network config ( for example of Ubuntu 18.04+) not uses the NIC Mac address as the default id for DHCP requests.
netplan
dhcp4: true
dhcp-identifier: mac
Set to ‘mac’ to pass that setting over to systemd-networkd to use the device’s MAC address as a unique identifier rather than a RFC4361-compliant Client ID. This has no effect when NetworkManager is used as a renderer.
systemd.network
The DHCPv4 client identifier to use. Takes one of "mac", "duid" or "duid-only". If set to "mac", the MAC address of the link is used.
The /etc/machine-id file contains the unique machine ID of the local system that is set during installation or boot.
The machine ID does not change based on local or network configuration or when hardware is replaced.
detektiven/vagans/common/vmHelpers.bash
Line 154 in 2b64f83
The cause of the problem is that sometimes the built-in network config ( for example of Ubuntu 18.04+) not uses the NIC Mac address as the default id for DHCP requests.
netplan
Set to ‘mac’ to pass that setting over to systemd-networkd to use the device’s MAC address as a unique identifier rather than a RFC4361-compliant Client ID. This has no effect when NetworkManager is used as a renderer.
systemd.network
The DHCPv4 client identifier to use. Takes one of "mac", "duid" or "duid-only". If set to "mac", the MAC address of the link is used.
The
/etc/machine-idfile contains the unique machine ID of the local system that is set during installation or boot.The machine ID does not change based on local or network configuration or when hardware is replaced.