WEBVTT

0:00:08.180000 --> 0:00:12.680000
 So here we're going to talk about something
 called the IPv6 neighbor discovery

0:00:12.680000 --> 0:00:17.820000
 process, which is actually a combination
 of several IPv6 packets working

0:00:17.820000 --> 0:00:20.720000
 together to perform special roles.


0:00:20.720000 --> 0:00:26.140000
 Now in the previous video, I talked about
 five special or distinguishable

0:00:26.140000 --> 0:00:32.800000
 types of IPv6 and we talked about
 multicast and a couple of others.

0:00:32.800000 --> 0:00:35.320000
 And I mentioned that there was one more
 special one that I wanted to get

0:00:35.320000 --> 0:00:39.460000
 to, but in order to understand that
 last one, we have to understand this

0:00:39.460000 --> 0:00:43.580000
 first. And then once I go through this,
 then my last video on sort of

0:00:43.580000 --> 0:00:48.080000
 IPv6 general theory will be on that final
 special address I've been holding

0:00:48.080000 --> 0:00:52.680000
 back. So let's talk about
 IPv6 neighbor discovery.

0:00:52.680000 --> 0:00:58.800000
 We've talked as far as layer
 four protocols are concerned.

0:00:58.800000 --> 0:01:04.200000
 We've really focused pretty much
 exclusively on TCP and UDP.

0:01:04.200000 --> 0:01:08.620000
 But I have hinted in some previous slides
 that there were others as well.

0:01:08.620000 --> 0:01:12.900000
 Well, one of them that you definitely
 need to be aware of that's a layer

0:01:12.900000 --> 0:01:21.060000
 four and above protocol is ICMP, the
 Internet Control Messaging Protocol.

0:01:21.060000 --> 0:01:23.740000
 ICMP, Internet Control
 Messaging Protocol.

0:01:23.740000 --> 0:01:31.160000
 So the most common usage of ICMP is
 when people issue the ping command.

0:01:31.160000 --> 0:01:36.180000
 For example, and you can do this
 on your own laptop as well.

0:01:36.180000 --> 0:01:42.080000
 If I open up my command prompt,
 bring it over here.

0:01:42.080000 --> 0:01:44.960000
 And a lot of times, if you want to figure
 out if you have network connectivity

0:01:44.960000 --> 0:01:51.520000
 to something, for example, I know that
 Google's DNS server, a server that

0:01:51.520000 --> 0:01:57.980000
 Google owns that can resolve websites
 to IP addresses is 8.8.8.8.

0:01:57.980000 --> 0:02:01.840000
 That's very common knowledge,
 it's public knowledge.

0:02:01.840000 --> 0:02:05.040000
 And so if I want to see if I can actually
 have connectivity to that, I

0:02:05.040000 --> 0:02:11.460000
 can type ping and then type in
 that IP address and hit enter.

0:02:11.460000 --> 0:02:15.440000
 Ah, so clearly, okay, now
 I'm getting a reply.

0:02:15.440000 --> 0:02:17.480000
 So what was just happening
 right there?

0:02:17.480000 --> 0:02:22.560000
 So when you type ping, what's actually
 happening is the CPU of your device

0:02:22.560000 --> 0:02:27.620000
 of my laptop in this case is
 creating an ICMP message.

0:02:27.620000 --> 0:02:32.240000
 And ICMP has several different kinds
 of messages depending on what the

0:02:32.240000 --> 0:02:41.660000
 objective is. Request,
 echo request.

0:02:41.660000 --> 0:02:45.960000
 Basically, sending out an
 echo request to 8.8.8.8.

0:02:45.960000 --> 0:02:51.400000
 And then if that server is also running
 ICMP, which most devices do, by

0:02:51.400000 --> 0:02:55.360000
 default, it will turn around and send
 back to me what's called an ICMP

0:02:55.360000 --> 0:02:59.480000
 echo reply. And that's
 what we see right here.

