WEBVTT

0:00:07.840000 --> 0:00:13.280000
 All right, now we're going to take a look
 at Slack configuration or stateless

0:00:13.280000 --> 0:00:16.300000
 address automatic configuration.

0:00:16.300000 --> 0:00:21.100000
 So the basic idea here, we're going
 to be using the same topology that

0:00:21.100000 --> 0:00:23.540000
 we used in our previous lesson.

0:00:23.540000 --> 0:00:28.020000
 Again, we're going to be focusing on
 VLAN 36, but this time we're going

0:00:28.020000 --> 0:00:30.440000
 to be looking more at
 the router 6 side.

0:00:30.440000 --> 0:00:33.620000
 Well, actually sort of both,
 router 3 and router 6.

0:00:33.620000 --> 0:00:39.060000
 And that's going to be basically what
 this is going to be for is to have

0:00:39.060000 --> 0:00:44.120000
 router 6 automatically pull
 its address from router 3.

0:00:44.120000 --> 0:00:50.380000
 So the basic idea before we jump too far
 into this as far as configuration,

0:00:50.380000 --> 0:00:55.120000
 you know, stateless auto configuration
 again is a replacement, so to speak.

0:00:55.120000 --> 0:01:00.620000
 An alternative method may be a
 better way to say it for DHCP.

0:01:00.620000 --> 0:01:05.180000
 And the idea is we can have a device automatically
 learn certain information

0:01:05.180000 --> 0:01:11.820000
 and the way Slack is right now, although
 I know there have been some RFCs

0:01:11.820000 --> 0:01:14.860000
 proposed to update Slack.

0:01:14.860000 --> 0:01:19.800000
 But what you're going to get so far
 is from your router advertisement,

0:01:19.800000 --> 0:01:21.360000
 and we're going to see this
 here in just a minute.

0:01:21.360000 --> 0:01:28.900000
 But from your router advertisement, you're
 going to get the prefix length

0:01:28.900000 --> 0:01:34.280000
 and the global address being
 advertised by the router.

0:01:34.280000 --> 0:01:39.940000
 The client is going to take that information
 and essentially make up his

0:01:39.940000 --> 0:01:43.920000
 own client portion of the address.


0:01:43.920000 --> 0:01:49.420000
 You will then also use the router advertisement
 to learn who your default

0:01:49.420000 --> 0:01:57.920000
 gateway is. So, you know, for warehouse
 scanners and various sensors and

0:01:57.920000 --> 0:02:00.200000
 so on, that's all fine.

0:02:00.200000 --> 0:02:02.440000
 And that's what we're going
 to start with here.

0:02:02.440000 --> 0:02:07.460000
 The problem comes in, of course, is if
 you need actual DNS servers, things

0:02:07.460000 --> 0:02:12.040000
 like that. That's where this falls a little
 short and where they're proposing

0:02:12.040000 --> 0:02:18.260000
 to do some changes to the RFCs.

0:02:18.260000 --> 0:02:21.380000
 So, the first thing we're going to take
 a look at is actually configuring

0:02:21.380000 --> 0:02:23.740000
 the IPv6 router side.

0:02:23.740000 --> 0:02:26.540000
 And in our case, that's going
 to be router-thrit.

0:02:26.540000 --> 0:02:28.720000
 So this is where we
 left off before.

0:02:28.720000 --> 0:02:32.540000
 I just want to show you one thing here
 real quick that I did do automatically

0:02:32.540000 --> 0:02:35.760000
 before we started on
 all these routers.

0:02:35.760000 --> 0:02:42.540000
 If we were to say, do show
 run, pipe, include IPv6.

0:02:42.540000 --> 0:02:48.040000
 Just want you to see that these devices
 automatically, well, not automatically,

0:02:48.040000 --> 0:02:49.400000
 we had to enable it.

0:02:49.400000 --> 0:02:54.640000
 But I already turned on IPv6
 unicast routing and IPv6 SAF.

