WEBVTT

0:00:08.400000 --> 0:00:12.940000
 So the title of this video I recognize
 looks a little strange, ARP and

0:00:12.940000 --> 0:00:15.040000
 the IPv6 solution.

0:00:15.040000 --> 0:00:19.760000
 But in order for me to really talk
 about the solicited node multicast

0:00:19.760000 --> 0:00:23.800000
 address, we first have to understand
 something that happens in a world

0:00:23.800000 --> 0:00:29.640000
 of IP version 4, which is called ARP
 or the address resolution protocol.

0:00:29.640000 --> 0:00:33.640000
 Haven't really discussed it up until
 now, but we need to understand this

0:00:33.640000 --> 0:00:39.180000
 so that the solicited node multicast
 address will make some more sense.

0:00:39.180000 --> 0:00:42.920000
 So let's go back to our whiteboard
 here for a moment.

0:00:42.920000 --> 0:00:50.400000
 Let's assume that this
 is your laptop.

0:00:50.400000 --> 0:00:54.340000
 This is you. This is
 you on a network.

0:00:54.340000 --> 0:01:00.840000
 And here is the laptop
 connected to a router.

0:01:00.840000 --> 0:01:05.300000
 And somewhere on here
 was a DHCP server.

0:01:05.300000 --> 0:01:08.780000
 Usually the DHCP server is not actually
 on your wire, but just to make

0:01:08.780000 --> 0:01:13.100000
 the drawing a little bit easier,
 I'm going to do it.

0:01:13.100000 --> 0:01:20.580000
 Okay, so the router has a network interface
 card, an ethernet NIC, just

0:01:20.580000 --> 0:01:23.500000
 like you have an ethernet NIC.

0:01:23.500000 --> 0:01:30.860000
 And his ethernet NIC has a MAC address on
 it that was created by the manufacturer.

0:01:30.860000 --> 0:01:37.860000
 Let's say the MAC address
 is 0011222333.

0:01:37.860000 --> 0:01:42.380000
 And because he's a router, we've statically
 configured an IP address on

0:01:42.380000 --> 0:01:48.200000
 him. 222 slash 24.

0:01:48.200000 --> 0:01:55.300000
 Okay, now your Mac, your your net
 card also has a MAC address on it.

0:01:55.300000 --> 0:01:57.320000
 Every net card does.

0:01:57.320000 --> 0:01:59.740000
 Let's say that's yours.

0:01:59.740000 --> 0:02:13.420000
 And let's say after doing the DHCP
 process and obtaining an DHCP, you

0:02:13.420000 --> 0:02:17.180000
 learn that your default
 gateway was 2.2.2.

0:02:17.180000 --> 0:02:22.300000
 So you learned all this via DHCP.

0:02:22.300000 --> 0:02:31.460000
 Okay, statistics show that when comparing
 the when a laptop creates traffic

0:02:31.460000 --> 0:02:35.860000
 or a tablet or a smartphone, people
 have done studies trying to answer

0:02:35.860000 --> 0:02:41.640000
 the question, what percentage of traffic
 that a laptop creates is destined

0:02:41.640000 --> 0:02:44.600000
 for its own local subnet?

0:02:44.600000 --> 0:02:48.700000
 And what percentage of traffic is destined
 for other subnets or the rest

0:02:48.700000 --> 0:02:53.200000
 of the world? And most
 of the time it's 2080.

0:02:53.200000 --> 0:02:58.460000
 In other words, roughly 20% of the traffic
 that you generate is for your

0:02:58.460000 --> 0:03:00.260000
 own local network.

0:03:00.260000 --> 0:03:04.220000
 And 80% of the traffic is going
 out to the rest of the world.

0:03:04.220000 --> 0:03:08.900000
 So we know that this PC right here at
 some point, he's going to want to

0:03:08.900000 --> 0:03:12.380000
 bring up a web page or he's going to
 want to open up his email program.

0:03:12.380000 --> 0:03:16.720000
 He's going to open up something where
 he's going to want to send a packet

0:03:16.720000 --> 0:03:18.500000
 to the outside world.

0:03:18.500000 --> 0:03:22.500000
 So let's say the PC does
 something like this.

0:03:22.500000 --> 0:03:26.020000
 So here's a little thought
 bubble from the PC.

