This is something I just came across myself. While deploying an Ubuntu Linux VM the DHCP reservation did not work. This was mixed up with a Windows 2016 DHCP server.
After looking at the wrong DHCP lease I quickly saw an extremely long MAC address and figured that the Linux VM used some kind of randomization for the interface.
IFCONFIG on the system showed the correct hardware MAC address.
It took me a few minutes of research and testing till I found the root cause and rather simple solution.
Linux replaced their NIC handling on many distributions with a newer system called NETPLAN.
I read that a 2019 Windows DHCP would likely handle this correctly, did not have time to test this out. But the following worked for me:
- List the contents /etc/netplan
- ls /etc/netplan
- there should be a file ending in .yaml
- Edit this .yaml file
- sudo nano /etc/netplan/<filename>.yaml
The file is structured like this:
1 2 3 4 5 6 7 8 | network: renderer: networkd version: 2 ethernets: nicdevicename: dhcp4: true dhcp-identifier: mac |
Under your NICDEVICENAME add the line dhcp-identifier: mac and save (CNTRL+O) and exit (CNTRL+X) the file.
Now you can either try to apply the netplan config via sudo netplan apply or simply reboot.
This should solve the issue.
