WEBVTT

1
00:00.000 --> 00:01.050 align:middle line:84%


2
00:01.050 --> 00:02.310 align:middle line:84%
It is time.

3
00:02.310 --> 00:04.243 align:middle line:90%
It is time to implement
the GRE tunnels.

4
00:04.243 --> 00:06.660 align:middle line:90%
Let's take a quick peek at our
plan to confirm what it is.

5
00:06.660 --> 00:09.745 align:middle line:90%
That will help both us because I
can remember what we agreed to,

6
00:09.745 --> 00:11.370 align:middle line:90%
and then we can walk
through together--

7
00:11.370 --> 00:13.997 align:middle line:90%
the actual implementation
of the GRE tunnels.

8
00:13.997 --> 00:14.830 align:middle line:84%
So this is our plan.

9
00:14.830 --> 00:17.290 align:middle line:90%
We'll use tunnel
interface on R1 and R2.

10
00:17.290 --> 00:19.290 align:middle line:90%
We'll use their outside
reachable addresses

11
00:19.290 --> 00:22.110 align:middle line:90%
for the beginning and the end
of the tunnel respectively.

12
00:22.110 --> 00:25.062 align:middle line:90%
We'll include the network
address space of 10.12.12

13
00:25.062 --> 00:29.190 align:middle line:90%
at the 24 route mask, and dot 1
over here and dot 2 over here.

14
00:29.190 --> 00:31.493 align:middle line:90%
And then we'll add
EIGRP to the mix,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

14
00:29.190 --> 00:31.493 align:middle line:90%
And then we'll add
EIGRP to the mix,

15
00:31.493 --> 00:33.660 align:middle line:90%
and we'll include any
interfaces that begin with 10.

16
00:33.660 --> 00:36.190 align:middle line:90%
That will capture the
internal networks here.

17
00:36.190 --> 00:38.520 align:middle line:90%
It will also capture
the tunnel interfaces

18
00:38.520 --> 00:41.668 align:middle line:90%
that we configure with
10 address space as well.

19
00:41.668 --> 00:42.210 align:middle line:84%
It's a party.

20
00:42.210 --> 00:44.530 align:middle line:90%
Let's start on R1s to a
show IP interface brief.

21
00:44.530 --> 00:46.280 align:middle line:90%
Just to make sure I'm
on the right device.

22
00:46.280 --> 00:49.370 align:middle line:90%
So gig 0 slash 3,
the inside is 10.1,

23
00:49.370 --> 00:53.190 align:middle line:90%
and gig 0 slash 1 facing that
public network is 15.1.1.1.

24
00:53.190 --> 00:53.997 align:middle line:84%
Fantastic.

25
00:53.997 --> 00:55.830 align:middle line:90%
So on R1, we'll create
our tunnel interface.

26
00:55.830 --> 00:59.700 align:middle line:90%
Interface tunnel, and we are
going to use the number of 0.

27
00:59.700 --> 01:01.680 align:middle line:90%
And we'll give it
an IP address based
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
00:59.700 --> 01:01.680 align:middle line:90%
And we'll give it
an IP address based

28
01:01.680 --> 01:04.080 align:middle line:90%
on our plan, which
is going to be

29
01:04.080 --> 01:08.430 align:middle line:84%
10.12.12.1 with a 24-bit mask.

30
01:08.430 --> 01:09.450 align:middle line:84%
Fantastic.

31
01:09.450 --> 01:11.130 align:middle line:84%
And it just said that it's up.

32
01:11.130 --> 01:13.327 align:middle line:84%
And we'll do a tunnel source.

33
01:13.327 --> 01:15.660 align:middle line:90%
Now for the tunnel source,
we can have a couple options.

34
01:15.660 --> 01:18.360 align:middle line:90%
We could say the actual
IP address here on 0

35
01:18.360 --> 01:22.320 align:middle line:90%
slash 1 of 15.1.1.1, or we could
just point to the interface

36
01:22.320 --> 01:24.460 align:middle line:90%
and it knows what the
IP address there is.

37
01:24.460 --> 01:26.678 align:middle line:90%
So in our case, let's
just put in the IP

38
01:26.678 --> 01:28.470 align:middle line:90%
address of that interface
to make it clear,

39
01:28.470 --> 01:29.830 align:middle line:84%
what we're talking about.

40
01:29.830 --> 01:35.460 align:middle line:90%
So the tunnel source will be
15.1.1.1 the tunnel destination
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
01:29.830 --> 01:35.460 align:middle line:90%
So the tunnel source will be
15.1.1.1 the tunnel destination

