WEBVTT 1 00:00.000 --> 00:06.720 So now we're finally ready for the big step of bringing up our tunnel 2 00:06.720 --> 00:09.000 interfaces on our two routers. 3 00:09.000 --> 00:13.450 So there's not too much to configure here, just some source destination 4 00:13.450 --> 00:14.000 addresses, 5 00:14.000 --> 00:17.000 tunnel modes, setting up the tunnel protection. 6 00:17.000 --> 00:21.000 So let's just go ahead and jump in and look at all the different moving parts. 7 00:21.000 --> 00:27.190 Once again, AWS R1 is going to be almost the same with some addresses switched 8 00:27.190 --> 00:28.000 around. 9 00:28.000 --> 00:34.000 So let's go ahead and start on our on-prem router one. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 9 00:28.000 --> 00:34.000 So let's go ahead and start on our on-prem router one. 10 00:34.000 --> 00:39.000 Okay, so for the configuration of the tunnel, the first thing, of course, 11 00:39.000 --> 00:43.000 we have to create an interface tunnel, we'll just make tunnel one. 12 00:43.000 --> 00:47.030 We'll put a description on it. That's of course optional, but we'll call this 13 00:47.030 --> 00:51.000 like two AWS R1. 14 00:51.000 --> 00:55.800 Of course, it's going to need an IP address for the IP address. We're going to 15 00:55.800 --> 00:57.000 use one six nine. 16 00:57.000 --> 01:01.000 Two five four dot and we'll use eleven dot two. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 16 00:57.000 --> 01:01.000 Two five four dot and we'll use eleven dot two. 17 01:01.000 --> 01:06.000 We're going to make the AWS R one side dot one. 18 01:06.000 --> 01:09.000 And this is going to be a slash 30. 19 01:09.000 --> 01:13.320 A few other things we may want to tweak since it is going to be an IP sec 20 01:13.320 --> 01:14.000 tunnel. 21 01:14.000 --> 01:21.000 These are of course optional, but we'll set the IPM to you to fourteen hundred. 22 01:21.000 --> 01:30.000 And then the IP TCP maximum segment size to forty bytes below that or thirteen WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 24 01:30.000 --> 01:34.450 Now, of course, we have some components of the tunnel that we absolutely have 25 01:34.450 --> 01:35.000 to have. 26 01:35.000 --> 01:38.000 The first one, of course, is the tunnel source. 27 01:38.000 --> 01:42.000 We can specify an IP address or an interface here. 28 01:42.000 --> 01:46.000 We'll specify an interface gigabit one. That way it makes it a little easier to 29 01:46.000 --> 01:50.000 transport the configuration to other devices. 30 01:50.000 --> 01:55.140 We also want to set the tunnel mode. And what we're looking for here 31 01:55.140 --> 01:57.000 specifically is IP sec. 32 01:57.000 --> 02:00.000 We want to run this as an IP sec tunnel. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 33 02:00.000 --> 02:03.000 And it's going to be running over IP V four. 34 02:03.000 --> 02:07.000 Of course, we also need a tunnel destination. 35 02:07.000 --> 02:11.000 Again, this is going to be the outside address or your elastic address. 36 02:11.000 --> 02:18.300 Again, in my case, that is fifty four dot one sixty three dot one fifty one dot 37 02:18.300 --> 02:19.000 twenty one. 38 02:19.000 --> 02:23.000 And finally, we need to specify the tunnel protection. 39 02:23.000 --> 02:27.000 This is going to be using, of course, our IP sec profile. 40 02:27.000 --> 02:29.000 And we need to put in the name here. 41 02:29.000 --> 02:32.000 That should take care of this configuration. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 41 02:29.000 --> 02:32.000 That should take care of this configuration. 42 02:32.000 --> 02:38.200 So now let's jump over to notepad and change what we need to change for a WS R 43 02:38.200 --> 02:39.000 one. 44 02:39.000 --> 02:42.000 So as we can see, most of this is the same. 45 02:42.000 --> 02:45.000 I did change the description to be more appropriate. 46 02:45.000 --> 02:49.500 We can see the IP address is the one six nine dot two five four dot eleven dot 47 02:49.500 --> 02:50.000 one. 48 02:50.000 --> 02:53.000 The rest of the configuration is mostly the same. 49 02:53.000 --> 02:56.000 Of course, the tunnel destination is going to change. 50 02:56.000 --> 03:02.020 And this is going to be that ISP assigned public address at your headquarters WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 50 02:56.000 --> 03:02.020 And this is going to be that ISP assigned public address at your headquarters 51 03:02.020 --> 03:03.000 site. 52 03:03.000 --> 03:06.000 Which for this example, we will be blurring that out. 53 03:06.000 --> 03:12.000 So let's go ahead and take this and put this on to a WS R one. 54 03:12.000 --> 03:14.000 So we'll simply paste this in. 55 03:14.000 --> 03:19.000 And if everything is gone correctly, our tunnel should actually come up. 56 03:19.000 --> 03:23.000 So to verify that, let's do a show IP interface brief. 57 03:23.000 --> 03:28.070 We can see that our tunnel one is in fact up and we can verify with reach 58 03:28.070 --> 03:29.000 ability. 59 03:29.000 --> 03:34.000 Let's do a paying one six nine dot two five four dot eleven dot two, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 59 03:29.000 --> 03:34.000 Let's do a paying one six nine dot two five four dot eleven dot two, 60 03:34.000 --> 03:37.000 which of course would be the far end of that tunnel. 61 03:37.000 --> 03:39.000 We can see that that's successful. 62 03:39.000 --> 03:44.000 If we go back over to our on parameter outer one, we'll ping the one six nine 63 03:44.000 --> 03:45.000 dot two five four 64 03:45.000 --> 03:48.000 dot eleven dot one, which is of course the remote end. 65 03:48.000 --> 03:52.000 We see that it's working from both sides, which would of course be expected. 66 03:52.000 --> 03:55.000 So our tunnel configuration was easy enough. 67 03:55.000 --> 03:59.330 The tunnel came right up and we were able to get traffic to pass through the 68 03:59.330 --> 04:01.000 tunnel to the other side. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 68 03:59.330 --> 04:01.000 tunnel to the other side. 69 04:01.000 --> 04:06.000 Now our final goal was of course to get the subnets to talk to each other. 70 04:06.000 --> 04:09.000 For that, we're going to need some form of routing. 71 04:09.000 --> 04:12.000 So let's discuss that coming up next.