Planning IPv6 Address Assignment

Understanding how IPv6 addresses are assigned to hosts manually and dynamically on your enterprise network.

Notice: This blog post was originally published on Men&Mice before its acquisition by BlueCat.

The content reflects the expertise and perspectives of the Men&Mice team at the time of writing. While some references may be outdated, the insights remain valuable. For the latest updates and solutions, explore the rest of our blog

Key Takeaways
  • Manual IPv6 address assignment closely mirrors IPv4 static configuration but typically uses a /64 subnet prefix and always requires explicit prefix length specification.
  • SLAAC relies on Router Advertisements via Neighbor Discovery Protocol for the network prefix, with hosts autonomously generating their interface identifiers.
  • Unix/Linux/Mac hosts commonly derive SLAAC interface identifiers from their MAC address using the Modified EUI-64 format, expanding a 48-bit MAC to a 64-bit identifier.
  • SLAAC simplifies automatic IPv6 address configuration but lacks centralized visibility and control compared to DHCP-based approaches.
  • Stateless DHCPv6 uses SLAAC for address assignment while a DHCPv6 server supplies only additional options such as DNS servers, domain name, and lease parameters.
  • Stateful DHCPv6 disables SLAAC via Router Advertisement flags and delegates full IPv6 address and option assignment to DHCPv6 servers, similar to IPv4 DHCP behavior.

Dynamic allocation of an IPv6 address is a bit different than in IPv4. We’ll go over some of the available methods of address assignment via manual, SLAAC, and DHCPv6 to help you plan your IPv6 migration and the best method for your networks.

Manual

Let’s start off with what’s most familiar to server admins, which is the manual assignment of an IP address, in this case an IPv6 address. You’ll use this method if you’re not using DHCP reservations to assign permanent IP addresses likely to servers on your network.

This is very similar to IPv4. On a Windows machine we just need to go into our network card properties, check the Use the following IPv6 address radio button, and type in the address, subnet prefix length, and default gateway. Typically, with IPv6 addressing you’ll have a 64-bit subnet prefix length.

Screenshot of Windows IPv6 Manual Configuration

Notice that the major difference here is that with IPv4 we would generally put in the entire 32-bit IP address as well as the entire 32-bit default gateway IP address. This will be done in a similar way on a Mac GUI, or it may be done on the Mac terminal or Linux/Unix command line always specifying the prefix length.

Stateless Address Auto Configuration (SLAAC)

In the case of SLAAC, which is new with IPv6, a device will be connected to a router (or Layer 3 switch more likely) and that layer 3 device will send out a Router Advertisement with its IPv6 network. This is called Neighbor Discovery Protocol (NDP). In the case of a Windows machine, it will pick its own random interface identifier (or host part of the address). Then add that on to the network address learned from the Router Advertisement.

Regarding a Unix/Linux/Mac machine it’s a similar process, except the host will use its MAC address in the creation of the Modified EUI (Extended Unique Identifier, or host part of the address) to create a unique IPv6 address. So, it will receive the network address from the router and then take the 48-bit MAC and modify it so that it becomes 64-bits. The way this is done is by breaking the MAC address in half and then adding an FF:FE in the middle. So if the MAC were 70:CF:49:B3:F2:0D it would become 00:CF:49:FF:FE:B3:F2:0D.

Then it will take the first 8 bits, in the case 00, and convert the seventh bit into the opposite of what it is currently. For 0000 0000, the seventh bit would change to a 1. Now we have 0000 0010, which becomes 02:CF:49:FF:FE:B3:F2:0d ultimately in hex.

A quick recap of the math for creating a Modified EUI:

Creating a Modified EUI in Mac/Linux/Unix

SLAAC is probably the simplest way to configure automatic IP addressing, but doesn’t give us all the benefits of DHCP, the biggest being centralized visibility and management. Also since many companies are still using IPv4 along with IPv6 it adds yet another layer of management complexity.

DHCPv6

DHCP gives centralized control for enterprise network management. There are two ways to use DHCP with IPv6 address allocation: Stateless and Stateful.

Stateless:

DHCPv6 (Stateless) still uses SLAAC in the same way described above. However, it will change a flag when sending the Router Advertisement for the client to check with the DHCP server for configuration options. So, you can specify things like which DNS server to go to, the domain name, and lease time. This is referred to as stateless because the DHCP server is not in charge of IP configuration, it’s only giving the extra options which are so often used in an enterprise environment for more automated and consistent configuration.

Stateful:

In the case of DHCPv6 (Stateful) the client will still try to get information from a Router Advertisement, but in this case the Router Advertisement will tell it not to use SLAAC at all and will be sent to a DHCP server for both IP configuration as well as the other options discussed above. This is very similar to how DHCP works in IPv4 environments and gives complete control to the DHCP servers.

In both Stateless and Stateful use cases, a DDI solution will be able to gather more information for a contextual view as well as control of DHCP for the entire environment.

For More Information

If you’d like to learn more about IPv6 and DCHPv6 check out our Fundamentals on-demand webinar.

Related content

Three armored figures walking toward a futuristic Las Vegas skyline with pyramids, glowing orb, and "Welcome to Fabulous Las

Your journey to intelligent NetOps begins at Cisco Live

Visit BlueCat’s booth or book a meeting now to learn more about how our solutions can help you build a network that supports constant change.

Read more
Stacked colorful wooden directional arrows on a post by a calm seaside with distant hills and blue sky

Replace BIND and ISC with Micetro DNS/DHCP Server (MDDS)

Tired of patching and manually configuring BIND DNS and ISC DHCP? Discover how Micetro MDDS appliances can replace them for modern DDI.

Read more
Row of orange industrial robotic arms positioned along an automated conveyor belt in a factory setting

Automate it all in Integrity with REST v2 API-first DDI management

Discover API-first DDI with Integrity X by using REST v2 to automate DNS, DHCP, and IPAM for scalable, secure network operations.

Read more
Three colleagues at monitors collaborating, overlaid with network, analytics, cloud, and gear icons.

Agentic AI adoption in network observability propels NetOps teams

Network observability is crucial for today’s networks and even more capable with agentic AI, according to new Omdia and BlueCat research.

Read more

⏳ Cisco Live is almost here. Put BlueCat on your agenda for smarter, more secure networks.