mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-01-06 22:30:19 +01:00
140ebbbf89
DHCPv6 RFCs require the DUID to be constant over time and to be used as a permanent identifiers of the machine. This precludes using a network interface MAC address since the MAC address may change, and there may be more than one network interface installed. Storing the DUID causes problems when an OS image is cloned between virtual or physical machines because then the saved DUID is no longer unique. To fix all these issues, generate the DUID from the machine's hashed machine-id, which is already a unique identifier of the machine and will always be present because dbus requires it, and NM requires dbus. It is assumed administrators will change the machine-id when cloning an OS image; thus they only have to update one file, not two (machine-id and the stored DUID). Administrators may still override the machine-id-derived DUID by setting a DUID in the default dhclient config file or the interface-specific dhclient config files. dhclient no longer saves a generated DUID to the config files, because the default DUID will always be regenerated from the machine-id on startup and thus always stable. |
||
|---|---|---|
| .. | ||
| tests | ||
| Makefile.am | ||
| nm-dhcp-client.c | ||
| nm-dhcp-client.h | ||
| nm-dhcp-dhclient-utils.c | ||
| nm-dhcp-dhclient-utils.h | ||
| nm-dhcp-dhclient.c | ||
| nm-dhcp-dhclient.h | ||
| nm-dhcp-dhcpcd.c | ||
| nm-dhcp-dhcpcd.h | ||
| nm-dhcp-manager.c | ||
| nm-dhcp-manager.h | ||