0:02:54.640000 --> 0:03:00.400000
 Now, the IPv6 unicast routing wasn't
 really required for what we did in

0:03:00.400000 --> 0:03:01.640000
 our previous section.

0:03:01.640000 --> 0:03:05.040000
 Just assigning addresses
 to interfaces and so on.

0:03:05.040000 --> 0:03:07.280000
 No problem at all.

0:03:07.280000 --> 0:03:11.680000
 But as soon as you want to start doing
 routing, then, of course, you'll

0:03:11.680000 --> 0:03:17.020000
 need that. And the reason I'm bringing
 this up here with Slack is if I

0:03:17.020000 --> 0:03:23.520000
 were to say, do debug IPv6 neighbour
 discovery router advertising, we're

0:03:23.520000 --> 0:03:25.660000
 going to do our neighbour
 discovery here.

0:03:25.660000 --> 0:03:29.260000
 And as soon as we start looking at this,
 we're going to see that router

0:03:29.260000 --> 0:03:31.100000
 three is already sending out.

0:03:31.100000 --> 0:03:34.280000
 There's the first one right there.


0:03:34.280000 --> 0:03:42.980000
 He is sending out a router advertisement
 on his link local to, and that

0:03:42.980000 --> 0:03:49.540000
 the FFO2 colon colon one, that is
 the all nodes multicast address.

0:03:49.540000 --> 0:03:52.100000
 So the FFO2 means link local.

0:03:52.100000 --> 0:03:55.140000
 So it's a link local multicast
 just on this segment.

0:03:55.140000 --> 0:04:01.200000
 And colon colon one on his
 FA00 up 36 interface.

0:04:01.200000 --> 0:04:04.540000
 Okay. He advertises the MTU.

0:04:04.540000 --> 0:04:07.120000
 He advertises the prefix.

0:04:07.120000 --> 0:04:11.660000
 And he also advertises a valid
 and preferred lifetime.

0:04:11.660000 --> 0:04:15.620000
 The valid lifetime is how long you're
 allowed to use that prefix.

0:04:15.620000 --> 0:04:23.240000
 The preferred lifetime is how long you
 originate traffic from that prefix.

0:04:23.240000 --> 0:04:26.860000
 Now, this as you can see is
 happening automatically.

0:04:26.860000 --> 0:04:32.400000
 I didn't have to do anything on router
 three except make it a router.

0:04:32.400000 --> 0:04:39.340000
 Soon as you turn on IPv6, unicast routing,
 you're going to get router

0:04:39.340000 --> 0:04:42.060000
 advertisements going
 out the interface.

0:04:42.060000 --> 0:04:47.420000
 Now if I said IPv6 question mark on
 the interface, there's quite a few

0:04:47.420000 --> 0:04:50.660000
 things here we can do, of course.

0:04:50.660000 --> 0:04:55.520000
 Okay. And most of this is going to be
 that we're talking about right now

0:04:55.520000 --> 0:04:57.760000
 is going to be under
 neighbor discovery.

0:04:57.760000 --> 0:05:02.260000
 So if we said IPv6 neighbor discovery
 is the things we're going to focus

0:05:02.260000 --> 0:05:05.740000
 on right this second, couple
 of things we can do.

0:05:05.740000 --> 0:05:11.800000
 Okay. First one is the RA, which is the
 router advertisement message we're

0:05:11.800000 --> 0:05:13.480000
 talking about right now.

0:05:13.480000 --> 0:05:16.160000
 And a couple of things you can do.


0:05:16.160000 --> 0:05:20.460000
 Okay. First off, you can
 change the lifetime.

0:05:20.460000 --> 0:05:26.060000
 You can change the interval, hop
 limit of how far it'll go.

0:05:26.060000 --> 0:05:27.860000
 Of course, the MTU.

