8.5.3 Module Quiz - Slaac And Dhcpv6

8.5.3 Module Quiz: SLAAC and DHCPv6

You just finished reading about SLAAC and DHCPv6, and now there's a quiz. Sound familiar? Whether you're taking the CCNA 200-301 exam or just trying to actually understand IPv6 addressing, this is where a lot of people pause and think: *Wait, what was the difference again?

Here's the thing — SLAAC and DHCPv6 aren't just two ways to hand out IP addresses. They're fundamentally different philosophies about how devices should get their network configuration. And if you mix them up on a test, or worse, in real life, things go sideways fast.

Let's cut through the confusion.

What Is SLAAC and DHCPv6?

SLAAC: Stateless Address Autoconfiguration

SLAAC stands for Stateless Address Autoconfiguration. It's how IPv6 devices configure themselves without a DHCP server. No server required. The device basically looks at the router advertisements on the network, grabs the network prefix, combines it with its own interface identifier (usually derived from the MAC address), and boom — it has an IPv6 address.

It's elegant, really. The router announces "Hey, this network is 2001:db8:1234:1::/64," and the host says "Cool, I'll make my address 2001:db8:1234:1:aaaa:bbbb:cccc:dddd." No handshaking, no server, no state tracking.

But here's what most people miss — SLAAC only gives you an IP address and a default route. It doesn't tell you the DNS servers. It doesn't tell you the domain name. It doesn't tell you much of anything beyond "you're on this network Less friction, more output..

DHCPv6: Stateful and Stateless Modes

DHCPv6 is the IPv6 version of DHCP — the protocol you've been using forever in IPv4 networks. But here's where it gets interesting: DHCPv6 has two modes, and this is where the quiz questions love to trip people up.

Stateful DHCPv6 works like classic DHCP. The server keeps track of which addresses are assigned to which clients. It hands out addresses, tracks leases, and manages the pool. Sound familiar? That's because it's basically DHCP for IPv4, just speaking IPv6.

Stateless DHCPv6 is the hybrid approach. The client still uses SLAAC to get its IPv6 address, but it also queries a DHCPv6 server for additional information — like DNS server addresses. Think of it as SLAAC + supplemental configuration.

Why It Matters

The IPv4 Hangover Problem

If you're coming from IPv4, your brain wants to default to "DHCP handles everything." That's not how IPv6 works by default. That said, sLAAC is the native, built-in way for IPv6 devices to configure themselves. DHCPv6 is the optional add-on Which is the point..

This matters because when you're troubleshooting an IPv6 network and devices aren't getting DNS servers, the question isn't "Is DHCP running?" — it's "Is the router advertising the right flags in its router advertisements?"

Real-World Network Design Decisions

Network engineers choose between SLAAC, stateful DHCPv6, and stateless DHCPv6 based on what they need to control. Want maximum simplicity and don't care about tracking individual devices? SLAAC. Need to enforce policies, track devices, or manage address pools carefully? In practice, stateful DHCPv6. Want the simplicity of SLAAC but still need DNS configuration? Stateless DHCPv6.

Get this wrong, and you either have networks that are impossible to manage or networks that are unnecessarily complex.

How It Works

The Router Advertisement Flags

Here's where the magic happens — and where most quiz questions live. Every IPv6 router periodically sends out Router Advertisement (RA) messages. These packets contain two critical flags that tell clients how to behave:

The M Flag (Managed Address Configuration)

When the M flag is set to 1, it means "Hey, there's a DHCPv6 server on this network. Which means you should talk to it to get your address configuration. " This triggers stateful DHCPv6.

When M is 0, clients use SLAAC for address configuration. No DHCPv6 server needed for addresses.

The O Flag (Other Configuration)

When the O flag is set to 1, it means "There's a DHCPv6 server available for other configuration information — like DNS servers." This works whether M is 0 or 1.

When O is 0, clients don't query DHCPv6 for additional info. They're on their own for DNS and domain names.

The Four Combinations

This is where the quiz loves to ask questions. The M and O flags create four scenarios:

M=0, O=0: Pure SLAAC. Devices configure themselves entirely from router advertisements. No DHCPv6 at all.

M=0, O=1: Stateless DHCPv6. Devices use SLAAC for addresses but query DHCPv6 for DNS and other config.

M=1, O=0: Stateful DHCPv6 for addresses only. No additional configuration via DHCPv6.