0:02:59.480000 --> 0:03:03.320000
 We see that the first one timed out for
 some reason, but then I got three

0:03:03.320000 --> 0:03:06.880000
 echo replies. So this was an echo
 request going out from me.

0:03:06.880000 --> 0:03:11.880000
 I actually sent four echo requests and
 I got a response back from three

0:03:11.880000 --> 0:03:17.360000
 of them. So that was just an
 example of ICMP in action.

0:03:17.360000 --> 0:03:19.980000
 Now there are other ICMP
 messages as well.

0:03:19.980000 --> 0:03:23.840000
 I don't have time to get into all of
 them in this course, but I would

0:03:23.840000 --> 0:03:27.560000
 definitely recommend that you Google
 the term ICMP and just be familiar

0:03:27.560000 --> 0:03:31.880000
 with the, there's about maybe five,
 four, five different ICMP messages.

0:03:31.880000 --> 0:03:36.880000
 And I've just talked about the top
 two echo request, echo reply.

0:03:36.880000 --> 0:03:39.100000
 What does that have
 to do with this?

0:03:39.100000 --> 0:03:42.260000
 Well, just like I mentioned a couple
 of slides back or a couple of videos

0:03:42.260000 --> 0:03:49.340000
 back that DHCP had been upgraded
 for V6, that there's a DHCP V6.

0:03:49.340000 --> 0:03:52.220000
 Well, there's an ICMP V6.

0:03:52.220000 --> 0:03:56.440000
 Now, this is kind of interesting when
 you think about it because ICMP,

0:03:56.440000 --> 0:04:01.360000
 because it's layer four, rides
 behind an IP header.

0:04:01.360000 --> 0:04:05.520000
 So in other words, you've got your IP
 header here and then ICMP is like

0:04:05.520000 --> 0:04:08.140000
 in the payload of the IP packet.

0:04:08.140000 --> 0:04:14.520000
 So one would wonder why did
 they have to update ICMP?

0:04:14.520000 --> 0:04:17.980000
 Well, for one thing, if they had not
 updated it, there'd be no way to

0:04:17.980000 --> 0:04:20.620000
 ping an IPV6 address.

0:04:20.620000 --> 0:04:24.960000
 Because within the body of the ICMP
 message, it says, who am I trying

0:04:24.960000 --> 0:04:29.660000
 to talk to? Well, I'm trying to talk to
 the manager of the IP packet itself,

0:04:29.660000 --> 0:04:33.000000
 but the destination you're trying to
 ping is also in the body of the ICMP

0:04:33.000000 --> 0:04:35.660000
 message saying, I'm trying to
 do an echo request to you.

0:04:35.660000 --> 0:04:37.000000
 Can you please respond back?

0:04:37.000000 --> 0:04:38.440000
 It's in the body of the packet.

0:04:38.440000 --> 0:04:43.280000
 So they had to upgrade ICMP as well
 in order to be able to handle IPV6

0:04:43.280000 --> 0:04:48.440000
 addresses. Now, in addition to doing
 that, when they update ICMP, they

0:04:48.440000 --> 0:04:53.520000
 actually added some new ICMP message
 types that did not exist before.

0:04:53.520000 --> 0:04:57.600000
 So in addition to echo request and echo
 reply, which still exists, they

0:04:57.600000 --> 0:05:04.220000
 also created four new types of ICMP V6
 messages, which are only applicable

0:05:04.220000 --> 0:05:12.460000
 for IPV6. And those are neighbor solicitation,
 neighbor advertisement,

0:05:12.460000 --> 0:05:15.420000
 router solicitation, and
 router advertisement.

0:05:15.420000 --> 0:05:21.380000
 So all four of those are in the
 body of an ICMP V6 packet.

0:05:21.380000 --> 0:05:25.920000
 In the header of the ICMP V6 packet
 in the header, there's a little type

0:05:25.920000 --> 0:05:30.160000
 code. And the type code indicates
 what kind of ICMP message is this?

