IPv6 address assignment – stateless, stateful, DHCP… oh my!

People don’t like changes. IPv6 could have help to solve a lot of the burden in networks deployed today, which are still mostly based on the original version of the Internet Protocol, aka version 4. But time has come, and even the old tricks like throwing network address translation (NAT) everywhere are not going to help anymore, simply because we are out of IP addresses. It may take some more time, and people will do everything they can to (continue and) delay it, but believe me – there is no other way around – IPv6 is here to replace IPv4. IPv6 is also a critical part of the promise of the cloud and the Internet of Things (IoT). If you want to connect everything to the network, you better plan for massive scale and have enough addresses to use.

One of the trickiest things with IPv6 though is the fact that it’s pretty different from IPv4. While some of the concepts remains the same, there are some fundamental differences between IPv4 and IPv6, and it’s definitely takes some time to get used into some of the IPv6 basics, including the terms being used. Experienced IPv4 engineers will probably need to change their mindset, and as I stated before, people don’t really like changes…

In this post, I want to highlight the address assignment options available with IPv6, which is in my view one of the most fundamental things in IP networking, and where things are pretty different comparing to IPv4. I am going to assume you have some basic background on IPv6, and while I will cover the theory part I will also show the command line interface and demonstrate some of the configuration options, focusing on SLAAC and stateless DHCPv6. I am going to use a simple topology with two Cisco routers directly connected to each other using their GigabitEthernet 1/0 interface. Both routers are running IOS 15.2(4).

 Let the party started

With IPv6 an interface can have multiple prefixes and IP addresses, and unlike IPv4, all of them are primary. All interfaces will have a Link-Local address which is the address used to implement many of the control plane functions. If you don’t manually set the Link-Local address, one will automatically be generated for you. Note that the IPv6 protocol stack will not become operational on an interface until a Link-Local address was assigned or generated and it passed Duplicate Address Detection (DAD) verification. In Cisco IOS, we will first need to enable IPv6 on the router which is done globally using the ipv6 unicast-routing command. We will then enable IPv6 on the interface using the ipv6 enable command:

ipv6 unicast-routing
interface GigabitEthernet1/0
 ipv6 enable

Now IPv6 in enabled on the interface, and we should get a Link-Local address assigned automatically:

show ipv6 interface g1/0 | include link

IPv6 is enabled, link-local address is FE80::C800:51FF:FE2F:1C

IPv6 address assignment options

A little bit of theory as promised. When it comes to IPv6 address assignment there are several options you can use:

  • Static (manual) address assignment – exactly like with IPv4, you can go on and apply the address yourself. I believe this is straight forward and therefore I am not going to demonstrate that.
  • Stateless Address Auto Configuration (SLAAC) – nodes listen for ICMPv6 Router Advertisements (RA) messages periodically sent out by routers on the local link, or requested by the node using an RA solicitation message. They can then create a Global unicast IPv6 address by combining its interface EUI-64 (based on the MAC address on Ethernet interfaces) plus the Link Prefix obtained via the Router Advertisement. This is a unique feature only to IPv6 which provides simple “plug & play” networking. By default, SLAAC does not provide anything to the client outside of an IPv6 address and a default gateway. SLAAC is greatly discussed in RFC 4862.
  • Stateless DHCPv6 – with this option SLAAC is still used to get the IP address, but DHCP is used to obtain “other” configuration options, usually things like DNS, NTP, etc. The advantage here is that the DHCP server is not required to store any dynamic state information about any individual clients. In case of large networks which has huge number of end points attached to it, implementing stateless DHCPv6 will highly reduce the number of DHCPv6 messages that are needed for address state refreshment.
  • Stateful DHCPv6 – functions exactly the same as IPv4 DHCP in which hosts receive both their IPv6 address and additional parameters from the DHCP server. Like DHCP for IPv4, the components of a DHCPv6 infrastructure consist of DHCPv6 clients that request configuration, DHCPv6 servers that provide configuration, and DHCPv6 relay agents that convey messages between clients and servers when clients are on subnets that do not have a DHCPv6 server. You can learn more about DHCP for IPv6 in RFC 3315.

NOTE: The only way to get a default gateway in IPv6 is via a RA message. DHCPv6 does not carry default route information at this time.

Putting it all together

An IPv6 host performs stateless address autoconfiguration (SLAAC) by default and uses a configuration protocol such as DHCPv6 based on the following flags in the Router Advertisement message sent by a neighboring router:

  • Managed Address Configuration Flag, the ‘M’ flag. When set to 1, this flag instructs the host to use a configuration protocol to obtain stateful IPv6 addresses
  • Other Stateful Configuration Flag, the ‘O’ flag. When set to 1, this flag instructs the host to use a configuration protocol to obtain other configuration settings, e.g., DNS, NTP, etc.

Combining the values of the M and O flags can yield the following:

  • Both M and O Flags are set to 0. This combination corresponds to a network without a DHCPv6 infrastructure. Hosts use Router Advertisements for non-link-local addresses and other methods (such as manual configuration) to configure other parameters.
  • Both M and O Flags are set to 1. DHCPv6 is used for both addresses and other configuration settings, aka stateful DHCPv6.

  • The M Flag is set to 0 and the O Flag is set to 1. DHCPv6 is not used to assign addresses, only to assign other configuration settings. Neighboring routers are configured to advertise non-link-local address prefixes from which IPv6 hosts derive stateless addresses. This combination is known as statless DHCPv6.

Examining the configuration


Client configuration:

interface GigabitEthernet1/0
 ipv6 address autoconfig
 ipv6 enable

Server configuration:

interface GigabitEthernet1/0
 ipv6 address 2001:1111:1111::1/64
 ipv6 enable