0:05:27.860000 --> 0:05:30.900000
 And if you didn't want to do this, because
 a lot of people look at this

0:05:30.900000 --> 0:05:35.040000
 and go, well, what if I'm going to
 use some other method to configure

0:05:35.040000 --> 0:05:40.600000
 this? I don't want this neighbor discovery
 and router advertisement message.

0:05:40.600000 --> 0:05:42.380000
 Then you can suppress it.

0:05:42.380000 --> 0:05:47.780000
 I will say this though, before you choose
 to press the router advertising

0:05:47.780000 --> 0:05:53.380000
 messages, you really need to think
 through what you're doing here.

0:05:53.380000 --> 0:06:00.560000
 The reason I say that is when we get
 to DHCP a little bit later, you're

0:06:00.560000 --> 0:06:04.380000
 going to discover that there's no option
 to advertise your default gateway

0:06:04.380000 --> 0:06:09.520000
 or default router in DHCP in IPv6.


0:06:09.520000 --> 0:06:15.080000
 That's gone. Your default gateway next
 hop, whatever you want to call

0:06:15.080000 --> 0:06:20.200000
 it, is going to come from a router
 advertisement message.

0:06:20.200000 --> 0:06:26.380000
 So before you just shut this off, you
 probably don't want to just do that

0:06:26.380000 --> 0:06:27.900000
 unless you know why.

0:06:27.900000 --> 0:06:29.800000
 But we can suppress it.

0:06:29.800000 --> 0:06:32.120000
 We can change the interval to
 make it run a little faster.

0:06:32.120000 --> 0:06:34.320000
 As you can see, it doesn't
 go very often here.

0:06:34.320000 --> 0:06:36.900000
 It doesn't really need to.

0:06:36.900000 --> 0:06:42.400000
 Because when the client comes online,
 it will send out a solicitation

0:06:42.400000 --> 0:06:47.220000
 message. In fact, rather than speeding
 it up, because it gets a little

0:06:47.220000 --> 0:06:50.700000
 harder to tell here, I'm going to let
 it go a little bit slower for right

0:06:50.700000 --> 0:06:56.500000
 now. And as we bring up router six
 as the client, we can see that it's

0:06:56.500000 --> 0:06:58.860000
 not like the client is really
 going to sit there.

0:06:58.860000 --> 0:07:05.940000
 And by the way, when I say it slow,
 notice that this message right here,

0:07:05.940000 --> 0:07:10.200000
 where was it? Oh, I've looked at
 a couple of things since then.

0:07:10.200000 --> 0:07:15.460000
 So, well, here's him advertising 36,
 and I don't have the timestamp on.

0:07:15.460000 --> 0:07:19.040000
 But if you notice, he hasn't
 advertised it for a while.

0:07:19.040000 --> 0:07:25.800000
 And the last one was way back up here
 where he advertised 36 when we first

0:07:25.800000 --> 0:07:30.080000
 started. So we have some other messages
 going on, but that's him advertising

0:07:30.080000 --> 0:07:34.180000
 36. There's him advertising
 36 again.

0:07:34.180000 --> 0:07:39.980000
 Do show IPv6 interface
 F800 dot 36.

0:07:39.980000 --> 0:07:46.640000
 The default is 200 seconds.

0:07:46.640000 --> 0:07:50.660000
 So, and again, we can speed this up
 a little bit just to show you how

0:07:50.660000 --> 0:07:52.660000
 the command works.

0:07:52.660000 --> 0:07:55.280000
 I didn't actually type it in.

0:07:55.280000 --> 0:08:00.620000
 And we could change this.

0:08:00.620000 --> 0:08:02.860000
 The shay-out works without
 going crazy with it.

0:08:02.860000 --> 0:08:06.240000
 Let's just say once
 every 30 seconds.

0:08:06.240000 --> 0:08:09.680000
 And then if I look at the interface
 again, that'll, of course, trigger

