1
00:00:01,080 --> 00:00:09,370
So let's power on the P.C. and open up a console and see if it now receives an IP address.

2
00:00:09,470 --> 00:00:13,620
So I have config eith zero.

3
00:00:13,670 --> 00:00:15,120
Notice the difference.

4
00:00:15,170 --> 00:00:20,340
It's now received a global IP address.

5
00:00:20,420 --> 00:00:28,380
2001 Cole on Face the network portion is that followed by some zeros.

6
00:00:28,390 --> 00:00:35,680
This is the host portion which you'll notice is the same as the link local host portion and is based

7
00:00:35,680 --> 00:00:37,620
on the MAC address of the host.

8
00:00:38,470 --> 00:00:39,910
So back in wire shock

9
00:00:42,800 --> 00:00:50,520
there are the right advertisements we saw previously and scrolling down we see a rather solicitation

10
00:00:50,520 --> 00:00:53,550
message to f f 0 2.

11
00:00:53,560 --> 00:00:54,880
Colon colon 2.

12
00:00:55,260 --> 00:01:06,150
From a host with a MAC address ending in 6 a 4 b center this year 6 a 4 B going to all routers on the

13
00:01:06,150 --> 00:01:08,140
local segment.

14
00:01:08,340 --> 00:01:16,100
There's the MAC address which is the layer to MAC address for IP version 6 multi costs.

15
00:01:16,280 --> 00:01:27,770
In this case for f f 0 2 colon colon 2 and we can see that the multicast was sent from this host.

16
00:01:27,940 --> 00:01:37,510
There is the link local address as shown here in y shock so the host is sending a rider solicitation

17
00:01:38,520 --> 00:01:44,990
to all riders in the local segment and the rider replies back to all hosts on the local segment.

18
00:01:45,120 --> 00:01:54,930
There is the IP version 6 multicast address from the broader to the IP version 6 multicast layer to

19
00:01:54,930 --> 00:02:04,670
address sources the rider destination is FFA 0 2 Collin Collin 1 it's a run advertisement and the rider

20
00:02:04,670 --> 00:02:11,670
is once again telling the host it's local MAC address there is the link layer address.

21
00:02:11,750 --> 00:02:16,590
Here's the empty you man here is the IP version 6 prefects.

22
00:02:16,880 --> 00:02:25,480
So the host has dynamically learnt this address so that was an example of slack what I'll do now is

23
00:02:25,540 --> 00:02:39,130
add another address on the Rada so let's call this 2001 on 0 1 0 1 so at an address

24
00:02:41,840 --> 00:02:48,490
like this and let's see if the Rada advertises that to the host.

25
00:02:48,660 --> 00:02:57,170
Notice there's the advertisement sent to all hosts on the local segment and back on the P.C. and back

26
00:02:57,170 --> 00:03:00,610
on the P.C. I have conflict eith zero.

27
00:03:00,830 --> 00:03:09,600
What we should notice is it after a while we'll learn that network and there you go.

28
00:03:09,600 --> 00:03:14,610
After a while the host has learnt that a new address.

29
00:03:14,920 --> 00:03:26,430
So can the host ping and the router show run interface gigabit to 0 0 shows us the 2 IP version 6 addresses

30
00:03:26,430 --> 00:03:37,740
on the router so ping 2001 face colon colon 1 Notice I'm using the wrong protocol I need to use ping

31
00:03:37,740 --> 00:03:46,690
6 and that ping now succeeds so ping 6 2001 there 1 0 1.

32
00:03:46,710 --> 00:03:59,980
Colon colon 1 that ping also works on the right or we could do a debug IP vs 6 ICMP and I can do the

33
00:03:59,980 --> 00:04:09,460
ping to face once again and notice we see that output on the router echo request was received from a

34
00:04:09,460 --> 00:04:13,060
source with this IP version 6 address.

35
00:04:13,510 --> 00:04:25,750
I have config eith 0 shows us that IP address as configured on the P.C. notice it ends in 6.

36
00:04:25,760 --> 00:04:36,010
A 4 b the destination of the Echo request was the rudder and the rudder now sends a code reply.

37
00:04:36,010 --> 00:04:37,720
There's the IP version 6.

38
00:04:37,770 --> 00:04:40,720
Echo request IP version 6.

39
00:04:40,770 --> 00:04:48,310
Echo reply he has a rudder advertisement sent from the local rudder to the destination.

40
00:04:48,330 --> 00:04:50,960
F f 0 2 col on column 1.

41
00:04:51,060 --> 00:04:53,550
All nodes on the segment.

42
00:04:53,550 --> 00:05:02,400
So that was a demonstration of how slack and rudder advertisements and rudder solicitation messages

43
00:05:02,790 --> 00:05:07,080
can be used to automatically allocate networks to hosts.

44
00:05:07,320 --> 00:05:11,880
This is once again using the neighbor Discovery Protocol or NDP.
