WEBVTT

0:00:08.580000 --> 0:00:14.860000
 Okay, so moving on, we're going
 to look at IPv6 stateless DHCP.

0:00:14.860000 --> 0:00:19.660000
 Again, same topology, not going to change
 anything around in the topology

0:00:19.660000 --> 0:00:26.280000
 right now. Okay, so again, this is
 going to be between three and six.

0:00:26.280000 --> 0:00:29.100000
 We already have this set
 up from the last lesson.

0:00:29.100000 --> 0:00:30.280000
 I haven't changed anything.

0:00:30.280000 --> 0:00:36.100000
 Router three going to router six, where
 three is acting like the router.

0:00:36.100000 --> 0:00:42.980000
 Six is at the moment acting like an
 IPv6 slack or stateless address auto

0:00:42.980000 --> 0:00:45.120000
 configuration client.

0:00:45.120000 --> 0:00:47.800000
 So he's getting his address
 and everything.

0:00:47.800000 --> 0:00:52.400000
 Okay, but this is where things
 get a little bit different.

0:00:52.400000 --> 0:01:00.340000
 Is stateless DHCP is basically running
 DHCP to get the options, but not

0:01:00.340000 --> 0:01:07.080000
 having the address assignment
 coming from DHCP itself.

0:01:07.080000 --> 0:01:11.180000
 Okay, so just to review here real quick
 before we jump in, where we are

0:01:11.180000 --> 0:01:18.540000
 on router six, he's not getting anything
 from DHCP that we looked at before.

0:01:18.540000 --> 0:01:22.340000
 All he has is an address
 and a default route.

0:01:22.340000 --> 0:01:24.100000
 That's all fine.

0:01:24.100000 --> 0:01:28.620000
 Okay, router three at the moment is
 doing nothing but sitting over here,

0:01:28.620000 --> 0:01:31.040000
 sending out router advertisement
 messages.

0:01:31.040000 --> 0:01:32.780000
 Debugs are still on.

0:01:32.780000 --> 0:01:36.220000
 Now what I'm going to do to start here though,
 we've seen the router advertisement

0:01:36.220000 --> 0:01:45.880000
 messages. So now I'm going to say turn
 off the debugging and say do debug

0:01:45.880000 --> 0:01:48.440000
 IPv6 and say do debug IPv6.

0:01:48.440000 --> 0:01:53.040000
 And we're just going to watch the DHCP
 debugging on both of these guys.

0:01:53.040000 --> 0:01:59.220000
 So we can watch what happens.

0:01:59.220000 --> 0:02:08.300000
 Okay, now what's cool about this is
 there's really nothing to do on the

0:02:08.300000 --> 0:02:12.820000
 client side. Okay, what I need to do
 is I need to go back to the server

0:02:12.820000 --> 0:02:18.500000
 side. And let's switch back over here
 and go over some of this stuff with

0:02:18.500000 --> 0:02:20.340000
 you here before we start.

0:02:20.340000 --> 0:02:24.440000
 Okay, so we're going to go
 over configuring IPv6.

0:02:24.440000 --> 0:02:27.620000
 Now the router side is
 going to get the scope.

0:02:27.620000 --> 0:02:30.380000
 And again, we're going to be using
 the router for the DHCP server.

0:02:30.380000 --> 0:02:35.880000
 You could of course use Windows, you
 know, whatever DHCP server it is

0:02:35.880000 --> 0:02:39.000000
 you want to use for IPv6.

0:02:39.000000 --> 0:02:40.260000
 It doesn't really matter.

0:02:40.260000 --> 0:02:45.240000
 Okay, as long as and this is probably
 the only little requirement here

0:02:45.240000 --> 0:02:47.880000
 for stateless DHCP.

0:02:47.880000 --> 0:02:50.540000
 And by the way, just
 throw this out there.

0:02:50.540000 --> 0:02:57.220000
 This topic, I've heard this referred
 to as DHCP light as well for IPv6,

0:02:57.220000 --> 0:03:03.800000
 although stateless DHCP is definitely
 more popular of a term.

0:03:03.800000 --> 0:03:11.260000
 But again, what's going to happen here
 is we configure IPv6 DHCP scope.

0:03:11.260000 --> 0:03:12.920000
 So we'll start with that.