0:08:09.680000 --> 0:08:11.660000
 to go right away.

0:08:11.660000 --> 0:08:15.040000
 But now it's going
 every 30 seconds.

0:08:15.040000 --> 0:08:20.220000
 Okay. Now, again, the reason I said this
 isn't all that critical, honestly,

0:08:20.220000 --> 0:08:25.080000
 is when the client comes online, he's
 not just going to have to sit there

0:08:25.080000 --> 0:08:28.960000
 and wait until this guy
 sends an advertisement.

0:08:28.960000 --> 0:08:30.620000
 That's not how it works.

0:08:30.620000 --> 0:08:36.160000
 The only reason that we even have these
 timed updates being sent every

0:08:36.160000 --> 0:08:44.260000
 so often is in case you go and change
 the prefix being advertised or you

0:08:44.260000 --> 0:08:47.220000
 change the valid and
 preferred lifetime.

0:08:47.220000 --> 0:08:50.780000
 If you change any of that, then you're
 going to want it to update the

0:08:50.780000 --> 0:08:55.320000
 clients that have already gotten
 this information previously.

0:08:55.320000 --> 0:08:58.180000
 So, that's the only reason for
 the timed update anyway.

0:08:58.180000 --> 0:09:00.800000
 So, if it's not the fastest thing in
 the world, you know, the default

0:09:00.800000 --> 0:09:04.340000
 is 200 seconds. You know, a lot of people
 go, I don't want a machine taking

0:09:04.340000 --> 0:09:06.560000
 200 seconds until it
 gets an address.

0:09:06.560000 --> 0:09:08.100000
 That's not what this is for.

0:09:08.100000 --> 0:09:15.100000
 This, you know, this periodic update is
 literally just to refresh anything.

0:09:15.100000 --> 0:09:23.840000
 Okay? So, if I were to, again, just for
 an example, say instead of interval,

0:09:23.840000 --> 0:09:26.800000
 right, we could say, let's see,
 let's take a look here.

0:09:26.800000 --> 0:09:30.840000
 Let's do lifetime.

0:09:30.840000 --> 0:09:34.160000
 So, we'll say that
 it's a lifetime.

0:09:34.160000 --> 0:09:36.360000
 I'm sorry, that's just for
 the router advertisement.

0:09:36.360000 --> 0:09:38.880000
 We need to do prefix for
 the one I'm looking at.

0:09:38.880000 --> 0:09:48.860000
 So, we'll say prefix and then we'll say
 default and set the valid lifetime.

0:09:48.860000 --> 0:09:52.320000
 Okay? So, just for the sake of something
 to do here, we'll say that we're

0:09:52.320000 --> 0:09:56.500000
 going to say it's valid for 600 and
 this is, of course, in seconds, so

0:09:56.500000 --> 0:10:00.580000
 that'd be 10 minutes and it's
 preferred for five minutes.

0:10:00.580000 --> 0:10:06.340000
 So, if we just change something like
 that, next interval, there we go,

0:10:06.340000 --> 0:10:08.500000
 we'll see these get changed.

0:10:08.500000 --> 0:10:12.240000
 And, by the way, you might have noticed
 too, as soon as I changed it,

0:10:12.240000 --> 0:10:17.220000
 notice that the iOS just kicked
 off another update anyway.

0:10:17.220000 --> 0:10:21.800000
 So, it's not even, you know, a lot of
 changes you make are going to trigger

0:10:21.800000 --> 0:10:25.340000
 an update anyway, even if it's
 not the 30 seconds yet.

0:10:25.340000 --> 0:10:30.260000
 Okay? But in any case, so here's router
 three over here advertising the

0:10:30.260000 --> 0:10:33.360000
 information. Now, let's go take
 a look at the client side.

0:10:33.360000 --> 0:10:38.760000
 So, let's go over to router six and
 we're going to say IPv6 address and

0:10:38.760000 --> 0:10:40.700000
 the command is auto-config.

