WEBVTT

1
00:00.000 --> 00:05.640
Just as in IPv4 is implementation of OSPF with OSPF V3 for IPv6.

2
00:05.640 --> 00:08.500
If we want to, we can set up an interface as passive.

3
00:08.500 --> 00:10.800
Now, why would we ever do that?

4
00:10.800 --> 00:11.800
Let's take a look at that.

5
00:11.800 --> 00:13.940
It's very same reason we do it for IPv4.

6
00:13.940 --> 00:16.380
If on this interface right here on R7,

7
00:16.380 --> 00:20.940
which is 2001, DBA6787, colon colon 7,

8
00:20.940 --> 00:24.140
if we wanted that interface not to participate in OSPF,

9
00:24.140 --> 00:25.880
one option would be just to tell that interface

10
00:25.880 --> 00:27.740
that it's not involved with OSPF,

11
00:27.740 --> 00:31.840
and it's not participating as part of our OSPF V3 process for Area 1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:27.740 --> 00:31.840
and it's not participating as part of our OSPF V3 process for Area 1.

12
00:31.840 --> 00:34.840
However, if we did that, that subnet 7 for IPv6,

13
00:34.840 --> 00:37.380
that subnet 7, if it's not enabled there for OSPF,

14
00:37.380 --> 00:41.540
it wouldn't be advertised and reachable from the rest of the OSPF domain.

15
00:41.540 --> 00:45.490
So, one of the benefits of using passive is that we can still include this 7

16
00:45.490 --> 00:46.140
subnet

17
00:46.140 --> 00:49.780
for IPv6, the 2001 DBA6787,

18
00:49.780 --> 00:53.740
but at the same time, we're not receiving hello messages on that interface.

19
00:53.740 --> 00:57.740
And that's going to prevent us from becoming an adjacent neighbor with some

20
00:57.740 --> 00:58.300
other device

21
00:58.300 --> 01:01.980
or some PC or some hacker that's trying to convince our router
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

21
00:58.300 --> 01:01.980
or some PC or some hacker that's trying to convince our router

22
01:01.980 --> 01:04.140
that we should become an OSPF neighbor with them.

23
01:04.140 --> 01:06.940
So, no hello's if the interface is passive.

24
01:06.940 --> 01:08.380
So, we can include the interface,

25
01:08.380 --> 01:11.780
but just specify in router configuration mode here on R7

26
01:11.780 --> 01:13.740
that that interface is passive.

27
01:13.740 --> 01:15.780
And that way, we have the benefit of advertising the route

28
01:15.780 --> 01:17.660
without the possibility of becoming neighbor.

29
01:17.660 --> 01:19.340
Now, to demonstrate that we can't form a neighbor ship

30
01:19.340 --> 01:22.220
if we make it passive, here's what I propose we do.

31
01:22.220 --> 01:24.620
Instead of doing it on this one, in the previous set of videos,

32
01:24.620 --> 01:26.620
we actually worked with passive interface here,

33
01:26.620 --> 01:30.140
let's go ahead and take an active interface like this one over here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

33
01:26.620 --> 01:30.140
let's go ahead and take an active interface like this one over here.

34
01:30.140 --> 01:32.780
R8's fast-eatenant 4/1,

35
01:32.780 --> 01:36.460
and it's currently included in OSPF for IPv6.

36
01:36.460 --> 01:38.620
And if we specify the interface is passive,

37
01:38.620 --> 01:42.300
it's going to break the adjacency here between R8 and R6,

38
01:42.300 --> 01:44.540
because it's no longer going to be processing hello messages.

39
01:44.540 --> 01:46.220
And as a result, we'll break the neighbors ship.

40
01:46.220 --> 01:49.820
Let's demonstrate that right here between R8 and R6.

41
01:49.820 --> 01:52.220
And once we've done it, and we validate that, yep,

42
01:52.220 --> 01:53.980
that the neighbor ship is no longer working,

43
01:53.980 --> 01:57.020
we'll then go ahead and restore the network to its full functionality

44
01:57.020 --> 02:01.020
by making this interface F/4-1 not a passive interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

44
01:57.020 --> 02:01.020
by making this interface F/4-1 not a passive interface.

45
02:01.020 --> 02:02.140
And here we go.

46
02:02.140 --> 02:05.260
So a moment ago, on R8, we verified we have routes,

47
02:05.260 --> 02:06.380
we have connectivity.

48
02:06.380 --> 02:09.740
And if we do a show, OSPF V3, IPv6 neighbor,