0:03:12.920000 --> 0:03:18.880000
 So switching over to our server, we're
 going to do this on router three.

0:03:18.880000 --> 0:03:23.340000
 And there's a couple things that are a
 little bit different with configuring

0:03:23.340000 --> 0:03:28.440000
 an IPv6 DHCP server, although
 it's not a whole lot.

0:03:28.440000 --> 0:03:34.180000
 So it's really just
 IPv6 DHCP pool.

0:03:34.180000 --> 0:03:35.360000
 And let's give it a name.

0:03:35.360000 --> 0:03:38.880000
 I'll call it something like six
 pool or something like that.

0:03:38.880000 --> 0:03:40.380000
 It doesn't really matter.

0:03:40.380000 --> 0:03:46.580000
 This drops us into DHCP pool config
 mode for DHCP version six.

0:03:46.580000 --> 0:03:52.040000
 Now, normally, and we'll do this in
 our next lesson where we're going

0:03:52.040000 --> 0:03:56.520000
 to do full-blown DHCP, the thing a
 lot of people want to do right off

0:03:56.520000 --> 0:03:59.460000
 the bat is give it an
 address to hand out.

0:03:59.460000 --> 0:04:04.600000
 On IPv4, of course, we know we would
 put in a network statement.

0:04:04.600000 --> 0:04:08.120000
 But that's not how
 we do stateless.

0:04:08.120000 --> 0:04:12.940000
 The whole idea behind stateless is
 that the DHCP server actually isn't

0:04:12.940000 --> 0:04:16.520000
 handing out the addressing at all.


0:04:16.520000 --> 0:04:21.400000
 Okay? The idea here is all it's going
 to hand out are the options.

0:04:21.400000 --> 0:04:28.800000
 So, for example, I could say something
 like, let's see what I want to

0:04:28.800000 --> 0:04:30.400000
 put in my DNS servers.

0:04:30.400000 --> 0:04:31.540000
 It's actually DNS servers.

0:04:31.540000 --> 0:04:34.360000
 I was wondering if I was going to type
 name server and that's not it.

0:04:34.360000 --> 0:04:37.960000
 other. So DNS server, what?

0:04:37.960000 --> 0:04:42.160000
 2001 DB eight colon 100
 colon 100 colon col...

0:04:42.160000 --> 0:04:44.400000
 Whoops. Yeah, I know
 it's incomplete.

0:04:44.400000 --> 0:04:45.640000
 colon colon one.

0:04:45.640000 --> 0:04:47.180000
 That's not accurate.

0:04:47.180000 --> 0:04:48.460000
 It's not a DNS server.

0:04:48.460000 --> 0:04:51.320000
 Okay? But I can certainly
 put that in.

0:04:51.320000 --> 0:04:55.400000
 How about like a domain name
 is, you know, I and E.

0:04:55.400000 --> 0:05:00.060000
 .com. Okay? Whatever it
 is you want to put in.

0:05:00.060000 --> 0:05:06.680000
 Remember what we said in the last lesson
 that the problem with Slack is

0:05:06.680000 --> 0:05:14.900000
 that it gives you no way to get other
 DHCP options to be sent to the client.

0:05:14.900000 --> 0:05:20.720000
 And basically what we're doing here
 is we're creating a DHCP server who

0:05:20.720000 --> 0:05:26.740000
 is doing nothing but handing
 out scope information.

0:05:26.740000 --> 0:05:31.700000
 And the other thing I want to point
 out is that none of these are about

0:05:31.700000 --> 0:05:34.660000
 a default route or anything else.

0:05:34.660000 --> 0:05:42.300000
 Like I said, the default router is coming
 from neighbor discovery router

0:05:42.300000 --> 0:05:45.180000
 advertisement messages.

0:05:45.180000 --> 0:05:51.020000
 Not from here. So what we do need to
 do though, and this is a little bit

0:05:51.020000 --> 0:05:58.240000
 different from IPv4 if you've ever
 run IPv4 DHCP on a router.

0:05:58.240000 --> 0:06:03.020000
 It's not certainly not my recommended
 practice, but it's just easiest

0:06:03.020000 --> 0:06:04.980000
 to do it here this way today.