41
01:35.460 --> 01:37.140 align:middle line:84%
is going to be the other side.

42
01:37.140 --> 01:41.490 align:middle line:90%
And I'll take a look at my notes
real quick, which is 25.2.2.2.

43
01:41.490 --> 01:45.240 align:middle line:90%
So put that in there,
and ask to do show run

44
01:45.240 --> 01:48.240 align:middle line:84%
for interface tunnel 0.

45
01:48.240 --> 01:49.080 align:middle line:84%
Fantastic.

46
01:49.080 --> 01:50.910 align:middle line:90%
And we'll repeat that
with the correct IP

47
01:50.910 --> 01:52.810 align:middle line:84%
addresses on the other side.

48
01:52.810 --> 01:54.910 align:middle line:90%
So let's go to R2 and
do the same thing.

49
01:54.910 --> 01:57.180 align:middle line:90%
So here in R2, config
t, interface tunnel

50
01:57.180 --> 02:03.860 align:middle line:90%
0, IP address 10.12.12
with a 24-bit mask.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

50
01:57.180 --> 02:03.860 align:middle line:90%
0, IP address 10.12.12
with a 24-bit mask.

51
02:03.860 --> 02:07.710 align:middle line:90%
Let's say tunnel
source is 25.2.2.2,

52
02:07.710 --> 02:13.290 align:middle line:84%
tunnel destination is 15.1.1.1.

53
02:13.290 --> 02:17.832 align:middle line:90%
Let's do a do show,
run interface tunnel 0.

54
02:17.832 --> 02:19.290 align:middle line:90%
And I'm going to
compare those two.

55
02:19.290 --> 02:22.110 align:middle line:84%
So here's R1 and here's R2.

56
02:22.110 --> 02:22.860 align:middle line:84%
That looks good.

57
02:22.860 --> 02:26.870 align:middle line:90%
And just as a test, if we
do a show IP route and press

58
02:26.870 --> 02:31.530 align:middle line:90%
Enter for the network
10.12 because I
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

58
02:26.870 --> 02:31.530 align:middle line:90%
Enter for the network
10.12 because I

59
02:31.530 --> 02:34.380 align:middle line:90%
am directly connected, so
is the router on tunnel 0--

60
02:34.380 --> 02:38.250 align:middle line:90%
if we pinged another
device on 10.12.12,

61
02:38.250 --> 02:40.055 align:middle line:90%
it would think, Oh, I
need to use tunnel 0.

62
02:40.055 --> 02:42.180 align:middle line:90%
And that would cause it to
encapsulate and shoot it

63
02:42.180 --> 02:43.470 align:middle line:84%
over to its good buddy, R1.

64
02:43.470 --> 02:49.090 align:middle line:90%
So let's do a quick
ping to 10.12.12.1.

65
02:49.090 --> 02:49.740 align:middle line:84%
And that works.

66
02:49.740 --> 02:51.040 align:middle line:84%
That's a great sign.

67
02:51.040 --> 02:53.790 align:middle line:90%
Now the next one is a video
do a video show IP route.

68
02:53.790 --> 02:57.690 align:middle line:90%
We currently-- if we're
talking about the 10.1 network,

69
02:57.690 --> 02:59.718 align:middle line:90%
this is from R2's
perspective, it's

70
02:59.718 --> 03:01.260 align:middle line:90%
going to use the
default route, which
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
02:59.718 --> 03:01.260 align:middle line:90%
going to use the
default route, which

71
03:01.260 --> 03:03.510 align:middle line:90%
isn't going to be forced
through the tunnel interface.

72
03:03.510 --> 03:05.680 align:middle line:90%
So we need to add the
routing to make that work.

73
03:05.680 --> 03:07.710 align:middle line:90%
So to do that based
on our plan, we

74
03:07.710 --> 03:10.750 align:middle line:90%
decided we're going to use
EIGRP autonomous system 1.

75
03:10.750 --> 03:12.750 align:middle line:90%
And we're going to include
any interface of that

76
03:12.750 --> 03:14.020 align:middle line:84%
being with 10.

77
03:14.020 --> 03:15.310 align:middle line:84%
So let's do that next.

78
03:15.310 --> 03:19.820 align:middle line:90%
So config t router, EIGRP
1, and an auto-summary

79
03:19.820 --> 03:21.570 align:middle line:90%
even though I believe
it's off these days.

80
03:21.570 --> 03:25.650 align:middle line:90%
And network 10 with a
wildcard mass saying we're

81
03:25.650 --> 03:27.870 align:middle line:90%
only going to match
on that first octet.