49
02:09.740 --> 02:12.300
we can verify that we are currently in a full adjacency

50
02:12.300 --> 02:14.620
with R6 based on that router ID.

51
02:14.620 --> 02:19.020
Again, R6 is this router right here, just north of R8.

52
02:19.020 --> 02:22.780
So let's do a show run section router, press enter,

53
02:22.780 --> 02:26.620
just to take a look at our current configuration for OSPF V3.

54
02:26.620 --> 02:28.220
So here's our configuration,

55
02:28.220 --> 02:31.180
and we have an address family for IPv6 unit cast.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

55
02:28.220 --> 02:31.180
and we have an address family for IPv6 unit cast.

56
02:31.180 --> 02:33.500
And what we're going to do is go into that address family.

57
02:33.500 --> 02:34.860
And from within that address family,

58
02:34.860 --> 02:37.020
we'll still be say passive interface,

59
02:37.020 --> 02:39.260
and then specify the interface that we want to be passive.

60
02:39.260 --> 02:40.620
And based on our topology,

61
02:40.620 --> 02:44.380
we're going to specify F/4-1 as a passive interface.

62
02:44.380 --> 02:46.060
So we'll go into configuration mode,

63
02:46.060 --> 02:49.580
and then we'll go into router OSPF V3 for process ID1

64
02:49.580 --> 02:50.860
by typing that in.

65
02:50.860 --> 02:54.060
And then we'll go into the address family for IPv6 unit cast

66
02:54.060 --> 02:55.500
by typing that in next.

67
02:55.500 --> 02:57.580
Then here we'll type in passive dash interface,

68
02:57.580 --> 02:59.980
and then we'll specify the interface that we want to be passive.

69
02:59.980 --> 03:03.180
So in our case, it's going to be fast Ethernet 4/1.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

69
02:59.980 --> 03:03.180
So in our case, it's going to be fast Ethernet 4/1.

70
03:03.180 --> 03:05.980
And before I press enter, let me just verify that's the interface,

71
03:05.980 --> 03:09.820
sure enough that's the interface on our R8 that's going up to our 6.

72
03:09.820 --> 03:11.820
So once we press enter here,

73
03:11.820 --> 03:13.980
that's going to break the adjacency.

74
03:13.980 --> 03:16.380
And we do a show run section router,

75
03:16.380 --> 03:18.060
so they look at the config that did that.

76
03:18.060 --> 03:19.980
So there's our passive interface command

77
03:19.980 --> 03:21.980
under the address family for IPv6.

78
03:21.980 --> 03:24.380
And if we do a show IPv6 protocols,

79
03:24.380 --> 03:26.940
and press enter, here showing us that we still have

80
03:26.940 --> 03:29.660
fast Ethernet 4/1 associated with area 2,

81
03:29.660 --> 03:31.820
but because that interface is passive,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

81
03:29.660 --> 03:31.820
but because that interface is passive,

82
03:31.820 --> 03:36.220
we're not able to form a naborship with any other router off of that interface.

83
03:36.220 --> 03:41.660
So let's go back into configuration mode for router OSPF V3 process ID1.

84
03:41.660 --> 03:45.180
And let's go ahead and take that off with a few up arrow keys.

85
03:45.180 --> 03:46.940
Then we'll do a control A together beginning of that.

86
03:46.940 --> 03:49.420
We'll say no passive interface, FAA 4/1,

87
03:49.420 --> 03:51.660
which should allow us to start processing the lows.

88
03:51.660 --> 03:53.900
And we've now formed an adjacency with R6.

89
03:53.900 --> 03:55.980
And that's how we can include an interface

90
03:55.980 --> 03:58.060
and its associated directly connected network

91
03:58.060 --> 04:00.780
as part of OSPF, but at the same time,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

91
03:58.060 --> 04:00.780
as part of OSPF, but at the same time,

92
04:00.780 --> 04:03.020
prevent the forming of a naborship

93
04:03.020 --> 04:05.740
with some other routing device on that same subnet.

94
04:05.740 --> 04:09.900
Now another cool feature, which is also common to both IPv4 and IPv6 with those

95
04:09.900 --> 04:14.720
PF, is to make an area not a normal area, but make it a stub or a totally stub

96
04:14.720 --> 04:15.500
by area.

97
04:15.500 --> 04:19.180
And that's exactly what we're going to do with the address family for IPv6 in

98
04:19.180 --> 04:19.820
the next video.

99
04:19.820 --> 04:21.660
So I'll see you there in just a moment.