0:03:26.020000 --> 0:03:35.380000
 And he says, I want to go to the
 website that is at 7.7.7.7.

0:03:35.380000 --> 0:03:39.740000
 That is not on my own subnet.

0:03:39.740000 --> 0:03:43.540000
 Because remember, he always says a comparison
 of his source address and

0:03:43.540000 --> 0:03:45.780000
 the destination of where
 he wants to go.

0:03:45.780000 --> 0:03:48.680000
 In this case, he's saying,
 okay, that's not me.

0:03:48.680000 --> 0:03:50.020000
 That's not here.

0:03:50.020000 --> 0:03:55.900000
 He says, okay, well, I'm going
 to create my packet anyway.

0:03:55.900000 --> 0:03:57.280000
 He says, okay, here we go.

0:03:57.280000 --> 0:03:59.120000
 Here's my IP packet.

0:03:59.120000 --> 0:04:05.480000
 And the source of the IP
 packet is going to be me.

0:04:05.480000 --> 0:04:11.680000
 2.2.1. Destination is
 going to be 7.7.7.7.

0:04:11.680000 --> 0:04:22.560000
 Okay. And they says, when I send that
 down to the and Ethernet frame has

0:04:22.560000 --> 0:04:26.440000
 a source and destination Mac, he says,
 all right, well, the source Mac,

0:04:26.440000 --> 0:04:27.080000
 that's pretty easy.

0:04:27.080000 --> 0:04:36.880000
 That's mine. And the destination is,
 huh, well, he says, I know that when

0:04:36.880000 --> 0:04:40.520000
 I create an Ethernet frame, the destination
 of the frame has to be somebody

0:04:40.520000 --> 0:04:44.260000
 on my wire, on my wire.

0:04:44.260000 --> 0:04:48.980000
 And he says, but ultimately the person
 I'm trying to reach is not on my

0:04:48.980000 --> 0:04:51.060000
 wire. They're not in my subnet.

0:04:51.060000 --> 0:04:56.020000
 And so the PC says, well, is there
 anybody on my wire that might know

0:04:56.020000 --> 0:04:57.440000
 how to get here?

0:04:57.440000 --> 0:04:59.940000
 Oh, yeah, the router.

0:04:59.940000 --> 0:05:02.700000
 That's why I have him in the first
 place, the default gateway.

0:05:02.700000 --> 0:05:07.620000
 So he says, what I should do is at layer
 two, I should destined my Ethernet

0:05:07.620000 --> 0:05:10.800000
 Mac address to the Mac
 address of the router.

0:05:10.800000 --> 0:05:13.800000
 That way the router will pick
 up this Ethernet frame.

0:05:13.800000 --> 0:05:16.880000
 And when he sends it up the stack to
 the networking layer, then he'll

0:05:16.880000 --> 0:05:21.220000
 realize that it's a packet that's not
 for him that needs to be routed.

0:05:21.220000 --> 0:05:23.840000
 He says, but, huh, interesting.

0:05:23.840000 --> 0:05:29.060000
 I know the router's IP address, but
 I don't know his layer two address.

0:05:29.060000 --> 0:05:32.160000
 How am I going to resolve
 that address?

0:05:32.160000 --> 0:05:35.600000
 That's where we, where he kicks in and
 uses something called the address

0:05:35.600000 --> 0:05:39.260000
 resolution protocol, ARP.

0:05:39.260000 --> 0:05:41.440000
 And this is what ARP
 was designed to do.

0:05:41.440000 --> 0:05:45.360000
 When you know the layer three address
 of someone in your subnet, and that's

0:05:45.360000 --> 0:05:48.360000
 the key, it's ARP is only used when
 you're trying to resolve someone in

0:05:48.360000 --> 0:05:53.920000
 your subnet. For example, he would never
 ARP for 777 because that device

0:05:53.920000 --> 0:05:56.460000
 is clearly not on this wire.

0:05:56.460000 --> 0:05:58.960000
 So when you're trying to reach someone
 in your subnet and you know their

0:05:58.960000 --> 0:06:04.940000
 layer three address, but you don't know
 their layer two Mac address, this

0:06:04.940000 --> 0:06:07.440000
 is where we use ARP.

0:06:07.440000 --> 0:06:10.500000
 So with ARP, it would
 look like this.