0:05:30.160000 --> 0:05:31.640000
 Is this an echo request?

0:05:31.640000 --> 0:05:33.120000
 Is an echo reply?

0:05:33.120000 --> 0:05:36.520000
 Or there are other type codes
 for these things right here.

0:05:36.520000 --> 0:05:43.200000
 So these specific ICMP V6 message types
 together, we call them the neighbor

0:05:43.200000 --> 0:05:44.860000
 discovery protocol.

0:05:44.860000 --> 0:05:48.760000
 So if you hear that term, which you
 most likely will, the IPV6 neighbor

0:05:48.760000 --> 0:05:51.120000
 discovery protocol, that should
 key off in your head.

0:05:51.120000 --> 0:05:54.820000
 Oh, okay. They're talking about how
 we use these four different kinds

0:05:54.820000 --> 0:05:57.360000
 of ICMP V6 messages.

0:05:57.360000 --> 0:06:01.360000
 So let's talk about how
 this process works.

0:06:01.360000 --> 0:06:05.060000
 And what I'm specifically going to
 refer to is back when I was talking

0:06:05.060000 --> 0:06:09.200000
 about IPV6 addresses, and I was first
 introducing the concept of an IPV6

0:06:09.200000 --> 0:06:14.120000
 address. I said that a device could
 have a statically configured IPV6

0:06:14.120000 --> 0:06:20.680000
 address. I said it could learn about
 it from a DHCP V6 server, or there

0:06:20.680000 --> 0:06:25.900000
 was something special in IPV6 called stateless
 address automatic configuration,

0:06:25.900000 --> 0:06:34.080000
 or Slack SLAC. And this, these messages
 that we see right here, our stateless

0:06:34.080000 --> 0:06:38.440000
 address, stateless address automatic
 configuration works.

0:06:38.440000 --> 0:06:44.220000
 So let's wipeboard that process
 so you can see what's going on.

0:06:44.220000 --> 0:06:52.020000
 Okay, so let's start
 with our laptop.

0:06:52.020000 --> 0:07:00.460000
 And the laptop has a network
 interface card, a NIC.

0:07:00.460000 --> 0:07:08.320000
 And then all of a sudden it's
 connected to a cable.

0:07:08.320000 --> 0:07:10.740000
 And there's something at the other end
 of this cable here, I'm not going

0:07:10.740000 --> 0:07:13.680000
 to tell you what it is, but whatever
 it is, it's generating electrical

0:07:13.680000 --> 0:07:18.900000
 signal. So the NIC card on this PC says,
 aha, okay, I've been connected

0:07:18.900000 --> 0:07:21.720000
 to a network. I know I'm
 connected to a network.

0:07:21.720000 --> 0:07:27.280000
 Now this NIC card is
 enabled for IPV6.

0:07:27.280000 --> 0:07:29.220000
 That's one of the protocols
 that's on it.

0:07:29.220000 --> 0:07:32.920000
 As a matter of fact, all Windows devices
 these days have IPV6 enabled

0:07:32.920000 --> 0:07:34.900000
 on their NIC cards.

0:07:34.900000 --> 0:07:37.800000
 But you're running IPV6.

0:07:37.800000 --> 0:07:41.760000
 So now we know that a NIC card, because
 it's connected to an ethernet

0:07:41.760000 --> 0:07:48.900000
 segment, has a burned in address
 called a MAC address.

0:07:48.900000 --> 0:07:53.100000
 So let's put my MAC
 address on here.

0:07:53.100000 --> 0:07:58.020000
 0 0 0 2 1 1 1 1 2 2 2 2.

0:07:58.020000 --> 0:08:03.160000
 All right, so that's the MAC
 address of this NIC card.

0:08:03.160000 --> 0:08:06.560000
 So the very first thing this NIC card
 has to do once it enables itself