0:10:40.700000 --> 0:10:47.540000
 Now, just so you know, before I type
 this, do show IPv6 interface brief.

0:10:47.540000 --> 0:10:49.080000
 He's going to have no address.

0:10:49.080000 --> 0:10:52.340000
 We're looking at this interface
 right here once again.

0:10:52.340000 --> 0:11:00.420000
 And I just want you guys to understand
 that if this were Windows, Linux,

0:11:00.420000 --> 0:11:06.840000
 Mac, just about any other desktop operating
 system out there and device,

0:11:06.840000 --> 0:11:12.500000
 anything like that, assuming of course
 it's IPv6 enabled, it would have

0:11:12.500000 --> 0:11:15.780000
 already pulled this information
 most likely.

0:11:15.780000 --> 0:11:21.260000
 Most things are automatically set up
 to do Slack and they'd already be

0:11:21.260000 --> 0:11:23.700000
 going. You'd already be done.

0:11:23.700000 --> 0:11:30.080000
 But the router, well, you know, understandably
 I hope is sort of designed

0:11:30.080000 --> 0:11:33.720000
 to be, well, a router,
 not an end device.

0:11:33.720000 --> 0:11:38.520000
 And therefore, you have to actually tell
 it, you know what, get your address

0:11:38.520000 --> 0:11:41.700000
 from auto-config.

0:11:41.700000 --> 0:11:44.780000
 As soon as we do that, if we hop over
 to router three, we should have

0:11:44.780000 --> 0:11:46.360000
 seen, there we go.

0:11:46.360000 --> 0:11:51.760000
 So, this is the other guy sending
 a router advertisement.

0:11:51.760000 --> 0:11:54.560000
 Oh, here we go. I wasn't
 looking up far enough.

0:11:54.560000 --> 0:11:55.720000
 I was looking for the
 solicit message.

0:11:55.720000 --> 0:12:01.600000
 There it is. Sending
 a solicited RA.

0:12:01.600000 --> 0:12:04.240000
 Now, notice he didn't wait
 for a time or anything.

0:12:04.240000 --> 0:12:08.300000
 He received right here, he received an
 RS, which is a router solicitation

0:12:08.300000 --> 0:12:13.640000
 message. So, he received the router
 solicitation on his interface from

0:12:13.640000 --> 0:12:18.360000
 colon colon. Basically, it's from, you
 know, the guy doesn't know, he's

0:12:18.360000 --> 0:12:19.620000
 saying, who's the router?

0:12:19.620000 --> 0:12:21.700000
 I need to know what my prefix is.

0:12:21.700000 --> 0:12:24.120000
 Basically, he's saying,
 I know nothing.

0:12:24.120000 --> 0:12:28.940000
 So, I, of course, send him that information
 right away and that's it.

0:12:28.940000 --> 0:12:32.500000
 Now, the rest of this, of course, is
 going on with some other information.

0:12:32.500000 --> 0:12:35.900000
 But you can see that's the important
 part I want to show you right now

0:12:35.900000 --> 0:12:42.240000
 is that we got the information.

0:12:42.240000 --> 0:12:50.120000
 So do show IPv6 interface brief and
 he's pulled that prefix from router

0:12:50.120000 --> 0:12:56.340000
 3. Now, something else you may want
 to do and this sort of goes back to

0:12:56.340000 --> 0:13:00.040000
 our previous lesson and this is
 completely optional, of course.

0:13:00.040000 --> 0:13:02.600000
 There's two things here
 that are optional.

0:13:02.600000 --> 0:13:07.160000
 First, you might want to control the
 address because, again, that's not

0:13:07.160000 --> 0:13:12.480000
 the prettiest host address in the world,
 especially if this is a router

0:13:12.480000 --> 0:13:16.200000
 and you're going to be doing traces
 and you're going to be doing pings