0:06:10.500000 --> 0:06:12.960000
 This packet would be put on hold.

0:06:12.960000 --> 0:06:15.900000
 You'd have to put it in memory
 and store it memory.

0:06:15.900000 --> 0:06:20.700000
 And he would create what's
 called an ARP request.

0:06:20.700000 --> 0:06:23.380000
 And the source would be himself.

0:06:23.380000 --> 0:06:30.240000
 And the destination would be the
 router he's trying to talk to.

0:06:30.240000 --> 0:06:35.520000
 All right. And an ARP request actually
 has a few more fields than that,

0:06:35.520000 --> 0:06:37.380000
 but we'll just keep it simple.

0:06:37.380000 --> 0:06:42.060000
 And then he would create
 his layer two header.

0:06:42.060000 --> 0:06:46.100000
 And the source of his layer
 two header would be himself.

0:06:46.100000 --> 0:06:51.040000
 0011 colon 333 colon
 four four four four.

0:06:51.040000 --> 0:06:56.640000
 And the destination would
 be a broadcast.

0:06:56.640000 --> 0:07:04.840000
 And a broadcast Mac address is all
 ones or FFFF in hexadecimal.

0:07:04.840000 --> 0:07:06.760000
 So that is a special Mac address.

0:07:06.760000 --> 0:07:11.500000
 That is the broadcast Mac addresses
 for everybody on the wire.

0:07:11.500000 --> 0:07:15.780000
 And that's what the layer
 two frame would look like.

0:07:15.780000 --> 0:07:19.320000
 And then when the and so everybody
 on the wire would see it, everybody

0:07:19.320000 --> 0:07:21.280000
 would say, Oh, this is for me.

0:07:21.280000 --> 0:07:24.520000
 But when everybody stripped off this
 layer two header, revealing what

0:07:24.520000 --> 0:07:28.700000
 was behind it, they would recognize,
 Oh, this isn't for me, except the

0:07:28.700000 --> 0:07:32.380000
 router. The router would say, Oh, somebody
 is request somebody sending

0:07:32.380000 --> 0:07:34.140000
 an ARP request to me.

0:07:34.140000 --> 0:07:37.420000
 All right. Guess what he's
 going to respond send back.

0:07:37.420000 --> 0:07:39.620000
 He's going to send I'm not
 going to draw it here.

0:07:39.620000 --> 0:07:41.320000
 I'm just going to write
 the name of it.

0:07:41.320000 --> 0:07:46.080000
 He would send back
 an ARP response.

0:07:46.080000 --> 0:07:51.320000
 And in that response, he would
 say, I am two, two, two, two.

0:07:51.320000 --> 0:07:58.460000
 My Mac is 0011, two, two, two, two,
 three, three, three, three.

0:07:58.460000 --> 0:08:03.300000
 So what we need when we know someone's
 layer three address who is in our

0:08:03.300000 --> 0:08:07.240000
 subnet, but we don't know their layer
 two address and we need to talk

0:08:07.240000 --> 0:08:09.540000
 to them, this is the process.

0:08:09.540000 --> 0:08:13.200000
 We send out a broadcast to everybody
 called an ARP request.

0:08:13.200000 --> 0:08:16.120000
 But inside the body of that packet, we
 say, Hey, this is the guy I'm actually

0:08:16.120000 --> 0:08:21.720000
 looking for. And if that guy actually
 exists, he sends back an ARP response

0:08:21.720000 --> 0:08:25.320000
 directly to us, giving
 us his Mac address.

0:08:25.320000 --> 0:08:28.760000
 And now that the Mac address is known,
 this packet, which has been waiting

0:08:28.760000 --> 0:08:33.540000
 forever up here to go the web server,
 we can now actually address it at

0:08:33.540000 --> 0:08:38.160000
 layer two to the router.

0:08:38.160000 --> 0:08:40.080000
 And away it goes.

0:08:40.080000 --> 0:08:42.960000
 Now the laptop can put
 this on the wire.

0:08:42.960000 --> 0:08:45.180000
 The router at layer two
 will think it's for him.

0:08:45.180000 --> 0:08:46.360000
 So he will pick it up.

0:08:46.360000 --> 0:08:49.160000
 Everybody else on this
 wire will ignore it.

0:08:49.160000 --> 0:08:52.880000
 And then when the router strips off
 the layer two header, he'll see this