0:08:06.560000 --> 0:08:11.040000
 for IPV6 is it has to create a
 link local address for itself.

0:08:11.040000 --> 0:08:15.780000
 Do you remember, review question, how
 do we recognize link local addresses

0:08:15.780000 --> 0:08:21.580000
 in IPV6? Well hopefully you said, aha,
 those are the addresses that begin

0:08:21.580000 --> 0:08:24.180000
 with FE80. You're
 absolutely right.

0:08:24.180000 --> 0:08:26.280000
 So it will begin with FE80.

0:08:26.280000 --> 0:08:31.960000
 But before I add that, we have to convert
 this into an EUI64 interface

0:08:31.960000 --> 0:08:34.120000
 ID. I'm not going to explain it.

0:08:34.120000 --> 0:08:35.900000
 We already did that
 in a previous video.

0:08:35.900000 --> 0:08:43.140000
 So all I'll say is that my link local
 address will end up being FE80 colon

0:08:43.140000 --> 0:08:53.960000
 colon 0 2 0 2 colon 1 1 F F
 colon FE11 colon 2 2 2 2.

0:08:53.960000 --> 0:08:57.240000
 So that's going to be
 my link local address.

0:08:57.240000 --> 0:09:03.960000
 Starts out with FE80 and then we use
 the EUI64 format to convert this

0:09:03.960000 --> 0:09:06.000000
 into an interface ID.

0:09:06.000000 --> 0:09:11.680000
 Now, one thing I want to make you aware
 of right now, several years back,

0:09:11.680000 --> 0:09:15.740000
 there were some engineers from various
 different disciplines and companies

0:09:15.740000 --> 0:09:23.540000
 who decided that creating an interface
 ID out of a MAC address might be

0:09:23.540000 --> 0:09:27.240000
 kind of a insecure because they said,
 hey, if somebody was monitoring

0:09:27.240000 --> 0:09:30.980000
 your traffic and they always saw the
 exact same interface ID, they could

0:09:30.980000 --> 0:09:32.300000
 track where you were.

0:09:32.300000 --> 0:09:35.040000
 They could say, oh, we can see this guy
 moved around through the building

0:09:35.040000 --> 0:09:37.400000
 throughout the day because
 we can see this link local.

0:09:37.400000 --> 0:09:42.800000
 We can see this interface ID, this
 same interface ID moving around.

0:09:42.800000 --> 0:09:47.400000
 So because just like IP version 4, right,
 when you move from one subnet

0:09:47.400000 --> 0:09:50.780000
 to the other, you get a
 new address via DHCP.

0:09:50.780000 --> 0:09:52.340000
 Well, same thing is
 true with IPV6.

0:09:52.340000 --> 0:09:56.320000
 If I'm sitting in payroll right now,
 I'll have some sort of IPV6 network

0:09:56.320000 --> 0:10:02.540000
 that belongs to payroll, but my interface
 ID will still be based off of

0:10:02.540000 --> 0:10:05.920000
 my MAC address if I'm using EUI64.


0:10:05.920000 --> 0:10:10.120000
 Now, if I pick up my laptop and I go
 over to the marketing department,

0:10:10.120000 --> 0:10:15.640000
 well, now my IPV6 prefix has changed because
 I did DHCP and now I'm sitting

0:10:15.640000 --> 0:10:20.160000
 in their subnet, but my interface
 ID has not changed.

0:10:20.160000 --> 0:10:24.980000
 If it's using EUI64, it is still the
 same because my MAC address goes

0:10:24.980000 --> 0:10:26.840000
 with me wherever I go.

0:10:26.840000 --> 0:10:28.640000
 So some people said, huh?

0:10:28.640000 --> 0:10:31.720000
 Well, that means that if somebody had
 some network monitoring equipment

0:10:31.720000 --> 0:10:35.800000
 set up like in a building or something,
 watching all the packets everywhere,

0:10:35.800000 --> 0:10:37.880000
 they could say, oh, interesting.