82
03:27.870 --> 03:29.310 align:middle line:84%
And we're done.

83
03:29.310 --> 03:34.920 align:middle line:90%
So IP EIGRP interface and we've
got R2 interfaces-- gig 0/3
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

83
03:29.310 --> 03:34.920 align:middle line:90%
So IP EIGRP interface and we've
got R2 interfaces-- gig 0/3

84
03:34.920 --> 03:36.900 align:middle line:84%
and also the tunnel interface 0.

85
03:36.900 --> 03:37.890 align:middle line:84%
Perfect.

86
03:37.890 --> 03:39.600 align:middle line:90%
Let's go do the
same thing on R1.

87
03:39.600 --> 03:42.980 align:middle line:90%
So we're here on
R1, router EIGRP 1.

88
03:42.980 --> 03:43.890 align:middle line:84%
[LAUGHTER]

89
03:43.890 --> 03:45.300 align:middle line:84%
Close, but no cigar.

90
03:45.300 --> 03:48.270 align:middle line:90%
And no auto-summary
and network 10

91
03:48.270 --> 03:50.640 align:middle line:90%
with the wildcard
mask, which basically

92
03:50.640 --> 03:53.787 align:middle line:90%
says any interface that starts
with 10 anything are in.

93
03:53.787 --> 03:55.620 align:middle line:90%
And if we have a
neighbors-- yeah there are.

94
03:55.620 --> 03:56.412 align:middle line:84%
That's a good sign.

95
03:56.412 --> 03:57.850 align:middle line:84%
The neighborship just came up.

96
03:57.850 --> 04:02.070 align:middle line:90%
And if we do a show IP route
for EIGRP learned routes,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
03:57.850 --> 04:02.070 align:middle line:90%
And if we do a show IP route
for EIGRP learned routes,

97
04:02.070 --> 04:03.030 align:middle line:84%
this is beautiful.

98
04:03.030 --> 04:07.440 align:middle line:90%
R1 says, hey, to get to 10.2.0,
I have an EIGRP learned route.

99
04:07.440 --> 04:11.230 align:middle line:90%
And there's the metric
aka feasible distance.

100
04:11.230 --> 04:14.730 align:middle line:90%
And I'm going to use my
egress interface of tunnel 0,

101
04:14.730 --> 04:17.519 align:middle line:90%
and the next hop
address is 10.12.12.2.

102
04:17.519 --> 04:18.450 align:middle line:84%
Fantastic.

103
04:18.450 --> 04:19.899 align:middle line:90%
So we've made some
good progress.

104
04:19.899 --> 04:22.770 align:middle line:90%
We planned out what we want
to do for the GRE tunnel.

105
04:22.770 --> 04:25.500 align:middle line:90%
We also implemented it, and
we added the routing protocols

106
04:25.500 --> 04:27.810 align:middle line:90%
we could have reachability
over that tunnel.

107
04:27.810 --> 04:30.125 align:middle line:90%
And we verified that
it works, but I'd
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

107
04:27.810 --> 04:30.125 align:middle line:90%
And we verified that
it works, but I'd

108
04:30.125 --> 04:31.750 align:middle line:90%
like to do one more
thing if your game.

109
04:31.750 --> 04:34.970 align:middle line:90%
And that is this--
having a protocol capture

110
04:34.970 --> 04:37.350 align:middle line:90%
of packets before
and after a process,

111
04:37.350 --> 04:40.040 align:middle line:90%
like before the
GRE encapsulation

112
04:40.040 --> 04:42.535 align:middle line:90%
and after, that's going to
help us understand the details

113
04:42.535 --> 04:43.660 align:middle line:84%
of what's really happening.

114
04:43.660 --> 04:46.050 align:middle line:90%
So in the next video,
let's pause for a moment

115
04:46.050 --> 04:48.060 align:middle line:90%
and let's do some packet
captures of traffic

116
04:48.060 --> 04:51.810 align:middle line:90%
before it hits the GRE tunnel,
and then during the GRE tunnel,

117
04:51.810 --> 04:53.070 align:middle line:84%
and then after.

118
04:53.070 --> 04:55.480 align:middle line:90%
So we'll do all of that
in the very next video.

119
04:55.480 --> 04:56.980 align:middle line:90%
I'll see you there
in just a moment.

120
04:56.980 --> 04:59.280 align:middle line:90%
Meanwhile, I hope this has
been informative for you.

121
04:59.280 --> 05:02.410 align:middle line:90%
And I'd like to thank
you for viewing.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

121
04:59.280 --> 05:02.410 align:middle line:90%
And I'd like to thank
you for viewing.