0:08:52.880000 --> 0:08:55.460000
 and recognize that's not for him.

0:08:55.460000 --> 0:09:00.320000
 Now what in the world does this
 have to do with IPV six?

0:09:00.320000 --> 0:09:03.820000
 And why is this grouped in
 with the IPV six videos?

0:09:03.820000 --> 0:09:08.140000
 The reason I want to bring this up is
 because this is a classic case in

0:09:08.140000 --> 0:09:12.420000
 the world of IP version four
 of usage of a broadcast.

0:09:12.420000 --> 0:09:16.400000
 In IP version four, there's a lot of
 things that go out as broadcast.

0:09:16.400000 --> 0:09:18.380000
 ARP requests are one of them.

0:09:18.380000 --> 0:09:22.260000
 You see ARP requests all the time,
 all day long on networks.

0:09:22.260000 --> 0:09:23.600000
 ARP requests go out as broadcast.

0:09:23.600000 --> 0:09:33.440000
 And there's a lot of other stuff that
 goes out as where the laptop would

0:09:33.440000 --> 0:09:37.920000
 say, I know the IPV six address of
 my router, what I don't know is his

0:09:37.920000 --> 0:09:41.760000
 MAC address. You might be tempted to
 think, Oh, well, there must be an

0:09:41.760000 --> 0:09:46.040000
 ARP V six. And there's where
 your mistake would be.

0:09:46.040000 --> 0:09:51.140000
 There is no such thing as ARP
 in the world of IPV six.

0:09:51.140000 --> 0:09:54.480000
 As a matter of fact, when I was showing
 you all those different types

0:09:54.480000 --> 0:10:00.240000
 of IPV six messages, link local, global,
 site local, did I ever show you

0:10:00.240000 --> 0:10:03.120000
 an IPV six address that
 was a broadcast address?

0:10:03.120000 --> 0:10:07.580000
 No, I didn't because
 they don't exist.

0:10:07.580000 --> 0:10:12.020000
 There's no such thing as a broadcast
 address in the world of IPV six.

0:10:12.020000 --> 0:10:14.800000
 So think about that for a second.

0:10:14.800000 --> 0:10:20.060000
 In this case, we needed to figure
 out what his MAC address was.

0:10:20.060000 --> 0:10:25.260000
 And since we didn't know it, we and
 we had to create an ethernet frame.

0:10:25.260000 --> 0:10:28.360000
 And an ethernet frame requires
 a destination MAC address.

0:10:28.360000 --> 0:10:30.260000
 But we didn't know the destination
 MAC address.

0:10:30.260000 --> 0:10:30.960000
 So what do we do?

0:10:30.960000 --> 0:10:32.500000
 We just broadcast it.

0:10:32.500000 --> 0:10:34.960000
 So how is IPV six
 going to do this?

0:10:34.960000 --> 0:10:40.020000
 If there's no such thing as a broadcast,
 this is where that solicited

0:10:40.020000 --> 0:10:44.120000
 node multicast address
 comes into play.

0:10:44.120000 --> 0:11:05.000000
 So I'm going to do is I'm going
 to replace it with IPV six.

0:11:05.000000 --> 0:11:10.640000
 Okay, so here we are.

0:11:10.640000 --> 0:11:12.920000
 Now let's go ahead and replace
 some of this stuff.

0:11:12.920000 --> 0:11:22.740000
 Okay. So let's say that the router now
 has, I'm going to give him a really

0:11:22.740000 --> 0:11:27.240000
 small IPV six and dense it down.

0:11:27.240000 --> 0:11:32.320000
 Two zero zero one colon colon one.


0:11:32.320000 --> 0:11:38.920000
 So most of the bits in his
 128-bit address are zeros.

0:11:38.920000 --> 0:11:41.880000
 And we also know he's going to
 have a link local address.

0:11:41.880000 --> 0:11:46.840000
 Let's just make that
 simple as well.

0:11:46.840000 --> 0:11:52.660000
 And we know he's listening to the all
 routers address, which is that.

0:11:52.660000 --> 0:11:58.500000
 And we know he's listening
 which is that.

0:11:58.500000 --> 0:12:04.040000
 Okay. Now there's another address
 that he's listening to.

0:12:04.040000 --> 0:12:09.080000
 Let me change his link local
 just a little bit.

