Why does "dhclient -6" not work if I haven't already enabled IPv6 on the interface?
- Updated on 17 Jan 2018
- 1 minute to read
IPv6 makes extensive use of the "link-local" address. This address is configured automatically when the interface is brought up. Various IPv6 subprotocols, including Neighbor Discovery Protocol (NDP) and DHCPv6, require and use this address.
The IPv6 link-local address is in the FE80::/64 space (which is within the reserved FE80::/10 network.) Every IPv6-enabled interface will have this address at a minimum. Link-local means just that: it is local to the link (interface or Ethernet segment) only, and it cannot be routed outside that link.
Your operating system (OS) will statelessly autoconfigure the IPv6 link-local address when IPv6 is enabled on the interface. The details of how this is done varies per OS, but the governing standard is RFC 4862, IPv6 Stateless Address Autoconfiguration.
DHCPv6 clients use their IPv6 link-local addresses to communicate with the server. If you have not enabled IPv6 on the interface, there is no link-local address yet, and the client is unable to reach the server.
 See section 1.1 of RFC 3315.
© 2001-2018 Internet Systems Consortium For assistance with problems and questions for which you have not been able to find an answer in our Knowledge Base, we recommend searching our community mailing list archives and/or posting your question there (you will need to register there first for your posts to be accepted). The bind-users and the dhcp-users lists particularly have a long-standing and active membership. ISC relies on the financial support of the community to fund the development of its open source software products. If you would like to support future product evolution and maintenance as well having peace of mind knowing that our team of experts are poised to provide you with individual technical assistance whenever you call upon them, then please consider our Professional Subscription Support services - details can be found on our main website.