MicroNugget: What is a Stateless DHCP with IPv6?

In this video, Keith Barker covers stateless DHCP with IPv6. SLAAC enables a client, when first connecting to an IPv6 network, to automatically discover what network it's connected to and configure its host ID. But when that leaves some important option information un-configured, you need Stateless DHCP.

You're running an IPv6 network and you connect a new device to it. The device sees the network and sends a router solicitation to which the router responds with a router advertisement. Combining that router information with the network address space it receives, the client can calculate its own host or interface ID. That's SLAAC.

But there's a problem: there are no instructions to the client on which DNS servers to use for name resolutions — and IPv6 addresses can get very long, so good DNS management is essential. Keith explains, and then demonstrates live, how to train a network to ask for option information by configuring the M bit and the O bit that reside in the Router Advertisement.

Start learning with CBT Nuggets:

[KeithBarker]

Thanks for the comments!

Best wishes,

Keith Barker

[KeithBarker]

Hi Adam- Thanks for the feedback. Glad the video is useful for you.

Cheers,

Keith

[markovujanic]

I really really like this video and wireshark screenshots.

[pierreuntel]

This guy sounds like he's doing commentary on a baseball match or something...



I like it

[overtheedge]

Great video Keith. Had a question if you or someone that could help:

When forwarding the DHCPv6 request message from the client to the DHCPv6 server, what source address is used by the router to forward the message to the server?

For example the interface address configured on the router is 2601:fc00:c:50::1/64 and the client received v6 address is

Our DHCP server is not on the same LAN segment as the DHCP client network and we are using DHCP helper address of 2601:fc00:f:7::109.

[slaye]

Are link-local addresses advertised as network prefixes in RA's?

[muhammad.rafi]

Hi Keith, video is informative but not fully, I am sorry to say, there are few information is missing from this video, like what type messages are being sent whether multicast or unicast...in DORA for v4 we know what messages are multicast and unicast and i was expecting the same information from this video...

[shauryasahu]

I found this too fast.
Same amount of content should be told in double time duration, with more explainations at some places

[AJProdz]

You talk too fast so i had to decrease the speed.

But good video :)