0:10:37.880000 --> 0:10:42.840000
 We see the interface
 ID here of Joe.

0:10:42.840000 --> 0:10:45.840000
 It's his MAC address and we see it
 traveling throughout the building.

0:10:45.840000 --> 0:10:50.960000
 Even though the prefix is changing, we
 can track where Joe is going because

0:10:50.960000 --> 0:10:56.380000
 we can see that same interface ID never
 changing as it moves around through

0:10:56.380000 --> 0:11:00.100000
 the network. So these engineers came
 up with a different, I don't know

0:11:00.100000 --> 0:11:03.840000
 what the RFC is, it's not off the top
 of my head, but there's an RFC that's

0:11:03.840000 --> 0:11:08.180000
 been out for a while now that says
 basically when a device dynamically

0:11:08.180000 --> 0:11:12.680000
 comes up with an interface ID, it should
 just be some like random number.

0:11:12.680000 --> 0:11:16.360000
 And it should change it every once in
 a while, like every hour or so it

0:11:16.360000 --> 0:11:18.820000
 should change it so that
 it can't be tracked.

0:11:18.820000 --> 0:11:23.160000
 So the reason I'm saying that to you
 is because if you look at the IPv6

0:11:23.160000 --> 0:11:28.460000
 address on your laptop, chances are
 your interface ID will probably not

0:11:28.460000 --> 0:11:30.860000
 be the EUI64 format.

0:11:30.860000 --> 0:11:33.240000
 It probably will not be related
 to your MAC address.

0:11:33.240000 --> 0:11:36.760000
 It's probably running this newer standard
 that says it needs to be some

0:11:36.760000 --> 0:11:39.280000
 random number that
 changes over time.

0:11:39.280000 --> 0:11:44.760000
 But you do need to know how EUI64 interface
 IDs are created, especially

0:11:44.760000 --> 0:11:46.900000
 on Cisco devices.

0:11:46.900000 --> 0:11:50.660000
 Because it's a keyword that you can
 use on Cisco device and every single

0:11:50.660000 --> 0:11:55.140000
 Cisco device when it creates a link local
 address for itself, it's always

0:11:55.140000 --> 0:11:58.160000
 based off of the EUI64 format.

0:11:58.160000 --> 0:12:02.780000
 Cisco routers and switches, they don't
 use this randomized interface ID

0:12:02.780000 --> 0:12:08.600000
 thing that Microsoft Windows and other
 hosts do, they always use EUI64.

0:12:08.600000 --> 0:12:10.760000
 So, enough said about that.

0:12:10.760000 --> 0:12:14.160000
 So this device right here creates a
 link local address for itself and

0:12:14.160000 --> 0:12:18.820000
 it says, alright, first thing I need
 to do is I need to make sure that

0:12:18.820000 --> 0:12:23.380000
 on this segment there's nobody else
 that's using this exact same link

0:12:23.380000 --> 0:12:26.860000
 local address. I have to make sure
 that there are no duplicates, that

0:12:26.860000 --> 0:12:34.320000
 this is unique. So he'll send out his
 very first type of neighbor discovery

0:12:34.320000 --> 0:12:45.140000
 packet, which is an ICMP V6, we
 call it neighbor solicitation.

0:12:45.140000 --> 0:12:54.420000
 And the source will be his link local
 and the destination, the destination

0:12:54.420000 --> 0:12:58.760000
 will be something called a solicited
 node multicast address.

0:12:58.760000 --> 0:13:03.420000
 Now that is that special type of address
 I have not talked to you about.

0:13:03.420000 --> 0:13:06.780000
 I said there was one remaining address
 that was unique that we hadn't

0:13:06.780000 --> 0:13:08.260000
 talked about, that's it.

0:13:08.260000 --> 0:13:12.140000
 And in the next video I'll talk about
 this, but I want to start out by

0:13:12.140000 --> 0:13:16.780000
 explaining where this special address
 is used and then we can look at