We can see the server sending the RA message with the prefix that was configured:

ICMPv6-ND: Request to send RA for FE80::C801:51FF:FE2F:1C
ICMPv6-ND: Setup RA from FE80::C801:51FF:FE2F:1C to FF02::1 on GigabitEthernet1/0 
ICMPv6-ND: MTU = 1500
ICMPv6-ND: prefix = 2001:1111:1111::/64 onlink autoconfig 
ICMPv6-ND: 2592000/604800 (valid/preferred)

And the client receiving the message and calculating an address using EUI-64:

ICMPv6-ND: Received RA from FE80::C801:51FF:FE2F:1C on GigabitEthernet1/0 
ICMPv6-ND: Prefix : 2001:1111:1111::ICMPv6-ND: Update on-link prefix 2001:1111:1111::/64 on GiabitEthernet1/0 
IPV6ADDR: Generating IntfID for 'eui64', prefix 2001:1111:1111::/64 
ICMPv6-ND: IPv6 Address Autoconfig 2001:1111:1111:0:C800:51FF:FE2F:1C 

R1#show ipv6 interface brief
GigabitEthernet1/0 [up/up]

Stateless DHCP

Client configuration:

No changes are required on the client side. The client is configured to use SLAAC by setting the “auto-config” option.

interface GigabitEthernet1/0
 ipv6 address autoconfig
 ipv6 enable

Server configuration:

dns-server 2001:1111:1111::10
domain-name test.com
interface GigabitEthernet1/0
 ipv6 address 2001:1111:11111::1/64
 ipv6 enable
 ipv6 nd other-config-flag
 ipv6 dhcp server STATELESS_DHCP

We can see the client keeping the same IP address, but now obtaining DNS settings through DHCP:

IPv6 DHCP: Adding server FE80::C801:51FF:FE2F:1C
IPv6 DHCP: Processing options
IPv6 DHCP: Configuring DNS server 2001:1111:1111::10
IPv6 DHCP: Configuring domain name test.com

16 thoughts on “IPv6 address assignment – stateless, stateful, DHCP… oh my!

  1. Pingback: IPv6 Prefix Delegation – what is it and how does it going to help OpenStack? | The Network Way – Nir Yechiel's blog

  2. v6 is near, repent of your NATs. Yeah right. Every year we hear this and every year it doesn’t happen. As a matter of fact, the easiest segment to convert is the mobile data. There really isn’t any concern over user education or firewall reconfig. And yet most mobile in the US is still v4.
    It doesn’t seem like there is any pressure from address exhausion.

    • Hello Garegin and thanks for your feedback.

      It’s a process, and I honestly feel sorry for any company which did not plan for IPv6 by now. I can confirm that Service Providers and web-scale deployments I have been engaged with are already using IPv6, and IPv6 support is a strict requirement for them.


  3. Pingback: Setting up a dhcp server for ipv6 | Turn on the lights…

  4. In My UTM, For IPv6 Interface IP Assignment selected DHCP from my end and after that I am getting mode 1) Auto 2) Manual

    So in Manual mode again getting 2 option 1) DHCP only & 2) Stateless

    So I selected DHCP only but it is asking for gateway address in DHCP only mode.

    So I am confuse with gateway address why is it required gateway in DHCP only option?

    Can any one reply earliest?

    • Hello,

      I have no experience with UTM. Can you please explain what are you trying to do and what is the topology? Remember that even stateful DHCP still relies on RAs for gateway information, so it could be that you need to set it manually if the device is not capable of learning it dynamically.


  5. Such a nice primer/resource (even in 2017 : ) and kudos for the post. Free copyedit to increase it’s greatness and ensure it’s longevity though… search “Stateful DCHPv6” change to “Stateful DHCPv6”. Continue to rock. (And feel free to delete this comment after too. ; )

    • Hello Jay,

      Thanks for the feedback. Good to hear that you found this post useful, even in 2017 😉

      The typo is fixed now.


  6. Great article!, thanks.

    When implementing IPv6 internally on a Windows Domain network, one thing that’s still not clear to me is how to deal with servers that need to have a static IPv6 address like Domain Controllers, etc. In the IPv4 world you just use addresses that are out of the DHCP scope, or maybe reservations, in order to avoid conflicts. With SLAAC, how do you handle this and avoid conflicts? or do you have to implement stateful DHCPv6 the same way you do with IPv4 for your whole subnet if you are required to assign a couple of static IPv6 addresses?

    Also, about best practices, should you assign IPv6 static addresses to all your servers / network devices (file servers, application servers, print servers, switches, etc.) like with IPv4? or should you only use static when strictly necessary?


    • Hello,

      Thanks for the feedback!

      I am not familiar with an easy way to “reserve” a pool of addresses when using SLAAC. But the beauty of SLAAC is that each node generates the address in a way that is safe enough to not create conflicts to begin with.

      Re: static assignments – yes, I would statically assign IPv6 addresses on key devices/nodes in most cases.


  7. Hi Nir, great article mate!. well done and very informative.. quite clear too!

    Just diving into IPV6 now.

    Trying to cleanup initial IPV6 DHCPV6 on zyxel usg60 and usg40 routers using STATEFUL DHCPV6 with a bunch of IPV6s from H.E. /64 block (global routable and with use with local in-house DNS).

    Works ok.. however ….

    Trying to disable the EUI.64 stuff. Just want a 2001:………/128 for each MacOS, FreeBSD and windows hosts for the AAAA DNS.

    Hard to find any hand holding “step by step” links.

    Any clues lads?

    Hong Kong

  8. I really wanted to do more with IPv6 lately for my homelab; but just couldn’t get my head around some terms and configuration methods. Thank you very much for such a clear post, it was a good read!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s