0:13:16.200000 --> 0:13:20.800000
 and you're going to be doing network
 diagnostic and troubleshooting.

0:13:20.800000 --> 0:13:25.260000
 If that's an end device, if that's
 somebody's Sally's workstation out

0:13:25.260000 --> 0:13:29.800000
 in accounting or something, just like
 DHCP, we don't really care what

0:13:29.800000 --> 0:13:35.920000
 its address is. But this is the device,
 we may actually have to troubleshoot.

0:13:35.920000 --> 0:13:40.240000
 So you may want to, a lot of times
 with our routers, I'm sure you all

0:13:40.240000 --> 0:13:44.060000
 understand this, that we would literally
 just have them all statically

0:13:44.060000 --> 0:13:47.940000
 assigned. But in the interest of showing
 you all the different options,

0:13:47.940000 --> 0:13:49.240000
 we're not going to do that.

0:13:49.240000 --> 0:13:54.560000
 So we can combine this, what we looked
 at before though, and say IPv6

0:13:54.560000 --> 0:14:03.460000
 address, Fe80, colon colon six, link
 local, and actually control that

0:14:03.460000 --> 0:14:07.040000
 he's getting this part from Slack.


0:14:07.040000 --> 0:14:11.640000
 But then, since we hard coded the link
 local address and therefore his

0:14:11.640000 --> 0:14:17.340000
 IPv6 client ID, we've now also controlled
 what his host portion is going

0:14:17.340000 --> 0:14:20.360000
 to be for that Slack address.

0:14:20.360000 --> 0:14:25.980000
 So that's one optional
 thing we could do.

0:14:25.980000 --> 0:14:33.300000
 And the other thing we can do is actually
 control that default route.

0:14:33.300000 --> 0:14:36.860000
 Remember we said with Slack, and let
 me switch back over here real quick,

0:14:36.860000 --> 0:14:39.940000
 because we're looking right now, of
 course, at configuring the client

0:14:39.940000 --> 0:14:42.540000
 device, and that's the main thing.


0:14:42.540000 --> 0:14:46.520000
 The client device should be getting
 some basic information here.

0:14:46.520000 --> 0:14:49.240000
 It needs to get the prefix,
 which we've gotten, check.

0:14:49.240000 --> 0:14:54.720000
 It needs to get the prefix length,
 slash 64 in our case, check.

0:14:54.720000 --> 0:14:58.220000
 And it needs to get, well,
 see, here's the next part.

0:14:58.220000 --> 0:15:03.100000
 It needs to get its default gateway
 or its default router.

0:15:03.100000 --> 0:15:10.180000
 Now, again, in the case of a normal
 desktop operating system, end device

0:15:10.180000 --> 0:15:15.480000
 acting like a Slack client,
 we'd probably be done.

0:15:15.480000 --> 0:15:20.920000
 But once again, because this is
 a router, we're not going to be.

0:15:20.920000 --> 0:15:24.280000
 I'm going to show you that in one second,
 but just real quickly here.

0:15:24.280000 --> 0:15:28.200000
 I want to show you what we're doing right
 now, of course, is how we control

0:15:28.200000 --> 0:15:32.120000
 the host portion with the
 link local address.

0:15:32.120000 --> 0:15:34.340000
 But here's the thing with
 the default gateway.

0:15:34.340000 --> 0:15:45.440000
 If I now said do show IPv6 route, notice
 that he's got the slash 64, and

0:15:45.440000 --> 0:15:50.980000
 if you look at your legend up top, notice
 that ND, sorry, I'm highlighting

0:15:50.980000 --> 0:15:55.180000
 the wrong thing, NDP, is that he learned
 that from a neighbor discovery

0:15:55.180000 --> 0:16:00.280000
 prefix, but what he does not have, and
 you can look over the routing table

0:16:00.280000 --> 0:16:05.980000
 here, these are all locally
 connected interfaces.

