WEBVTT 1 00:00.000 --> 00:09.890 So as our final step, we want to test reachability between SRV1 and Workstation 2 00:09.890 --> 00:10.780 1, which again 3 00:10.780 --> 00:14.260 with our primary goal going into this entire skill. 4 00:14.260 --> 00:20.240 So let's jump into SRV1 and make sure that it can reach not only the network on 5 00:20.240 --> 00:20.380 the 6 00:20.380 --> 00:24.760 on-prem location where Workstation 1 is, but make sure that it can still reach 7 00:24.760 --> 00:25.340 the internet 8 00:25.340 --> 00:26.340 as well. 9 00:26.340 --> 00:32.300 Let's go ahead and jump in to the command line of SRV1. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 9 00:26.340 --> 00:32.300 Let's go ahead and jump in to the command line of SRV1. 10 00:32.300 --> 00:38.800 So our first step of course would be to ping 10.10.10.10, which is Workstation 11 00:38.800 --> 00:39.180 1. 12 00:39.180 --> 00:42.880 We see right away that this is working, so that's good. 13 00:42.880 --> 00:45.740 We should probably also trace route to it. 14 00:45.740 --> 00:52.920 So if we trace route to 10.10.10.10, we see that it is first going to 10.40.10. 15 00:52.920 --> 00:53.060 2, which 16 00:53.060 --> 01:01.650 is of course, GCP R1, then we see it going to 169.254.41.2, which is on-prem R1 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 16 00:53.060 --> 01:01.650 is of course, GCP R1, then we see it going to 169.254.41.2, which is on-prem R1 17 01:01.650 --> 01:02.340 across 18 01:02.340 --> 01:07.440 the tunnel, and then of course it finally reaches its destination of 10.10.10. 19 01:07.440 --> 01:08.780 10.10. 20 01:08.780 --> 01:11.940 So we see that this is going exactly the way we want. 21 01:11.940 --> 01:17.700 If we ping the internet, we see this is still working as well, and if we trace 22 01:17.700 --> 01:18.300 it, we see 23 01:18.300 --> 01:22.180 that our first hop here is also going to GCP R1. 24 01:22.180 --> 01:25.850 Now there's several devices in the middle there that aren't responding to our 25 01:25.850 --> 01:26.380 trace, but 26 01:26.380 --> 01:32.980 we see that it ultimately does get 28.8.8.8, one of Google's DNS servers. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 26 01:26.380 --> 01:32.980 we see that it ultimately does get 28.8.8.8, one of Google's DNS servers. 27 01:32.980 --> 01:38.100 So this means that our reachability across our IPsec VPN and connectivity to 28 01:38.100 --> 01:39.020 the internet 29 01:39.020 --> 01:42.860 are both working as we designed. 30 01:42.860 --> 01:45.860 So in this video, we didn't configure anything. 31 01:45.860 --> 01:50.020 We just jumped into the command line here on SRV1 and made sure that it had 32 01:50.020 --> 01:50.940 reachability 33 01:50.940 --> 01:56.730 to workstation 1 in the on-prem or headquarters location the way we want it to 34 01:56.730 --> 01:57.300 across our 35 01:57.300 --> 01:59.420 IPsec VPN. 36 01:59.420 --> 02:02.940 We also of course verified that it can still get to the internet. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 36 01:59.420 --> 02:02.940 We also of course verified that it can still get to the internet. 37 02:02.940 --> 02:07.200 So with all of this working, that concludes everything that we need to cover in 38 02:07.200 --> 02:08.460 this skill 39 02:08.460 --> 02:10.420 except for our challenge. 40 02:10.420 --> 02:17.090 In this challenge, you're going to be deploying a redundant VPN between on-prem 41 02:17.090 --> 02:18.620 R2 and GCP 42 02:18.620 --> 02:19.620 R2. 43 02:19.620 --> 02:21.500 So go ahead and give that a shot. 44 02:21.500 --> 02:25.620 Good luck and I'll see you in the solution video on the other side. 45 02:25.620 --> 02:44.620 [ Silence ]