M=1, O=1: Stateful DHCPv6 for everything. Addresses and additional configuration both come from DHCPv6.

How SLAAC Actually Works

Let's walk through the SLAAC process:

1. A router sends a Router Advertisement with the network prefix and flags.
2. The host generates its interface identifier. In the old days, this was based on the MAC address using EUI-64. Today, privacy extensions (RFC 4941) are preferred, generating random interface IDs that change over time.
3. The host combines the network prefix with its interface identifier to create its IPv6 address.
4. The host performs Duplicate Address Detection (DAD) — it sends a Neighbor Solicitation to make sure no one else is using that address.
5. If no one responds, the address is assigned.

How Stateful DHCPv6 Works

Stateful DHCPv6 follows a familiar pattern if you know IPv4 DHCP:

1. The client sends a Solicit message looking for DHCPv6 servers.
2. Servers respond with Advertise messages.
3. The client sends a Request for addresses and configuration.
4. The server responds with a Reply containing the assigned addresses and config.
5. The client can Renew (RENEW) or Rebind (REBIND) as the lease expires.

How Stateless DHCPv6 Works

This is the hybrid:

1. The client uses SLAAC to configure its IPv6 address from the router advertisement.
2. But because the O flag is set, the client also sends an Information-request message to the DHCPv6 server.
3. The server responds with configuration info (DNS servers, domain search list, etc.) — but not addresses.
4. No address tracking happens. The server doesn't maintain state about which addresses are assigned.

Common Mistakes People Make

Confusing M and O Flags

I see this constantly. Which means people memorize "M means managed" and "O means other" but forget what each actually controls. But here's a trick: M controls addresses (Managed = addresses managed by DHCPv6). O controls other stuff (Other = other configuration like DNS) That alone is useful..

Thinking SLAAC Can't Provide DNS

This is outdated thinking. Yes, pure SLAAC (M=0, O=0) can't provide DNS. But stateless DHCPv6 (M=0, O=1) absolutely can. In real terms, the quiz might ask "Can SLAAC provide DNS? " and the answer depends on which mode you're talking about.

Forgetting About Privacy Extensions

Traditional SLAAC uses EUI-64 interface identifiers derived from MAC addresses. This creates privacy concerns because the interface ID never changes and can be used to track devices. RFC 4941 privacy extensions solve this, but they're often overlooked in exam questions and real networks That alone is useful..

Easier said than done, but still worth knowing.

Mixing Up Stateful and Stateless

Stateful = the server keeps track of state (which addresses are assigned to which clients). Stateless = the server doesn't track state. The name describes the server's behavior, not whether addresses are involved.

Practical Tips That Actually Work

Use the Flag Matrix

When you're stuck on a quiz question, draw this out:

Monitor Your Neighbor Discovery (ND) Cache

In an IPv6 environment, you can't just rely on the ARP table like you did in IPv4. If you are troubleshooting connectivity, your first stop should be the NDP cache. Use commands like show ipv6 neighbors (on Cisco) or ip -6 neighbor show (on Linux) to see if the Neighbor Solicitation/Advertisement process is actually working. If you see a "STALE" or "INCOMPLETE" status for a target address, you have a Layer 2/Layer 3 connectivity issue, not necessarily a DHCP issue.

Watch the Router Advertisement (RA) Frequency

If clients are taking too long to get an address, check your RA timers. Even so, conversely, if it's too low, you're flooding your network with unnecessary multicast traffic. Now, if the Max Advertisment Interval is set too high, clients might wait a long time before realizing they need to perform a new solicitation. Finding the "sweet spot" is key to a stable network.

Conclusion

Understanding IPv6 addressing and configuration is a massive leap from the simplicity of IPv4. While it may feel overwhelming at first with all the flags (M and O) and the various modes (SLAAC, Stateful, and Stateless), it all boils down to one question: Who is responsible for the address, and who is responsible for the extra info?

Once you master the relationship between Router Advertisements and DHCPv6, the complexity vanishes. Whether you are designing a high-security enterprise network using Stateful DHCPv6 for strict auditing, or a massive IoT deployment using Stateless DHCPv6 for efficiency, knowing how these protocols interact is the foundation of modern networking. Keep these flags in mind, watch your ND cache, and you'll be well on your way to mastering the IPv6 landscape.