0:16:05.980000 --> 0:16:10.480000
 So that's, of course, the interface
 that we're talking about right now.

0:16:10.480000 --> 0:16:14.560000
 And then, and I know you guys don't
 have the diagram right in front of

0:16:14.560000 --> 0:16:21.280000
 you, but that is the VLAN 69
 interface, both of those.

0:16:21.280000 --> 0:16:26.760000
 This, of course, is his loopback, and
 this is simply for multicast traffic.

0:16:26.760000 --> 0:16:30.600000
 Anything starting with FF
 slash eight is multicast.

0:16:30.600000 --> 0:16:35.240000
 So that's just basically telling him
 to receive any multicast, it comes

0:16:35.240000 --> 0:16:40.060000
 to me. What we don't have
 is a colon colon route.

0:16:40.060000 --> 0:16:42.140000
 We don't have a default route.

0:16:42.140000 --> 0:16:45.740000
 And again, this sort of goes back to
 the fact that this is a router, not

0:16:45.740000 --> 0:16:49.140000
 a client, and it's basically sitting
 there going, well, I'm a router,

0:16:49.140000 --> 0:16:50.660000
 I should have routes.

0:16:50.660000 --> 0:16:54.700000
 I don't, I'm not a client, I don't
 just go to the default route.

0:16:54.700000 --> 0:16:58.540000
 But if you want it to, going back up to
 our command where we put the address

0:16:58.540000 --> 0:17:07.960000
 in, and actually get
 a default route.

0:17:07.960000 --> 0:17:13.600000
 And if we do that, then it will insert
 the default route into the routing

0:17:13.600000 --> 0:17:16.820000
 table. Let's give
 it a second here.

0:17:16.820000 --> 0:17:21.200000
 We may have to actually bounce the
 interface to get it to do it again.

0:17:21.200000 --> 0:17:22.400000
 Now there we go.

0:17:22.400000 --> 0:17:27.160000
 Usually it kicks in, but I'm not patient,
 so I often just bounce the interface

0:17:27.160000 --> 0:17:29.200000
 quick. But there we go.

0:17:29.200000 --> 0:17:33.560000
 So there's your colon colon slash zero,
 otherwise known as a default.

0:17:33.560000 --> 0:17:36.380000
 And it is from neighbor discovery.


0:17:36.380000 --> 0:17:40.060000
 So that is your NDD fault,
 neighbor discovery default.

0:17:40.060000 --> 0:17:47.340000
 And by the way, I also notice that
 it gives it a very, very good admin

0:17:47.340000 --> 0:17:50.760000
 distance. And of course the metric
 is zero because it's connected.

0:17:50.760000 --> 0:17:54.540000
 But these are going to be very, very
 believable routes when it comes to

0:17:54.540000 --> 0:17:58.660000
 comparing this to other
 routing protocols.

0:17:58.660000 --> 0:18:08.480000
 Now what we don't have at this point is
 if I said do show IPV6 DHCP interface,

0:18:08.480000 --> 0:18:16.700000
 gigabit 00.36, is we're not
 getting this from DHCP.

0:18:16.700000 --> 0:18:21.740000
 Now in a couple minutes, this is going
 to change a little bit in our next

0:18:21.740000 --> 0:18:23.960000
 lesson. But for right
 now, that's it.

0:18:23.960000 --> 0:18:27.300000
 That's Slack. It's pretty
 straightforward.

0:18:27.300000 --> 0:18:34.220000
 The big thing to remember of
 course is that it's not DHCP.

0:18:34.220000 --> 0:18:40.720000
 All you're getting is a prefix, a prefix
 length, and your default gateway.

0:18:40.720000 --> 0:18:46.240000
 The host portion you make up yourself,
 and as far as any other options

0:18:46.240000 --> 0:18:50.280000
 that you would normally get from DHCP,
 then this is not going to give

0:18:50.280000 --> 0:18:51.500000
 you those options.