0:13:16.780000 --> 0:13:19.400000
 how is it created.

0:13:19.400000 --> 0:13:24.880000
 So now if anybody did have this link
 local address here, what I will tell

0:13:24.880000 --> 0:13:29.500000
 you is that the solicited node multicast
 address is actually derived from

0:13:29.500000 --> 0:13:35.100000
 this. It's derived from that so that
 if somebody on this wire actually

0:13:35.100000 --> 0:13:39.160000
 did have this exact same link local
 address which is highly unlikely,

0:13:39.160000 --> 0:13:43.740000
 then they would actually listen to
 this packet and they would respond

0:13:43.740000 --> 0:13:52.320000
 back. So hopefully nobody does and
 so he says okay now if somebody did

0:13:52.320000 --> 0:13:56.860000
 respond back, I'm just going
 to, I'm going to erase this.

0:13:56.860000 --> 0:14:03.400000
 Somebody would respond back with
 a neighbor advertisement.

0:14:03.400000 --> 0:14:11.000000
 So that's another part of the neighbor discovery
 process, neighbor solicitation

0:14:11.000000 --> 0:14:13.220000
 and neighbor advertisement.

0:14:13.220000 --> 0:14:16.540000
 But in this particular case we don't
 want to see a neighbor advertisement

0:14:16.540000 --> 0:14:20.380000
 come back because that would mean
 somebody's got our address.

0:14:20.380000 --> 0:14:25.860000
 So this process right now of what we're
 basically sending out a packet

0:14:25.860000 --> 0:14:30.460000
 saying hey is anybody using my address,
 it actually goes by a name that

0:14:30.460000 --> 0:14:31.760000
 you should be familiar with.

0:14:31.760000 --> 0:14:40.840000
 It's called duplicate
 address detection.

0:14:40.840000 --> 0:14:47.340000
 So whenever an IPv6 node either dynamically
 comes up with an address for

0:14:47.340000 --> 0:14:52.140000
 itself or you statically configure
 one on there, it always does this.

0:14:52.140000 --> 0:14:56.000000
 It sends out a neighbor solicitation
 packet basically for itself saying

0:14:56.000000 --> 0:14:58.720000
 hey is anybody out
 there using this.

0:14:58.720000 --> 0:15:04.260000
 Most of the time probably 99.99% of
 the time nothing should come back

0:15:04.260000 --> 0:15:09.080000
 so you have completed the duplicate
 address detection process.

0:15:09.080000 --> 0:15:16.160000
 Okay now this PC says okay great
 I've got a link local address.

0:15:16.160000 --> 0:15:20.220000
 So the next thing he says is I need
 to get a global prefix if I'm ever

0:15:20.220000 --> 0:15:24.520000
 going to get off this link and send
 IPv6 packets to other departments

0:15:24.520000 --> 0:15:26.080000
 or even the Internet.

0:15:26.080000 --> 0:15:29.060000
 I need a global address
 to do that.

0:15:29.060000 --> 0:15:34.020000
 And he says well I've been configured
 for Slack for stateless address

0:15:34.020000 --> 0:15:36.120000
 automatic configuration.

0:15:36.120000 --> 0:15:43.100000
 So what he does is now he sends out
 another type of ICMP message.

0:15:43.100000 --> 0:15:55.360000
 ICMP V6 which is called
 a router solicitation.

0:15:55.360000 --> 0:16:01.260000
 And once again the source is going to
 be his link local and the destination

0:16:01.260000 --> 0:16:07.860000
 is going to be FFO2 colon colon 2.


0:16:07.860000 --> 0:16:12.060000
 Now FF you should be able
 to recognize that.

0:16:12.060000 --> 0:16:14.020000
 That's one of those patterns
 I said you should recognize.

0:16:14.020000 --> 0:16:17.080000
 That is a multicast address.

0:16:17.080000 --> 0:16:20.000000
 And this multicast address
 has special meaning.