0:06:04.980000 --> 0:06:09.240000
 So what I'm going to do is use this,
 but this is one thing that's a little

0:06:09.240000 --> 0:06:11.260000
 bit different is you have
 to go into the interface.

0:06:11.260000 --> 0:06:19.000000
 So in our case it's FAA00.36 and you
 have to say IPv6 DHCP server and

0:06:19.000000 --> 0:06:21.480000
 call to the pool name
 that we created.

0:06:21.480000 --> 0:06:24.980000
 As soon as we do this, since we have
 the debugging on, we should see the

0:06:24.980000 --> 0:06:27.140000
 DHCP server start up.

0:06:27.140000 --> 0:06:32.280000
 There it goes. So IPv6 DHCP
 server is now started.

0:06:32.280000 --> 0:06:38.080000
 But notice that we also have gotten
 no requests whatsoever.

0:06:38.080000 --> 0:06:42.040000
 And just to show you that it's not
 going to happen like, you know, do

0:06:42.040000 --> 0:06:46.160000
 a reset or something like that, I will
 actually shut this interface on

0:06:46.160000 --> 0:06:48.440000
 router 6. We'll bring
 this thing down.

0:06:48.440000 --> 0:06:53.500000
 And just so you know, I do have IP
 version 4 running underneath all of

0:06:53.500000 --> 0:06:56.980000
 this because we will need
 it for some stuff later.

0:06:56.980000 --> 0:07:03.260000
 So when you see like that go down, that's
 just OSPF for IPv4 running underneath.

0:07:03.260000 --> 0:07:07.760000
 It's also a pretty good indicator that
 our sub-interfaces down there too.

0:07:07.760000 --> 0:07:13.500000
 So now we'll say no shut and we'll see
 that he still doesn't make a DHCP

0:07:13.500000 --> 0:07:19.900000
 request. And that's because, well,
 we're not quite done yet.

0:07:19.900000 --> 0:07:23.580000
 He's sitting here doing nothing if
 I were to say, okay, you know what,

0:07:23.580000 --> 0:07:26.740000
 why don't you show me
 the DHCP information?

0:07:26.740000 --> 0:07:31.460000
 Nothing. If you take a look at router
 3, he's not done anything except

0:07:31.460000 --> 0:07:32.980000
 fire up the server.

0:07:32.980000 --> 0:07:35.920000
 We've seen nothing else going on.

0:07:35.920000 --> 0:07:40.260000
 Okay. Now, the next thing we can do,
 or the next thing I should say we

0:07:40.260000 --> 0:07:46.540000
 have to do, is simply to configure
 the router advertiser message.

0:07:46.540000 --> 0:07:49.440000
 And I'm going to finish off the
 last two points I have on here.

0:07:49.440000 --> 0:07:55.720000
 And that is to actually configure the
 IPv6 host and controlling the host

0:07:55.720000 --> 0:07:58.540000
 portion with the link
 local address.

0:07:58.540000 --> 0:08:04.480000
 Now that part hasn't really changed from
 what we did in the last section.

0:08:04.480000 --> 0:08:08.720000
 Okay. If I were to go to router 6 and
 say do show run interface, kick

0:08:08.720000 --> 0:08:27.600000
 it. And then we have the IPV6 address,
 auto config with default still

0:08:27.600000 --> 0:08:29.440000
 there from before.

0:08:29.440000 --> 0:08:33.360000
 Those are the two things that those
 last two bullet points were meant

0:08:33.360000 --> 0:08:37.720000
 for. And we've already done those
 in the previous section.

0:08:37.720000 --> 0:08:40.380000
 But just as a reminder,
 they're still there.

0:08:40.380000 --> 0:08:44.520000
 He's still pulling his address, but see
 nothing there says anything about

0:08:44.520000 --> 0:08:50.880000
 DHCP. So basically router 6 is sitting
 here going, yep, got my prefix,

0:08:50.880000 --> 0:08:53.260000
 got my route, got
 everything I need.

0:08:53.260000 --> 0:08:57.560000
 Maybe he's thinking to himself, I'm
 not inside the router, I don't know

0:08:57.560000 --> 0:08:58.480000
 what he's thinking.

0:08:58.480000 --> 0:09:01.020000
 But maybe he's sitting there thinking,
 you know, it'd be really handy

