Comment 4 for bug 1738998
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Using the DUID as a client identifier for DHCP is the best option in most cases; that won't change. The specifics of this are well described in RFC 4361.
However, I do understand the requirement for making it possible to use other options, this is why the bug is Triaged. Some installations will not work with the DUID, and we should provide a way for people to work around that.
@Mark, I think the issue here is that the VMs were all created via cloning, in which case /etc/machine-id would be the same, which will explain why the DUID is the same on all the systems created. This should not be an issue where VMs are installed independently. You can remove the file to have it re-created at reboot, or use 'systemd-