0:16:20.000000 --> 0:16:24.900000
 This is called the all
 IPv6 routers multicast.

0:16:24.900000 --> 0:16:30.500000
 So any router that's enabled for IPv6
 is listening for packets going to

0:16:30.500000 --> 0:16:35.760000
 this address. So let's say there is
 a router hopefully there is one.

0:16:35.760000 --> 0:16:38.480000
 Let's put them right here.

0:16:38.480000 --> 0:16:44.580000
 And let's say that on that router's interface
 I have configured the following

0:16:44.580000 --> 0:16:55.060000
 IPv6 address. Okay, so looking at that
 remember how much of an IPv6 address

0:16:55.060000 --> 0:16:58.380000
 is the prefix the network?

0:16:58.380000 --> 0:17:02.960000
 The first 64 bits that's what the subnet
 mask is telling us which is all

0:17:02.960000 --> 0:17:05.980000
 of this right there
 that's the prefix.

0:17:05.980000 --> 0:17:11.540000
 So when this router receives this IP
 this router solicitation message

0:17:11.540000 --> 0:17:15.500000
 he responds back with you
 can preface the network.

0:17:15.500000 --> 0:17:17.760000
 So you probably guess what it is.

0:17:17.760000 --> 0:17:26.940000
 A router advertisement.

0:17:26.940000 --> 0:17:30.840000
 And he sends it back to that node.


0:17:30.840000 --> 0:17:33.940000
 So try to make some room here.

0:17:33.940000 --> 0:17:44.000000
 Destination equals Fe80 colon colon
 0202 colon 11 FF colon Fe11 colon

0:17:44.000000 --> 0:17:47.560000
 2222. So it's going
 back to that host.

0:17:47.560000 --> 0:17:54.420000
 And the source is see if
 I can fit it in here.

0:17:54.420000 --> 0:18:00.000000
 The routers link local address.

0:18:00.000000 --> 0:18:03.000000
 Because this router also has one.

0:18:03.000000 --> 0:18:13.080000
 So whatever his link local address
 is that is what the source of this

0:18:13.080000 --> 0:18:15.900000
 will be. And here's
 the great thing.

0:18:15.900000 --> 0:18:21.860000
 Inside this router advertisement in
 the body of it he says hey let me

0:18:21.860000 --> 0:18:30.620000
 tell you what prefixes I
 have on this interface.

0:18:30.620000 --> 0:18:35.620000
 Now that the host sees that that router
 advertisement he says oh very

0:18:35.620000 --> 0:18:39.440000
 cool I know what the global prefixes
 that lives on this wire.

0:18:39.440000 --> 0:18:43.600000
 So I can use stateless address automatic
 configuration to come up with

0:18:43.600000 --> 0:18:46.260000
 my own global address.

0:18:46.260000 --> 0:18:49.540000
 I'll just use that because after all
 that's what the router is using and

0:18:49.540000 --> 0:18:52.840000
 I got to be on the same
 thing as the router.

0:18:52.840000 --> 0:18:59.600000
 And then I will use the same interface
 ID that I got in my link local

0:18:59.600000 --> 0:19:03.020000
 just do the EUI64 process again.

0:19:03.020000 --> 0:19:05.660000
 Which will end up with
 the same thing.

0:19:05.660000 --> 0:19:14.740000
 And then once he has this he will do
 duplicate address detection on this

0:19:14.740000 --> 0:19:18.100000
 he'll send out a neighbor solicitation
 message for this.

0:19:18.100000 --> 0:19:23.380000
 Shouldn't hear anything back and
 now he knows that is unique.

0:19:23.380000 --> 0:19:28.820000
 So this is how stateless address automatic
 configuration works or address

0:19:28.820000 --> 0:19:32.940000
 auto config. Basically you got to come
 up with a link local address for

0:19:32.940000 --> 0:19:36.980000
 yourself first. Verify that there's
 no duplicates by sending a neighbor

