WEBVTT 1 00:00.000 --> 00:03.990 Alright, so our first step in our game plan is to verify and update our top 2 00:03.990 --> 00:05.000 ology. 3 00:05.000 --> 00:07.560 So let's take a moment right now and do that. 4 00:07.560 --> 00:10.600 So here in the vSphere client, let me go ahead and take Mint 1 and I'm going to 5 00:10.600 --> 00:11.080 rename 6 00:11.080 --> 00:14.440 that Mint 10 and make sure it's on the 10 segment right there. 7 00:14.440 --> 00:16.080 So I'll right click on Mint 1. 8 00:16.080 --> 00:19.010 From the menu, we'll go ahead and click here on Rename and then we'll go ahead 9 00:19.010 --> 00:19.360 and call 10 00:19.360 --> 00:21.600 it Mint 10 and click on OK. 11 00:21.600 --> 00:25.400 And then we'll take Mint 2 and we'll make it Mint 20 again based on our plan 12 00:25.400 --> 00:26.680 right there. 13 00:26.680 --> 00:30.590 So we'll right click on Mint 2 from the menu, click here on Rename and we'll WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:26.680 --> 00:30.590 So we'll right click on Mint 2 from the menu, click here on Rename and we'll 14 00:30.590 --> 00:31.200 call that 15 00:31.200 --> 00:32.200 Mint 20. 16 00:32.200 --> 00:34.640 Then we're also going to need Mint 23 up here. 17 00:34.640 --> 00:36.970 So let me go ahead and first of all, make sure that Mint 10 and 20 are on the 18 00:36.970 --> 00:37.800 right segments 19 00:37.800 --> 00:41.960 and then I'll clone one of them and put them up here on the 23 network. 20 00:41.960 --> 00:45.590 So let's go to the networks tab here for a moment and there's segment 10 yellow 21 00:45.590 --> 00:46.120 , there's 22 00:46.120 --> 00:48.000 Mint 10 that looks good. 23 00:48.000 --> 00:51.240 Let's go to segment 20 pink, there's Mint 20, perfect. 24 00:51.240 --> 00:53.760 So now that we know they're on the right segments, let's take Mint 20, we'll 25 00:53.760 --> 00:54.840 right click on it 26 00:54.840 --> 00:58.160 and from the menu, we'll click on clone and then from the clone sub menu, we'll 27 00:58.160 --> 00:58.360 click 28 00:58.360 --> 01:02.840 right here and clone to virtual machine and let's call this Mint 23. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 28 00:58.360 --> 01:02.840 right here and clone to virtual machine and let's call this Mint 23. 29 01:02.840 --> 01:05.860 As far as where we want to keep that, let's put in a folder called VMs for 30 01:05.860 --> 01:06.400 testing, we'll 31 01:06.400 --> 01:07.400 click on Next. 32 01:07.400 --> 01:11.450 Let's go ahead and put some ESXIA and click on Next and then we'll put on the 33 01:11.450 --> 01:12.160 local data 34 01:12.160 --> 01:15.980 store, we'll use thin provisioning, click on Next and then we'll customize it 35 01:15.980 --> 01:16.360 to put 36 01:16.360 --> 01:19.420 it on the right subnet here, the 23 network and then we'll have it power on 37 01:19.420 --> 01:20.200 automatically 38 01:20.200 --> 01:23.820 after it's done, click on Next and then here instead of being on the pink sub 39 01:23.820 --> 01:24.480 net, we'll 40 01:24.480 --> 01:28.440 click on Browse and we want to put it on the 23 network. 41 01:28.440 --> 01:30.360 So I have a port group for that, here it is. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 41 01:28.440 --> 01:30.360 So I have a port group for that, here it is. 42 01:30.360 --> 01:34.880 It's not an ESX port group, it's our external network here, it's VLAN-23. 43 01:34.880 --> 01:39.350 So we'll select that, click on OK and then click on Next and then click on 44 01:39.350 --> 01:40.080 Finish and 45 01:40.080 --> 01:43.860 in a few minutes, we should have a brand new VM right here called Mint 23 46 01:43.860 --> 01:44.560 connected to 47 01:44.560 --> 01:46.280 the 2312 network. 48 01:46.280 --> 01:49.200 So also let me check on it's tab show quick, okay, so it's being deployed. 49 01:49.200 --> 01:52.630 Let me also go ahead and power on Mint 10 right here, so let's simply power it 50 01:52.630 --> 01:52.920 up. 51 01:52.920 --> 01:57.500 So that's this VM right here and let's also deploy my little web server right 52 01:57.500 --> 01:57.960 here and 53 01:57.960 --> 01:59.320 we'll call it Web 10. 54 01:59.320 --> 02:02.320 So we'll right click on the data center from the drop-down, say I want to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 54 01:59.320 --> 02:02.320 So we'll right click on the data center from the drop-down, say I want to 55 02:02.320 --> 02:03.320 deploy an OVF 56 02:03.320 --> 02:07.400 template, I have those files locally, so I'll click right here and upload files 57 02:07.400 --> 02:07.480 . 58 02:07.480 --> 02:10.000 So I've grabbed that file, I'll click on Next. 59 02:10.000 --> 02:12.670 So we'll go ahead and name it Web 10 and then we'll go ahead and place that in 60 02:12.670 --> 02:13.160 the VMs 61 02:13.160 --> 02:19.100 for testing folder, click on Next and then let's host this on ES6IB and click 62 02:19.100 --> 02:19.840 on Next. 63 02:19.840 --> 02:23.410 We'll put it on the local data store there, I'll use thin provisioning, click 64 02:23.410 --> 02:23.840 on Next 65 02:23.840 --> 02:25.400 and then put it on the right port group. 66 02:25.400 --> 02:28.600 So I want this one, this Web 10 VM to be on segment 10. 67 02:28.600 --> 02:33.710 So we'll click on Browse and we'll put it on segment 10, click on OK, click on WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 67 02:28.600 --> 02:33.710 So we'll click on Browse and we'll put it on segment 10, click on OK, click on 68 02:33.710 --> 02:34.120 Next 69 02:34.120 --> 02:35.520 and then click on Finish. 70 02:35.520 --> 02:39.690 Then we'll check on our status, I'll click here and please show me all running 71 02:39.690 --> 02:40.240 tasks. 72 02:40.240 --> 02:43.670 So it's still deploying Mint 20, it's about halfway done there and it's down 73 02:43.670 --> 02:44.280 the process 74 02:44.280 --> 02:47.780 of deploying our little web server right here, Web 10 and that's a teeny little 75 02:47.780 --> 02:48.240 VM so that 76 02:48.240 --> 02:49.440 shouldn't take too long. 77 02:49.440 --> 02:51.680 All right, so that's making progress, great, great, great. 78 02:51.680 --> 02:56.480 So while that's being deployed, let's also go ahead and update our NAT policy. 79 02:56.480 --> 02:59.580 So based on our plan, we wanted to change the source NAT and make sure we're 80 02:59.580 --> 03:00.080 just doing WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 80 02:59.580 --> 03:00.080 just doing 81 03:00.080 --> 03:04.230 NATting over to one single IP address here instead of a pool of addresses and 82 03:04.230 --> 03:04.560 what we 83 03:04.560 --> 03:08.760 want to do NAT to is 23.1.2.60 on our Tier Zero Gateway. 84 03:08.760 --> 03:09.760 So let's do that next. 85 03:09.760 --> 03:13.780 So we'll go to the NSX Manager, we'll click here on Networking on the left 86 03:13.780 --> 03:14.680 under Network 87 03:14.680 --> 03:16.240 Services, we'll click on NAT. 88 03:16.240 --> 03:19.360 Currently right here under NAT, we have this Net Rule associated with our Tier 89 03:19.360 --> 03:19.400 Zero 90 03:19.400 --> 03:22.720 Gateway that's doing source NAT and there's the range of addresses. 91 03:22.720 --> 03:26.600 So I'm going to click on the three dots, click on Edit to edit that NAT Rule 92 03:26.600 --> 03:26.800 and let's 93 03:26.800 --> 03:30.520 say we want to go ahead and not use this range of addresses and let me go ahead WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 93 03:26.800 --> 03:30.520 say we want to go ahead and not use this range of addresses and let me go ahead 94 03:30.520 --> 03:30.760 and 95 03:30.760 --> 03:33.570 collapse the left hand column and give us a little more room here and instead 96 03:33.570 --> 03:33.960 of using 97 03:33.960 --> 03:36.600 this pool of addresses, I'll click on the X to remove that. 98 03:36.600 --> 03:41.460 What we want to do is map it to 23.1.2.60 which is the virtual IP address we 99 03:41.460 --> 03:42.200 assign to 100 03:42.200 --> 03:46.180 Gateway Zero and with that in place, we'll scroll down and click on Save and 101 03:46.180 --> 03:46.600 now that's 102 03:46.600 --> 03:48.840 done, let me go ahead and bring in a client. 103 03:48.840 --> 03:52.140 So let's go over to Mint 10, we'll verify first we can get out to the internet 104 03:52.140 --> 03:52.480 and also 105 03:52.480 --> 03:56.000 let's also verify by just doing an SSH session over to our little external 106 03:56.000 --> 03:57.200 router here that 107 03:57.200 --> 04:01.130 it appears that we're coming in from 23.1.2.60 and that'll help guarantee that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 107 03:57.200 --> 04:01.130 it appears that we're coming in from 23.1.2.60 and that'll help guarantee that 108 04:01.130 --> 04:01.680 we're actually 109 04:01.680 --> 04:04.000 using the NAT as intended. 110 04:04.000 --> 04:08.130 So back here on the VSphere client, let's go to Mint 10 and let's launch a 111 04:08.130 --> 04:09.080 remote console 112 04:09.080 --> 04:11.400 and here that is, fantastic. 113 04:11.400 --> 04:13.440 Let's also verify its IP address. 114 04:13.440 --> 04:16.280 So we can have an IF config or IP address. 115 04:16.280 --> 04:19.090 Either way is great, they're both going to show us the IP address in use and 116 04:19.090 --> 04:19.400 this is 117 04:19.400 --> 04:21.840 10100165. 118 04:21.840 --> 04:24.780 Let's verify we can get out to the internet with a trace, we'll do a dash N for 119 04:24.780 --> 04:25.200 don't 120 04:25.200 --> 04:29.940 bother doing name resolution and let's go out to Google at 8.8.8.8 press enter 121 04:29.940 --> 04:30.280 and that's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 121 04:29.940 --> 04:30.280 and that's 122 04:30.280 --> 04:32.240 looking good, I'll do a control C to stop that. 123 04:32.240 --> 04:34.760 I just want to make sure we're getting out to the real internet. 124 04:34.760 --> 04:40.060 Let's also do an SSH dash L login as a user of VYOS to this little gateway 125 04:40.060 --> 04:41.000 right here 126 04:41.000 --> 04:42.000 at .1. 127 04:42.000 --> 04:47.210 So that's the 23.1.2.1 press enter, I'll put in the password and we'll type in 128 04:47.210 --> 04:47.920 who and 129 04:47.920 --> 04:51.400 that should confirm whether or not the NAT is working as intended. 130 04:51.400 --> 04:55.290 So from this little router's perspective, it looks like it's getting an inbound 131 04:55.290 --> 04:55.560 SSH 132 04:55.560 --> 05:00.200 connection coming from 23.1.2.60, which verifies our NAT. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 132 04:55.560 --> 05:00.200 connection coming from 23.1.2.60, which verifies our NAT. 133 05:00.200 --> 05:03.300 Now also in preparation for setting up our gateway rules, I want to have a 134 05:03.300 --> 05:03.960 destination 135 05:03.960 --> 05:07.080 NAT rule for this little Web 10 server as well. 136 05:07.080 --> 05:08.880 So let's bring that console up next. 137 05:08.880 --> 05:11.920 So we'll go back to the vSphere client and here is Web 10. 138 05:11.920 --> 05:13.200 Oh, I thought I told it to turn on. 139 05:13.200 --> 05:14.200 I guess I didn't. 140 05:14.200 --> 05:15.600 So we'll select Web 10. 141 05:15.600 --> 05:17.320 Let's just verify it's on the right segment. 142 05:17.320 --> 05:20.640 So it's on seg 10 fantastic and let's power it on. 143 05:20.640 --> 05:22.520 Now this little VM does not have VMware tools. 144 05:22.520 --> 05:26.320 So I'll have to be careful about how I power it off and do it gracefully. 145 05:26.320 --> 05:30.800 But for our purposes, it's a super small VM and it has web services running as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 145 05:26.320 --> 05:30.800 But for our purposes, it's a super small VM and it has web services running as 146 05:30.800 --> 05:31.840 a default. 147 05:31.840 --> 05:35.600 So let's open up a remote console toward little Web 10 server as well. 148 05:35.600 --> 05:37.320 Just to verify its IP address. 149 05:37.320 --> 05:40.190 So we'll click here on launch remote console and then let's bring in that 150 05:40.190 --> 05:41.360 little Web server. 151 05:41.360 --> 05:42.560 And here it is right here. 152 05:42.560 --> 05:43.560 So I'm showing you right here. 153 05:43.560 --> 05:46.280 It's IP address is 1010.181. 154 05:46.280 --> 05:48.840 We could also verify that by opening up a shell. 155 05:48.840 --> 05:52.520 So here if we do an IF config and let me zoom in a little bit there. 156 05:52.520 --> 05:55.880 So sure enough, it's IP address is 10.10.0.181. 157 05:55.880 --> 05:59.630 So I'm going to make a note of that that that is the IP address for this little 158 05:59.630 --> 05:59.920 Web 159 05:59.920 --> 06:01.280 server right here. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 159 05:59.920 --> 06:01.280 server right here. 160 06:01.280 --> 06:04.630 So if we want to set up a destination NAT here on our gateway zero that leads 161 06:04.630 --> 06:05.040 to this 162 06:05.040 --> 06:06.440 little Web VM. 163 06:06.440 --> 06:11.160 So we can go ahead and map the global address of 23.1.2.181 and have that map 164 06:11.160 --> 06:11.880 down to this 165 06:11.880 --> 06:14.280 Web server at 1010.181. 166 06:14.280 --> 06:16.480 So to do that, we'll go to the NSX manager. 167 06:16.480 --> 06:20.440 So here in the NSX manager with the networking tab selected on the left, we've 168 06:20.440 --> 06:21.280 selected NAT. 169 06:21.280 --> 06:23.400 Let me go ahead and collapse that left hand side. 170 06:23.400 --> 06:25.480 And let's add a new NAT rule. 171 06:25.480 --> 06:27.280 So we'll click right here, add NAT rule. 172 06:27.280 --> 06:30.500 Also if you want a further deep dive into the world of sitting up and working WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 172 06:27.280 --> 06:30.500 Also if you want a further deep dive into the world of sitting up and working 173 06:30.500 --> 06:31.320 with NAT, 174 06:31.320 --> 06:34.630 please check out that respective skill where we walk through sitting at both 175 06:34.630 --> 06:35.160 source and 176 06:35.160 --> 06:37.240 destination NAT and verify it all of it together. 177 06:37.240 --> 06:40.920 So here, as we have the destination NAT in place, we can test our gateway rules 178 06:40.920 --> 06:41.320 from the 179 06:41.320 --> 06:44.120 outside trying to get down to the server, Web 10. 180 06:44.120 --> 06:49.210 So for the NAT rule, we'll go ahead and call this Web SRVR and the type of NATs 181 06:49.210 --> 06:49.640 can be 182 06:49.640 --> 06:51.000 destination NAT. 183 06:51.000 --> 06:53.340 So for the source address, I'm going to leave that wide open so we could have 184 06:53.340 --> 06:53.880 any possible 185 06:53.880 --> 06:55.160 source address. 186 06:55.160 --> 07:01.640 And then if they're trying to go to the destination address of 23.1.2.181. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 186 06:55.160 --> 07:01.640 And then if they're trying to go to the destination address of 23.1.2.181. 187 07:01.640 --> 07:04.920 So put that here as the initial IP address that the customer is trying to reach 188 07:04.920 --> 07:05.160 . 189 07:05.160 --> 07:08.080 So that's 23.1.2.181. 190 07:08.080 --> 07:12.260 And if that happens, we want to translate that to the IP address of the Web 10 191 07:12.260 --> 07:12.920 server, which 192 07:12.920 --> 07:15.720 is 1010.181. 193 07:15.720 --> 07:20.000 So the translated address is going to be 10.10.0.181. 194 07:20.000 --> 07:22.760 And currently I have two edges out here, edge one and edge two. 195 07:22.760 --> 07:25.850 So I'm going to go ahead and also specify that that's where I want that to be 196 07:25.850 --> 07:26.320 applied 197 07:26.320 --> 07:29.680 to, to both of my logical interfaces on tier zero. 198 07:29.680 --> 07:31.360 And that's edge one and edge two. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 198 07:29.680 --> 07:31.360 And that's edge one and edge two. 199 07:31.360 --> 07:34.530 And also behind the scenes, I've got a virtual IP address of about 60 that we 200 07:34.530 --> 07:35.240 're using on 201 07:35.240 --> 07:36.640 that gateway zero as well. 202 07:36.640 --> 07:40.220 So for the NAT rule for the destination NAT, we'll apply it to these two 203 07:40.220 --> 07:41.000 interfaces, click 204 07:41.000 --> 07:44.360 on apply, and then scroll down and click on save. 205 07:44.360 --> 07:45.960 So there's our destination NAT rule. 206 07:45.960 --> 07:47.320 Also let's edit that one more time. 207 07:47.320 --> 07:48.960 I'll show you something else pretty cool. 208 07:48.960 --> 07:51.920 And the details for this NAT rule, check out where it says firewall. 209 07:51.920 --> 07:55.850 It says, what do you want to match on the external address for this NAT rule or 210 07:55.850 --> 07:56.560 the internal 211 07:56.560 --> 07:57.560 address? 212 07:57.560 --> 07:59.440 And so by default, it's matching the internal address. 213 07:59.440 --> 08:03.260 So if we set up rules based on IP addresses with our gateway firewall, we'll WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 213 07:59.440 --> 08:03.260 So if we set up rules based on IP addresses with our gateway firewall, we'll 214 08:03.260 --> 08:03.960 want to specify 215 08:03.960 --> 08:08.960 for this web server, either its group membership or its internal address of 10 216 08:08.960 --> 08:10.640 10 zero 181. 217 08:10.640 --> 08:14.280 But we have options to control that behavior right here if we want to. 218 08:14.280 --> 08:16.920 So we'll leave the default of matching on the internal address. 219 08:16.920 --> 08:18.440 We'll click on save again. 220 08:18.440 --> 08:20.480 And then we should test it to verify that it's working. 221 08:20.480 --> 08:24.880 So let's go out to this mint 23 VM here will verify its IP address. 222 08:24.880 --> 08:29.960 And we should be able from here to reach out to the IP address of 2312181 and 223 08:29.960 --> 08:30.280 with the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 223 08:29.960 --> 08:30.280 with the 224 08:30.280 --> 08:34.120 destination NAT rule that should forward our traffic down to the web 10 server. 225 08:34.120 --> 08:35.360 So let's verify that next. 226 08:35.360 --> 08:39.400 However, I just realized I don't have an open console to this mint 23 VM. 227 08:39.400 --> 08:42.640 Let's go back to the vSphere client and open up a remote console. 228 08:42.640 --> 08:44.400 So here's our mint 23. 229 08:44.400 --> 08:48.070 Let me go ahead and right click and we'll just launch a remote console and 230 08:48.070 --> 08:48.720 bring that 231 08:48.720 --> 08:49.720 up. 232 08:49.720 --> 08:50.720 All right. 233 08:50.720 --> 08:52.920 So here is mint 23. 234 08:52.920 --> 08:54.280 Let's verify its IP address. 235 08:54.280 --> 08:56.040 We'll bring up a command prompt to do that. 236 08:56.040 --> 09:01.370 So here let's type in if config just to verify its IP address 23.1.2.74 out WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 236 08:56.040 --> 09:01.370 So here let's type in if config just to verify its IP address 23.1.2.74 out 237 09:01.370 --> 09:02.160 here on the 23 238 09:02.160 --> 09:03.160 network. 239 09:03.160 --> 09:07.930 So if we did a ping to 23.1.2.181 that is the IP address where we have the 240 09:07.930 --> 09:08.760 destination 241 09:08.760 --> 09:10.560 NAT rule here on our tier zero gateway. 242 09:10.560 --> 09:13.250 So if we try to ping that address, we should have destination NAT change the 243 09:13.250 --> 09:13.840 destination 244 09:13.840 --> 09:18.640 address here on our tier zero gateway to the 10 10 zero 181 address. 245 09:18.640 --> 09:20.940 And that would cause it to forward down here to gateway A who would forward it 246 09:20.940 --> 09:21.280 down to 247 09:21.280 --> 09:24.480 the VM and the response would come back in that reverse path. 248 09:24.480 --> 09:26.240 So let's go ahead and do a ping real quick. 249 09:26.240 --> 09:27.240 And that works. 250 09:27.240 --> 09:28.240 That looks pretty good. 251 09:28.240 --> 09:34.040 Also while we're here, let's try an SSH session down to 23.1.2.181. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 251 09:28.240 --> 09:34.040 Also while we're here, let's try an SSH session down to 23.1.2.181. 252 09:34.040 --> 09:38.640 And so this little VM here is really, really old. 253 09:38.640 --> 09:40.920 So let me go ahead and let's use the telnet trick. 254 09:40.920 --> 09:45.160 I'm still going to tell that to 23.1.2.181. 255 09:45.160 --> 09:48.390 But instead of using the well known port for telnet, which is 23, I'm going to 256 09:48.390 --> 09:48.960 put in 257 09:48.960 --> 09:51.000 the IP address at 22 press enter. 258 09:51.000 --> 09:55.740 And if that server is listening on port 22, we should get some response similar 259 09:55.740 --> 09:56.480 to this. 260 09:56.480 --> 09:59.960 So I just want to verify that we have connectivity there on port 22. 261 09:59.960 --> 10:04.920 And let's also try HTTP by opening up a browser right here on this client out WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 261 09:59.960 --> 10:04.920 And let's also try HTTP by opening up a browser right here on this client out 262 10:04.920 --> 10:06.520 on the 23 network. 263 10:06.520 --> 10:09.640 So to do that, we'll click on the icon for the browser and we'll put in the IP 264 10:09.640 --> 10:10.120 address 265 10:10.120 --> 10:11.120 at 23.1.2.181. 266 10:11.120 --> 10:15.780 I'm going to be using HTTP because I don't have HTTPS services here on this 267 10:15.780 --> 10:16.300 little web 268 10:16.300 --> 10:20.080 VM, so we'll test it by using a browser to 23.1.2.181. 269 10:20.080 --> 10:24.660 We'll press enter and boom, this is the web page for that little web 10 server 270 10:24.660 --> 10:25.160 right 271 10:25.160 --> 10:26.160 there. 272 10:26.160 --> 10:28.800 And the reason it's showing the address there is because that took a moment to 273 10:28.800 --> 10:29.180 edit the 274 10:29.180 --> 10:31.920 index.html file on that little web server. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 274 10:29.180 --> 10:31.920 index.html file on that little web server. 275 10:31.920 --> 10:33.580 That's why it's showing up with that IP address. 276 10:33.580 --> 10:36.810 That way when we hit that server, we'll know exactly where that content is 277 10:36.810 --> 10:37.500 coming from. 278 10:37.500 --> 10:39.640 It's coming from this little web 10 server right here. 279 10:39.640 --> 10:43.500 So we've tested connectivity from this Mint 23 machine down to the server, 280 10:43.500 --> 10:44.700 which also confirms 281 10:44.700 --> 10:48.300 we have nullity connectivity, but also that the destination that is working. 282 10:48.300 --> 10:51.210 The last thing I want to do is verify Mint 20, so we deployed that earlier, let 283 10:51.210 --> 10:51.480 's go 284 10:51.480 --> 10:53.400 ahead and power it on. 285 10:53.400 --> 10:57.080 So here for Mint 20, it's showing us the IP address at 10.0.153. 286 10:57.080 --> 11:00.830 We'll verify that at the VM itself and we'll also verify we have basic WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 286 10:57.080 --> 11:00.830 We'll verify that at the VM itself and we'll also verify we have basic 287 11:00.830 --> 11:01.920 connectivity. 288 11:01.920 --> 11:03.760 So here is VM 20. 289 11:03.760 --> 11:07.580 We'll open up a command prompt and we'll type in IF config just to confirm the 290 11:07.580 --> 11:08.340 IP address. 291 11:08.340 --> 11:12.740 Sure enough, it is at 10.0.153, which is what it said right here on the vSphere 292 11:12.740 --> 11:13.600 client. 293 11:13.600 --> 11:14.600 Fantastic. 294 11:14.600 --> 11:17.460 So we'll do a trace out to 8888 and that looks good. 295 11:17.460 --> 11:18.460 I'll stop that. 296 11:18.460 --> 11:21.390 Just want to make sure we're going out to the internet and let's also verify we 297 11:21.390 --> 11:21.600 can 298 11:21.600 --> 11:25.520 reach our web 10 machine right there, which is at 1010 0 181. 299 11:25.520 --> 11:27.480 And we'll try that right here from Mint 20. 300 11:27.480 --> 11:32.400 So we'll do a ping to 10.10.0.181, press enter and that's working. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 300 11:27.480 --> 11:32.400 So we'll do a ping to 10.10.0.181, press enter and that's working. 301 11:32.400 --> 11:35.360 Let's also just to confirm we're connected to the right device. 302 11:35.360 --> 11:39.820 Let's also bring up a browser and here at the browser, we'll go to 10.10.0.181, 303 11:39.820 --> 11:40.180 press 304 11:40.180 --> 11:42.960 enter and sure enough, that is working. 305 11:42.960 --> 11:45.950 So now that we've verified our basic connectivity in the next video, let's 306 11:45.950 --> 11:47.120 begin our configuration 307 11:47.120 --> 11:50.640 of Gateway firewall and we'll start here on Gateway 0. 308 11:50.640 --> 12:00.640 [BLANK_AUDIO]