![]() ![]() After that I needed to clear the entry on the DHCP server leases table and reboot the linux server. This config forces linux to use the hardware MAC. The fix I found was to edit the /etc/dhcp/nf file on the linux server and add this line ( If you try to create a DHCP reservation for a linux machine's NIC, the DHCP admin console will not recognize the extra long MAC. This pic below shows the issue as it appears in Win DHCP server. In my research it's considered the DHCP client ID. ![]() Instead it adds many more characters and creates an extremely long string which appears to contain part of the MAC address. The default installation is using this a configuration whereby the dhcp-client-identifier is not using the hardware MAC address of the NIC. ![]() The issue being that newer Linux is using NetPlan to manage networking functionality and I'm not sure if this is a bug or intended. I was searching for the root cause and found a different answer which I believe may be a better solution. ) however the "fix" mentioned there may not address the root cause, it's a workaround. Weird MAC Address on an Ubuntu VM on ESXi I saw another closed thread on this topic ( ![]()
0 Comments
Leave a Reply. |