0:19:36.980000 --> 0:19:39.760000
 solicitation message to
 yourself essentially.

0:19:39.760000 --> 0:19:45.500000
 Then you send out a router solicitation
 to this reserved address of FF02

0:19:45.500000 --> 0:19:48.980000
 colon colon 2. All routers are
 supposed to listen to that.

0:19:48.980000 --> 0:19:53.080000
 When the router hears it he sends
 a router advertisement back.

0:19:53.080000 --> 0:19:57.440000
 He sends it to you your link local address
 and in the body of that message

0:19:57.440000 --> 0:20:00.520000
 he says here's the global prefix
 that everybody on this wire.

0:20:00.520000 --> 0:20:03.620000
 Here's the group that you're
 a part of the subnet.

0:20:03.620000 --> 0:20:09.000000
 And now the PC can use that prefix
 once again create his own interface

0:20:09.000000 --> 0:20:14.280000
 ID and now he has a global prefix that
 he can use to speak to the rest

0:20:14.280000 --> 0:20:20.600000
 of the world. Now there is one other
 there's a couple of additional things

0:20:20.600000 --> 0:20:22.600000
 about this here that
 I want to talk about.

0:20:22.600000 --> 0:20:28.060000
 This address is special we
 put a red circle around it.

0:20:28.060000 --> 0:20:30.720000
 Definitely want to memorize that.

0:20:30.720000 --> 0:20:38.460000
 And every single IPv6 host is also listening
 to another special multicast

0:20:38.460000 --> 0:20:44.120000
 address. I'll write that
 on the bottom I suppose.

0:20:44.120000 --> 0:20:50.080000
 That would be FF02 colon colon 1.

0:20:50.080000 --> 0:20:55.360000
 That is the all IPv6
 hosts address.

0:20:55.360000 --> 0:20:57.480000
 And the router is
 listening to that.

0:20:57.480000 --> 0:21:05.360000
 So actually this router is listening
 to four addresses.

0:21:05.360000 --> 0:21:07.840000
 The router's got his link local.

0:21:07.840000 --> 0:21:11.580000
 He's listening to anybody who wants
 to talk to him on his global prefix.

0:21:11.580000 --> 0:21:14.580000
 He's listening to anybody who wants to
 send something to him specifically

0:21:14.580000 --> 0:21:16.160000
 as just a generic router.

0:21:16.160000 --> 0:21:19.480000
 And he is considered a host.

0:21:19.480000 --> 0:21:23.380000
 Any nikcard that has IPv6 on is considered
 a host so he's listening to

0:21:23.380000 --> 0:21:25.180000
 the all hosts address.

0:21:25.180000 --> 0:21:35.100000
 So everybody at minimum at minimum
 devices are listening to three IPv6

0:21:35.100000 --> 0:21:41.880000
 addresses. They're link local the all
 hosts address and the solicited

0:21:41.880000 --> 0:21:43.600000
 node multicast address.

0:21:43.600000 --> 0:21:46.340000
 Now I know that I haven't defined
 that one for you yet.

0:21:46.340000 --> 0:21:48.240000
 That'll be in the next video.

0:21:48.240000 --> 0:21:52.480000
 But every device has a solicited
 node multicast address.

0:21:52.480000 --> 0:21:55.940000
 And that's derived from
 the link local address.

0:21:55.940000 --> 0:22:00.720000
 And they're also listening to the
 all hosts multicast address.

0:22:00.720000 --> 0:22:04.420000
 Now whether or not they have a global
 prefix they may or they may not.

0:22:04.420000 --> 0:22:07.740000
 I mean if they want to get off of their
 subnet they're going to need one

0:22:07.740000 --> 0:22:10.940000
 but it's not mandatory.

0:22:10.940000 --> 0:22:15.400000
 And routers also listen to this other
 special address of the all IPv6

0:22:15.400000 --> 0:22:16.620000
 routers address.