0:12:09.080000 --> 0:12:22.880000
 F E 80 colon colon zero zero one one
 one F F E two three four four four

0:12:22.880000 --> 0:12:23.840000
 four. All right.

0:12:23.840000 --> 0:12:26.480000
 So let's say that this is his link
 local address and this was derived

0:12:26.480000 --> 0:12:28.280000
 from his MAC address.

0:12:28.280000 --> 0:12:36.000000
 For every interface ID that
 he has that's unique to him.

0:12:36.000000 --> 0:12:38.760000
 So right now he actually has
 two interface IDs doesn't he?

0:12:38.760000 --> 0:12:42.380000
 Um, actually if I derived it from his
 MAC, I actually probably should

0:12:42.380000 --> 0:12:56.720000
 have looked at E two two
 three three three three.

0:12:56.720000 --> 0:13:00.620000
 There we go. Okay, because this is actually
 derived off of his real MAC

0:13:00.620000 --> 0:13:01.760000
 address right there.

0:13:01.760000 --> 0:13:06.020000
 I just used EUI 64 to
 come up with that.

0:13:06.020000 --> 0:13:12.040000
 And just to make things simple, let's
 just say that, um, that his global

0:13:12.040000 --> 0:13:14.560000
 prefix is just like that too.

0:13:14.560000 --> 0:13:20.300000
 Zero two one one two two F F F E.

0:13:20.300000 --> 0:13:24.440000
 I guess I can do it over here.

0:13:24.440000 --> 0:13:31.940000
 Okay, this makes it easy because now
 we've used his MAC address in the

0:13:31.940000 --> 0:13:36.360000
 interface ID of both his global prefix
 as well as his link local prefix.

0:13:36.360000 --> 0:13:40.040000
 Okay, so every device does this.

0:13:40.040000 --> 0:13:42.520000
 I'm just going to focus on the router
 for a moment, but then we'll see

0:13:42.520000 --> 0:13:44.460000
 how the laptop does this as well.

0:13:44.460000 --> 0:13:49.960000
 So the router once he comes up with
 an interface ID, he also comes up

0:13:49.960000 --> 0:13:57.140000
 with a special address called a solicited
 node multicast address.

0:13:57.140000 --> 0:14:00.000000
 And you can see here this one
 is a nightmare to remember.

0:14:00.000000 --> 0:14:01.720000
 Look how long that that pattern.

0:14:01.720000 --> 0:14:02.480000
 Good luck with that.

0:14:02.480000 --> 0:14:04.020000
 You're going to have to
 memorize that pattern.

0:14:04.020000 --> 0:14:08.060000
 But it's a hundred and four bit
 pattern that never changes.

0:14:08.060000 --> 0:14:19.080000
 And the last 24 bits because
 it so based on this.

0:14:19.080000 --> 0:14:26.780000
 Here's how he's going to come up with
 a solicited node multicast address.

0:14:26.780000 --> 0:14:28.440000
 I'm going to get rid
 of the DHCP server.

0:14:28.440000 --> 0:14:30.900000
 So I have a little bit
 of room here to write.

0:14:30.900000 --> 0:14:35.120000
 And I'll put this in green to
 make a little bit different.

0:14:35.120000 --> 0:14:43.980000
 So it's going to be F F zero
 two colon colon one colon.

0:14:43.980000 --> 0:14:47.560000
 So the last 24 bits.

0:14:47.560000 --> 0:14:48.580000
 So let's see here.

0:14:48.580000 --> 0:14:52.380000
 I'm going to put a red line under the
 last 24 bits of the interface ID.

0:14:52.380000 --> 0:14:54.900000
 So there's 16 bits.

0:14:54.900000 --> 0:14:59.140000
 There's 20. There's
 24 right there.

0:14:59.140000 --> 0:15:02.700000
 So those are the last 24 bits because
 remember it said right here after

0:15:02.700000 --> 0:15:06.800000
 this pattern right here the remaining
 24 bits are taken from the interface

0:15:06.800000 --> 0:15:09.640000
 ID. So I've already started
 that pattern.

0:15:09.640000 --> 0:15:10.920000
 I shortened my zeros.

0:15:10.920000 --> 0:15:15.140000
 I used colon colon for
 the zeros right there.

