Actions
Feature #8518
closedAllow using system-generated IAID/DUID for all DHCPv4
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Start date:
2017-07-20
Due date:
% Done:
100%
Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:
Description
By default, for an IPv4 interface that is not in an IP network multipathing (IPMP) group, that is not IP over InfiniBand (IPoIB), and that is not a logical interface, the DHCP agent will forgo sending a client identifier unless CLIENT_ID is defined.
It would be useful to add a setting to allow dhcpagent to use a system-managed, RFC 3315-style (i.e., DHCPv6-style) binding identifier as documented in RFC 4361, "Node-specific Client Identifiers for DHCPv4," for all IPv4 interfaces (unless CLIENT_ID is defined).
Updated by Electric Monk over 4 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
git commit b31320a79e2054c6739b5229259dbf98f3afc547
commit b31320a79e2054c6739b5229259dbf98f3afc547 Author: Chris Fraire <cfraire@me.com> Date: 2017-09-12T12:42:21.000Z 7388 Support -h <hostname> for ipadm DHCP 8517 Add ipadm and nwam options to allow designating a DHCP address as the primary interface 8518 Allow using system-generated IAID/DUID for all DHCPv4 8519 Add ns_name_pton2 to libresolv2 mapfile Reviewed by: Dan McDonald <danmcd@joyent.com> Reviewed by: Toomas Soome <tsoome@me.com> Reviewed by: Peter Tribble <peter.tribble@gmail.com> Approved by: Gordon Ross <gwr@nexenta.com>
Actions