When having an old Winsdows 2003 dhcp server, which doesn't understand the dhcp identifier OS'es such as Fedora 29 and Ubuntu 18.04 server sends. Which looks like

10,11/09/18,12:28:17,Assign,192.168.234.30,tst.example.com,525400D19B51,,1918747074,0,,,
11,11/09/18,12:29:15,Renew,192.168.234.30,tst.example,525400D19B51,,1005047232,0,,,

RFC 4361 should be the RFC about this new way to identifying hosts.

When I take a CentOS 7 as dhcp server, which should support this, both Fedora and Ubuntu presents the MAC address, which I did not expect, as one has to add

send dhcp-client-identifier = hardware;

to /etc/dhcp/dhclient.conf disable this new method on Fedora and Ubuntu.

Question

Can someone explain if this new method is just "protocol" and therefore something the Linux admin will never see, if the dhcp server supports this?

In order words, will the DHCP reservations still be based on MAC addresses or this new method?

  • This "new" method is more than a decade old. And I'm not sure we can even predict what will happen when you use an obsolete server with modern clients. Remember that that Windows server was supposed to have been decommissioned years ago. – Michael Hampton Nov 9 at 14:36
  • Yes, this is not about the Windows dhcp server. Here I know it doesn't understand it. The question is about when using a modern dhcpd server on CentOS 7. – Sandra Nov 9 at 14:48

Your Answer

 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.