0:15:15.140000 --> 0:15:18.020000
 And I got to put in the F F.

0:15:18.020000 --> 0:15:26.780000
 And then the rest of it
 I'll put in in blue.

0:15:26.780000 --> 0:15:37.120000
 Okay. So that is the solicited
 node multicast address.

0:15:37.120000 --> 0:15:41.040000
 Now let's go over to
 this laptop here.

0:15:41.040000 --> 0:15:47.700000
 Here he creates his IPV
 six link local address.

0:15:47.700000 --> 0:15:55.860000
 So that's going to be F E 80 colon
 colon zero two one one colon three

0:15:55.860000 --> 0:16:04.800000
 three F F colon F E four four colon uh
 no F E three three colon four four

0:16:04.800000 --> 0:16:09.280000
 four four. Okay and I've already
 explained how that's derived.

0:16:09.280000 --> 0:16:15.680000
 And so now he says okay duplicate address
 detection you know send out

0:16:15.680000 --> 0:16:18.840000
 a neighbor solicitation making
 sure that nobody else has that.

0:16:18.840000 --> 0:16:21.100000
 Great. Nobody's got it.

0:16:21.100000 --> 0:16:35.120000
 And they says okay so now so I
 CMP V six router solicitation.

0:16:35.120000 --> 0:16:38.480000
 So let's solicitation.

0:16:38.480000 --> 0:16:39.420000
 Yeah I got that right there.

0:16:39.420000 --> 0:16:46.060000
 So the source is going to be his F E
 80 F E 80 colon colon zero two one

0:16:46.060000 --> 0:17:00.140000
 one three three F F F E three three
 four four four and I'm sort of zero

0:17:00.140000 --> 0:17:03.880000
 two colon colon two.

0:17:03.880000 --> 0:17:10.260000
 So that is my router solicitation router
 gets that router responds back.

0:17:10.260000 --> 0:17:14.960000
 Now he uses his link local address
 as the source F E 80 responds back

0:17:14.960000 --> 0:17:20.140000
 to this guy's link locally says hey
 buddy I'm using the 2001 prefix.

0:17:20.140000 --> 0:17:25.280000
 So laptop says oh okay great then let
 me go ahead and configure myself

0:17:25.280000 --> 0:17:32.680000
 with 2001 and then I'll use the exact
 same interface ID that I did before

0:17:32.680000 --> 0:17:40.960000
 slash 64. He does duplicate
 address detection for that.

0:17:40.960000 --> 0:17:59.860000
 Okay now now he says okay let's put
 the website at 2001 let's say 2004

0:17:59.860000 --> 0:18:04.760000
 4444 colon colon one.

0:18:04.760000 --> 0:18:08.840000
 That's not on my subnet.

0:18:08.840000 --> 0:18:15.720000
 He says okay same thing as before right
 here he said okay when it's not

0:18:15.720000 --> 0:18:20.320000
 on my subnet I need to go to my router
 but hmm didn't know the MAC address

0:18:20.320000 --> 0:18:24.100000
 of my router so what did I do in IP
 version four I sent out a broadcast

0:18:24.100000 --> 0:18:29.480000
 called an ARP request the router got
 it sent an ARP response back and

0:18:29.480000 --> 0:18:32.080000
 that's how I learned about the
 MAC address of the router.

0:18:32.080000 --> 0:18:39.440000
 In IPV6 we send out and I don't know
 if I have enough room here for this

0:18:39.440000 --> 0:18:46.400000
 an ICMPV6 neighbor solicitation.

0:18:46.400000 --> 0:18:55.900000
 And so here we go source is going to
 be his link local and the destination

0:18:55.900000 --> 0:19:01.900000
 is going to be the solicited node
 multicast address of the router.

0:19:01.900000 --> 0:19:11.720000
 Now you might be wondering well wait
 a second let me put this in a box

0:19:11.720000 --> 0:19:19.300000
 here if I can squeeze it all in you
 might be wondering okay I understand

0:19:19.300000 --> 0:19:24.060000
 how when the PC sent the solicit the
 neighbor solicitation I understand

0:19:24.060000 --> 0:19:29.680000
 how he knew about this part because that's
 standard everybody knows about

0:19:29.680000 --> 0:19:35.880000
 that but how did he come up with the
 last 24 bits well remember remember