0:09:01.020000 --> 0:09:04.160000
 if I had a DNS server and
 a domain name here.

0:09:04.160000 --> 0:09:06.040000
 Yeah, he doesn't, obviously.

0:09:06.040000 --> 0:09:08.120000
 But the point of course is this.

0:09:08.120000 --> 0:09:12.220000
 We need to tell router 6
 to get that information.

0:09:12.220000 --> 0:09:18.040000
 This is actually done on the server side
 through a router advertiser message.

0:09:18.040000 --> 0:09:25.000000
 So also on the sub interface, we need
 to say IPV6, neighbor discovery,

0:09:25.000000 --> 0:09:30.860000
 and the command is
 other config flag.

0:09:30.860000 --> 0:09:34.600000
 This is sort of the golden
 command, if you will.

0:09:34.600000 --> 0:09:38.160000
 This is the one you might want to
 go right down here at the moment.

0:09:38.160000 --> 0:09:45.160000
 This is what makes this DHCP
 light or stateless DHCP.

0:09:45.160000 --> 0:09:46.960000
 Two real factors.

0:09:46.960000 --> 0:09:52.780000
 Number one, obviously the whole, there
 has to be a DHCP server and it

0:09:52.780000 --> 0:09:55.520000
 has to be set up with options.

0:09:55.520000 --> 0:09:57.940000
 And when I was saying earlier, there
 was a little bit of a caveat with

0:09:57.940000 --> 0:10:01.740000
 using other devices
 as your DHCP server.

0:10:01.740000 --> 0:10:08.660000
 The caveat is they have to support creating
 DHCP options without having

0:10:08.660000 --> 0:10:13.200000
 the DHCP scope actually set.

0:10:13.200000 --> 0:10:19.240000
 So as soon as we turn this on, we will
 then see router 6 immediately go,

0:10:19.240000 --> 0:10:22.820000
 oh, I'm supposed to get
 more information.

0:10:22.820000 --> 0:10:28.940000
 See that? He immediately starts the
 DHCP client, sends out a request for

0:10:28.940000 --> 0:10:33.500000
 more information, gets the
 reply, and look at this.

0:10:33.500000 --> 0:10:39.320000
 Now we have the DNS server and the
 domain name, just like we wanted.

0:10:39.320000 --> 0:10:42.960000
 You can also, of course, look at the router
 3 side and see that he received

0:10:42.960000 --> 0:10:48.780000
 the request, used the pull from the
 interface, and sent the information

0:10:48.780000 --> 0:10:51.860000
 out that interface.

0:10:51.860000 --> 0:10:56.440000
 So now if we were to go back here and
 look at our DHCP for the interface,

0:10:56.440000 --> 0:11:00.420000
 we can see what happened.

0:11:00.420000 --> 0:11:04.420000
 Now he already got his information,
 prefix state he wasn't even trying

0:11:04.420000 --> 0:11:08.140000
 to get, but the important thing is he
 got those two pieces of information

0:11:08.140000 --> 0:11:12.960000
 right there. The rest of this stuff
 on here, of course, we'll go over

0:11:12.960000 --> 0:11:20.380000
 in the next section where we're
 going to do full-blown DHCP.

0:11:20.380000 --> 0:11:23.580000
 So that's where we're
 going to head next.

0:11:23.580000 --> 0:11:30.760000
 But this is simply DHCP light, or like
 I said, the real proper common

0:11:30.760000 --> 0:11:36.340000
 more recent name is
 stateless DHCP.

0:11:36.340000 --> 0:11:41.240000
 And again, the big thing to remember
 on that is that it is simply DHCP

0:11:41.240000 --> 0:11:49.400000
 with a scope, with options, but no actual
 pull of addresses to hand out.

0:11:49.400000 --> 0:11:56.140000
 All we're doing is supplementing Slack
 and using Slack in combination

0:11:56.140000 --> 0:12:00.960000
 with DHCP to get a client everything
 they need to be on the network.

0:12:00.960000 --> 0:12:06.280000
 Not just the prefix, not just the default
 gateway, but also DNS and any

0:12:06.280000 --> 0:12:11.980000
 other DHCP options they need to actually
 be a full-blown functional machine