0:19:35.880000 --> 0:19:40.340000
 when he sent out a router solicitation
 to the all routers address and

0:19:40.340000 --> 0:19:45.900000
 he got a router advertisement back
 what was the source so let me just

0:19:45.900000 --> 0:19:51.020000
 write that up here just to refresh your
 memory so initially he sent out

0:19:51.020000 --> 0:20:00.680000
 a router solicitation to the all IPV6
 routers address and then he got

0:20:00.680000 --> 0:20:08.920000
 back a router advertisement now what
 did I say was the source of that

0:20:08.920000 --> 0:20:13.860000
 router advertisement I said it was the
 link local address of the router

0:20:13.860000 --> 0:20:20.840000
 FE80 colon colon 0211 I'm kind of running
 out of room here but it was

0:20:20.840000 --> 0:20:29.220000
 this well remember how we said the interface
 ID here was used to create

0:20:29.220000 --> 0:20:33.780000
 the solicited node multicast address
 so just like the router was able

0:20:33.780000 --> 0:20:40.960000
 to create that for himself the host
 the PC said okay I now know what the

0:20:40.960000 --> 0:20:44.740000
 router's link local address is because
 he responded to me with a router

0:20:44.740000 --> 0:20:51.000000
 advertisement so I know that he is listening
 to a solicited node multicast

0:20:51.000000 --> 0:20:55.540000
 address that was derived from this
 and that's how he was able to come

0:20:55.540000 --> 0:20:59.880000
 up with that himself as a matter of
 fact the laptop also heads create

0:20:59.880000 --> 0:21:03.460000
 a solicited node multicast address
 I'll see if I can have room up here

0:21:03.460000 --> 0:21:09.900000
 to do that so the laptop he said all
 right my solicited node just in case

0:21:09.900000 --> 0:21:14.360000
 anybody ever needs to resolve me and
 figure out what my MAC address is

0:21:14.360000 --> 0:21:30.400000
 is 334444 remember it was the last 24
 bits after that static pattern it

0:21:30.400000 --> 0:21:38.120000
 was the last 24 bits of the interface
 ID that was put in here so every

0:21:38.120000 --> 0:21:44.600000
 device comes up with a link local address
 for itself and a solicited node

0:21:44.600000 --> 0:21:50.600000
 multicast address for itself and if anybody
 ever needs to arp for it well

0:21:50.600000 --> 0:21:54.600000
 there is no arp in the world of IPV6
 but there is neighbor solicitation

0:21:54.600000 --> 0:22:00.680000
 and they were they will send a neighbor
 solicitation to your solicited

0:22:00.680000 --> 0:22:05.680000
 node multicast address which is what
 you're listening for and then the

0:22:05.680000 --> 0:22:11.720000
 router in turn will respond back this
 is the final piece he'll respond

0:22:11.720000 --> 0:22:26.780000
 back with a neighbor advertisement
 and that is how this PC will learn

0:22:26.780000 --> 0:22:31.700000
 of the MAC address of the router so
 to recap in the world of IP version

0:22:31.700000 --> 0:22:35.980000
 4 to learn someone's MAC address who's
 on your same wire you sent out

0:22:35.980000 --> 0:22:42.060000
 an arp request and you got back an arp
 response in the world of IPV6 you

0:22:42.060000 --> 0:22:52.220000
 send out a neighbor solicitation and you
 get a lot of protocols use broadcasts

0:22:52.220000 --> 0:22:59.660000
 in the world of IP version 6 there is
 no broadcast if you absolutely must

0:22:59.660000 --> 0:23:04.880000
 talk to everybody who is on your wire
 you send a packet to this address

0:23:04.880000 --> 0:23:11.120000
 the all IPV6 nodes address that's that's
 basically the equivalent of a

0:23:11.120000 --> 0:23:15.700000
 broadcast even though it's a multicast
 everybody's listening to it but

0:23:15.700000 --> 0:23:20.460000
 usually we don't send stuff to that we
 send stuff either to the all routers

0:23:20.460000 --> 0:23:24.960000
 address or we send it to their solicited
 node multicast address or to

0:23:24.960000 --> 0:23:29.020000
 their link local address so I know
 there's a lot of addresses here in

0:23:29.020000 --> 0:23:32.420000
 IPV6 and that's just something you're
 gonna have to go over and over and

