Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated:
1
00:00:01,040 --> 00:00:07,839
Welcome to Jeremy’s IT Lab. This is a free,\xa0\n
2
00:00:07,839 --> 00:00:13,919
videos, please subscribe to follow along with the\xa0\n
3
00:00:13,919 --> 00:00:17,920
and share the video to help spread this\xa0\n
4
00:00:19,280 --> 00:00:23,839
In this video we will finish up the topic\xa0\n
5
00:00:24,879 --> 00:00:27,759
NAT is topic 4.1 of the CCNA exam.\xa0\xa0
6
00:00:28,800 --> 00:00:34,799
In Day 44 I introduced NAT and covered static\xa0\n
7
00:00:36,079 --> 00:00:41,199
After this video, I think you’ll have no problems\xa0\n
8
00:00:42,960 --> 00:00:48,240
Here’s what we’ll cover in this video. First, I\xa0\n
9
00:00:48,240 --> 00:00:53,200
I didn’t mention in the last video. Then\xa0\n
10
00:00:53,200 --> 00:00:58,719
manually map addresses one-to-one, but instead the\xa0\n
11
00:00:59,759 --> 00:01:03,519
And then another very important\xa0\n
12
00:01:03,520 --> 00:01:10,400
which translates not only the IP address, but\xa0\n
13
00:01:10,400 --> 00:01:16,880
useful because it allows many devices to share\xa0\n
14
00:01:16,879 --> 00:01:22,399
until the end of the video for a bonus practice\xa0\n
15
00:01:24,480 --> 00:01:30,400
First, some review about static NAT. Static\xa0\n
16
00:01:30,400 --> 00:01:36,480
mappings of private IP addresses to public\xa0\n
17
00:01:36,480 --> 00:01:40,719
host is sent to the outside network, the\xa0\n
18
00:01:42,000 --> 00:01:50,319
So, I have mapped inside local address\xa0\n
19
00:01:50,959 --> 00:02:00,000
and also mapped 192.168.0.168 to 100.0.0.2 Then,\xa0\n
20
00:02:00,000 --> 00:02:09,680
at 8.8.8.8, it sends a packet with source IP\xa0\n
21
00:02:09,680 --> 00:02:16,000
translates the source address to 100.0.0.1, a\xa0\n
22
00:02:16,000 --> 00:02:23,039
reply, the destination is the public IP address.\xa0\n
23
00:02:23,039 --> 00:02:31,039
to 192.168.0.167 and forwards it to PC1. Okay,\xa0\n
24
00:02:31,039 --> 00:02:34,079
but let me demonstrate one other\xa0\n
25
00:02:35,759 --> 00:02:41,359
This one-to-one mapping of IP addresses doesn’t\xa0\n
26
00:02:41,360 --> 00:02:47,760
resources, it also allows external hosts to access\xa0\n
27
00:02:49,039 --> 00:02:53,519
So, without PC1 initiating communication\xa0\n
28
00:02:53,520 --> 00:03:01,040
to destination IP 100.0.0.1, and because of that\xa0\n
29
00:03:01,039 --> 00:03:09,759
it to 192.168.0.167 and forward it to PC1, and\xa0\n
30
00:03:10,319 --> 00:03:16,159
not just from inside to outside, but also\xa0\n
31
00:03:16,159 --> 00:03:21,359
to make that clear since I didn’t mention it\xa0\n
32
00:03:23,280 --> 00:03:26,159
In dynamic NAT, the router dynamically maps inside\xa0\xa0
33
00:03:26,159 --> 00:03:32,159
local addresses to inside global addresses\xa0\n
34
00:03:32,159 --> 00:03:37,039
‘map this IP address to this IP address,\xa0\n
35
00:03:37,759 --> 00:03:42,479
The router makes those mappings automatically, and\xa0\n
36
00:03:43,280 --> 00:03:49,439
Here’s how it works in Cisco IOS. An ACL is used\xa0\n
37
00:03:50,400 --> 00:03:55,039
Okay, this part is important, because it’s a\xa0\n
38
00:03:55,039 --> 00:04:01,120
very common use. ACLs can be used to indicate\xa0\n
39
00:04:01,120 --> 00:04:06,719
should be blocked, you already know that. But\xa0\n
40
00:04:07,520 --> 00:04:13,840
If the source IP of a packet is permitted by the\xa0\n
41
00:04:14,479 --> 00:04:20,480
However if the source IP is denied by the ACL, the\xa0\n
42
00:04:20,480 --> 00:04:25,439
mean the traffic will be dropped! We’re simply\xa0\n
43
00:04:25,439 --> 00:04:31,279
translated, we’re not using it to drop traffic,\xa0\n
44
00:04:31,279 --> 00:04:37,119
with the IP ACCESS-GROUP command. Anyway, when\xa0\n
45
00:04:38,240 --> 00:04:44,079
Then, a NAT pool is used to define the available\xa0\n
46
00:04:44,079 --> 00:04:53,599
translation. For example, on R1 I configured ACL\xa0\n
47
00:04:53,600 --> 00:05:01,920
other traffic. I also configured NAT POOL1,\xa0\n
48
00:05:03,279 --> 00:05:09,679
That means if a packet with a source IP permitted\xa0\n
49
00:05:09,680 --> 00:05:17,840
address from POOL1. So, PC1 sends a packet, and\xa0\n
50
00:05:17,839 --> 00:05:25,199
translates the source IP to an address from\xa0\n
51
00:05:25,199 --> 00:05:30,800
and R1 translates the address back. So, it\xa0\n
52
00:05:31,600 --> 00:05:37,360
The difference is that, instead of manually\xa0\n
53
00:05:37,360 --> 00:05:43,040
to 100.0.0.1, R1 did it automatically\xa0\n
54
00:05:44,240 --> 00:05:49,439
Now, I want to emphasize this point. If the\xa0\n
55
00:05:50,000 --> 00:05:53,920
it doesn’t mean the packet will be dropped,\xa0\n
56
00:05:55,839 --> 00:06:00,079
Let me explain a few more points about dynamic\xa0\n
57
00:06:01,279 --> 00:06:05,119
Although they are dynamically assigned,\xa0\n
58
00:06:05,120 --> 00:06:11,840
one inside local IP address per inside global IP\xa0\n
59
00:06:11,839 --> 00:06:17,279
addresses available, if they are all currently\xa0\n
60
00:06:18,079 --> 00:06:25,279
In the previous example, the ACL specified a /24\xa0\n
61
00:06:25,279 --> 00:06:31,199
only had 10 inside global addresses. So, there\xa0\n
62
00:06:32,240 --> 00:06:36,639
What happens if there are no available\xa0\n
63
00:06:37,680 --> 00:06:43,199
If a packet from another inside host arrives and\xa0\n
64
00:06:43,199 --> 00:06:48,159
the router will drop the packet. The host\xa0\n
65
00:06:48,160 --> 00:06:53,360
until one of the inside global IP addresses\xa0\n
66
00:06:54,480 --> 00:07:01,040
Dynamic NAT entries will time out automatically\xa0\n
67
00:07:01,040 --> 00:07:06,080
in our previous example if PC1 stops\xa0\n
68
00:07:06,079 --> 00:07:12,000
the inside global address 100.0.0.1 would become\xa0\n
69
00:07:13,040 --> 00:07:18,319
Or you can use the CLEAR IP NAT TRANSLATION\xa0\n
70
00:07:20,079 --> 00:07:28,159
Let me demonstrate that NAT pool exhaustion. A\xa0\n
71
00:07:28,879 --> 00:07:37,759
It is translated to 100.0.0.1, and then forwarded.\xa0\n
72
00:07:37,759 --> 00:07:43,759
and is translated to 100.0.0.2, and then\xa0\n
73
00:07:43,759 --> 00:07:50,319
and now those ten inside global IP addresses,\xa0\n
74
00:07:51,519 --> 00:07:57,839
If host 192.168.0.98 tries to send some\xa0\n
75
00:07:58,959 --> 00:08:06,560
There are no addresses available, so the router\xa0\n
76
00:08:06,560 --> 00:08:12,639
stops communicating over the Internet. After\xa0\n
77
00:08:13,839 --> 00:08:21,839
If 192.168.0.98 tries to send that traffic\xa0\n
78
00:08:21,839 --> 00:08:27,039
and it can reach the Internet. So, that’s a\xa0\n
79
00:08:27,920 --> 00:08:33,920
Although both are one-to-one mappings, static\xa0\n
80
00:08:33,919 --> 00:08:38,479
mappings are temporary, they will time out when\xa0\n
81
00:08:38,480 --> 00:08:44,720
can use that same public IP address. However,\xa0\n
82
00:08:44,720 --> 00:08:50,879
IP address at the same time. To do that, you\xa0\n
83
00:08:52,559 --> 00:08:57,039
But before looking at Port Address Translation,\xa0\n
84
00:08:58,159 --> 00:09:02,719
First, just like in static NAT you must\xa0\n
85
00:09:03,679 --> 00:09:09,039
Then define the traffic that should be translated.\xa0\n
86
00:09:09,039 --> 00:09:16,799
ACL will be translated. So, this ACL tells R1\xa0\n
87
00:09:18,000 --> 00:09:24,320
Then define the pool of inside global IP\xa0\n
88
00:09:24,320 --> 00:09:29,200
then the pool name. After that you\xa0\n
89
00:09:29,200 --> 00:09:37,520
and then the last IP address in the range. So I\xa0\n
90
00:09:38,559 --> 00:09:43,439
Finally, you have to specify the prefix\xa0\n
91
00:09:43,440 --> 00:09:50,320
or the NETMASK option. IOS uses this to check\xa0\n
92
00:09:50,320 --> 00:09:55,120
of the range, are in the same subnet. If\xa0\n
93
00:09:56,559 --> 00:10:02,959
Finally, configure dynamic NAT by mapping the\xa0\n
94
00:10:02,960 --> 00:10:08,720
and then instead of STATIC use LIST, followed\xa0\n
95
00:10:08,720 --> 00:10:14,879
followed by the pool name. And that’s all there\xa0\n
96
00:10:14,879 --> 00:10:20,720
complicated than static NAT configuration, but\xa0\n
97
00:10:20,720 --> 00:10:28,960
complete I sent some traffic from PC1 and PC2 to\xa0\n
98
00:10:30,559 --> 00:10:36,639
So, here’s R1’s table after sending pings as\xa0\n
99
00:10:37,600 --> 00:10:44,480
Notice there are three entries for each\xa0\n
100
00:10:45,120 --> 00:10:53,600
and three for 192.168.0.168 to 100.0.0.2. When\xa0\n
101
00:10:53,600 --> 00:10:59,840
inside global mappings, these entries are created.\xa0\n
102
00:10:59,840 --> 00:11:05,920
when translations are made, separate entries like\xa0\n
103
00:11:07,120 --> 00:11:11,360
Now, those UDP and ICMP entries will\xa0\n
104
00:11:11,919 --> 00:11:16,719
but the original dynamic mappings themselves\xa0\n
105
00:11:17,279 --> 00:11:20,079
and each time a translation\xa0\n
106
00:11:21,200 --> 00:11:26,720
So, dynamic NAT mappings actually last quite\xa0\n
107
00:11:26,720 --> 00:11:32,320
if you want, but that’s not something you need\xa0\n
108
00:11:32,320 --> 00:11:38,560
entries look like the static NAT entries from Day\xa0\n
109
00:11:39,120 --> 00:11:42,560
these entries will be cleared because\xa0\n
110
00:11:44,240 --> 00:11:46,480
Now here’s SHOW IP NAT STATISTICS.\xa0\xa0
111
00:11:47,360 --> 00:11:50,960
Note that I entered this command when all\xa0\n
112
00:11:51,679 --> 00:11:57,279
so it displays 6 total active translations.\xa0\n
113
00:11:58,159 --> 00:12:02,959
So, all of those entries were dynamic, but can\xa0\n
114
00:12:03,600 --> 00:12:09,680
They are those UDP and ICMP temporary entries\xa0\n
115
00:12:09,679 --> 00:12:14,639
details of extended entries aren’t something you\xa0\n
116
00:12:14,639 --> 00:12:21,279
point out here is that you can confirm the dynamic\xa0\n
117
00:12:21,279 --> 00:12:26,959
with static NAT, the two SHOW commands you should\xa0\n
118
00:12:27,519 --> 00:12:33,600
and SHOW IP NAT STATISTICS. You should be familiar\xa0\n
119
00:12:35,120 --> 00:12:40,399
Now let’s move to PAT, Port Address Translation,\xa0\n
120
00:12:41,440 --> 00:12:45,680
It translates both the IP address and the\xa0\n
121
00:12:46,480 --> 00:12:52,000
And what’s the purpose of translating the port\xa0\n
122
00:12:52,000 --> 00:12:57,679
communication flow between internal hosts and\xa0\n
123
00:12:57,679 --> 00:13:04,639
be used by many different internal hosts. TCP\xa0\n
124
00:13:04,639 --> 00:13:10,879
which means there are over 65,000 port numbers.\xa0\n
125
00:13:10,879 --> 00:13:16,559
local address is using which inside global\xa0\n
126
00:13:16,559 --> 00:13:22,079
track of the communication flows by using unique\xa0\n
127
00:13:23,279 --> 00:13:32,879
PC1 sends a DNS message to 8.8.8.8. Its source IP\xa0\n
128
00:13:32,879 --> 00:13:42,720
port, 54321. PC2 also sends a DNS message\xa0\n
129
00:13:43,679 --> 00:13:49,199
It also selects a random source port, and it\xa0\n
130
00:13:49,200 --> 00:13:57,520
54321. R1 translates the source IP of PC1’s\xa0\n
131
00:13:57,519 --> 00:14:06,319
port the same, 54321. For PC2’s message, it\xa0\n
132
00:14:06,320 --> 00:14:13,040
but it changes the source port to 54322. Why\xa0\n
133
00:14:13,039 --> 00:14:18,480
the communication flows. If both flows\xa0\n
134
00:14:18,480 --> 00:14:23,440
when the replies come from the server, R1\xa0\n
135
00:14:24,720 --> 00:14:29,840
So, the server sends the replies to\xa0\n
136
00:14:31,279 --> 00:14:39,279
but one has destination port 54321, and the\xa0\n
137
00:14:39,279 --> 00:14:47,279
R1 knows to send this reply to PC1 and this reply\xa0\n
138
00:14:47,279 --> 00:14:52,000
same random source port number, because I wanted\xa0\n
139
00:14:53,120 --> 00:14:56,960
However, if PC2 selected a different\xa0\n
140
00:14:57,519 --> 00:15:00,079
then R1 would have no need\xa0\n
141
00:15:00,639 --> 00:15:05,840
It would simply use the source port PC2 selected\xa0\n
142
00:15:06,799 --> 00:15:13,279
So, that’s how PAT works. Because many inside\xa0\n
143
00:15:13,279 --> 00:15:18,639
is very useful for preserving public IP addresses,\xa0\n
144
00:15:19,600 --> 00:15:24,879
Of the three types we have covered, static\xa0\n
145
00:15:24,879 --> 00:15:29,679
widely used because it allows so many inside\xa0\n
146
00:15:31,279 --> 00:15:38,480
Here’s how to configure PAT. It’s basically the\xa0\n
147
00:15:38,480 --> 00:15:44,560
first define the inside and outside interfaces.\xa0\n
148
00:15:44,559 --> 00:15:52,399
by using an ACL. Again, traffic permitted by the\xa0\n
149
00:15:52,399 --> 00:16:00,720
inside global IP addresses. This time I defined\xa0\n
150
00:16:02,000 --> 00:16:06,480
Chances are, unless the internal network is\xa0\n
151
00:16:06,480 --> 00:16:13,360
IP address, but this provides some scalability,\xa0\n
152
00:16:13,360 --> 00:16:19,759
a prefix length of 24 bits. As long as the\xa0\n
153
00:16:19,759 --> 00:16:26,960
this specified prefix length doesn’t\xa0\n
154
00:16:26,960 --> 00:16:34,879
all fit in the subnet 100.0.0.0/24, so the command\xa0\n
155
00:16:35,679 --> 00:16:42,159
It’s the same as for dynamic NAT, except at\xa0\n
156
00:16:42,159 --> 00:16:52,879
INSIDE SOURCE LIST 1 POOL POOL1 OVERLOAD. So,\xa0\n
157
00:16:53,679 --> 00:16:57,359
Let’s take a look at the NAT\xa0\n
158
00:16:59,120 --> 00:17:04,799
So, here are the translations on R1. One big\xa0\n
159
00:17:04,799 --> 00:17:10,799
is that those one-to-one dynamic mapping entries\xa0\n
160
00:17:10,799 --> 00:17:16,960
there are no one-to-one mappings, they’re many\xa0\n
161
00:17:16,960 --> 00:17:26,400
inside global address. As you can see, both\xa0\n
162
00:17:27,359 --> 00:17:32,240
They both selected different source port numbers,\xa0\n
163
00:17:33,359 --> 00:17:40,240
It will use port number 63925 to track the\xa0\n
164
00:17:40,799 --> 00:17:48,399
and it will use port number 59549 to track the\xa0\n
165
00:17:49,359 --> 00:17:54,879
And here’s SHOW IP NAT STATISTICS. Feel free\xa0\n
166
00:17:54,880 --> 00:17:59,840
you’re interested, but now I’m going to move on\xa0\n
167
00:18:01,440 --> 00:18:06,080
One more way to configure PAT, and probably\xa0\n
168
00:18:06,079 --> 00:18:10,799
router to use its own public IP address\xa0\n
169
00:18:12,000 --> 00:18:16,240
So, as always you must configure the inside\xa0\n
170
00:18:17,119 --> 00:18:21,119
And then just like before use an ACL to\xa0\n
171
00:18:22,480 --> 00:18:25,360
Here’s the difference with the\xa0\n
172
00:18:26,480 --> 00:18:30,000
Instead of specifying a POOL\xa0\n
173
00:18:30,000 --> 00:18:36,640
you specify INTERFACE, then the outside\xa0\n
174
00:18:37,920 --> 00:18:45,600
So, R1 will translate the source IP address of\xa0\n
175
00:18:45,599 --> 00:18:54,639
its G0/0 interface, 203.0.113.1. It will also use\xa0\n
176
00:18:54,640 --> 00:18:59,600
so it can keep track of them and multiple\xa0\n
177
00:19:01,359 --> 00:19:08,000
Let me demonstrate that. PC1 and PC2\xa0\n
178
00:19:09,039 --> 00:19:16,960
Notice that they both selected a different random\xa0\n
179
00:19:18,240 --> 00:19:23,200
R1 translates the source IP address of both\xa0\n
180
00:19:23,200 --> 00:19:30,960
G0/0 interface, 203.0.113.1. Because both\xa0\n
181
00:19:30,960 --> 00:19:36,960
there is no need to translate the port numbers.\xa0\n
182
00:19:36,960 --> 00:19:42,319
them back and sends them to their correct\xa0\n
183
00:19:42,319 --> 00:19:51,839
R1 knows which to translate back to 192.168.0.167\xa0\n
184
00:19:52,720 --> 00:19:55,200
Here is R1’s NAT translation table after that.\xa0\xa0
185
00:19:56,559 --> 00:20:06,079
Notice that both 192.168.0.167 and .168\xa0\n
186
00:20:06,079 --> 00:20:10,639
Also notice that, as I said, there was no need\xa0\n
187
00:20:10,640 --> 00:20:17,759
because they were already unique. And here is SHOW\xa0\n
188
00:20:17,759 --> 00:20:22,559
check this command out if you want, but going in\xa0\n
189
00:20:24,160 --> 00:20:26,400
Here are the new commands\xa0\nwe covered in this video.\xa0\xa0
190
00:20:27,279 --> 00:20:31,759
If you don’t remember these commands, go back\xa0\n
191
00:20:31,759 --> 00:20:37,200
practice them in packet tracer either by making\xa0\n
192
00:20:38,880 --> 00:20:42,320
Before moving on to the quiz, let’s\xa0\n
193
00:20:43,440 --> 00:20:49,120
First, I demonstrated how static NAT not only\xa0\n
194
00:20:49,119 --> 00:20:53,599
but it also allows hosts on external\xa0\n
195
00:20:53,599 --> 00:21:02,559
using the mapped inside global IP address. Then I\xa0\n
196
00:21:02,559 --> 00:21:08,879
is probably the most common type of NAT. It allows\xa0\n
197
00:21:08,880 --> 00:21:15,280
all at the same time. My home router, for\xa0\n
198
00:21:15,279 --> 00:21:21,599
of the devices in my home such as my PC, phones\xa0\n
199
00:21:21,599 --> 00:21:27,839
public IP address when accessing the Internet. And\xa0\n
200
00:21:27,839 --> 00:21:34,000
a bonus question from Boson Software’s ExSim\xa0\n
201
00:21:35,839 --> 00:21:41,119
Which of the following NAT types best fulfills\xa0\n
202
00:21:41,839 --> 00:21:43,839
Pause the video now to think about your answer.
203
00:21:48,640 --> 00:21:55,520
Okay, the answer is D, NAT Overload, aka PAT.\xa0\n
204
00:21:55,519 --> 00:22:00,480
use a single public IP address because the\xa0\n
205
00:22:00,480 --> 00:22:06,559
using the Layer 4 port number. This means most\xa0\n
206
00:22:06,559 --> 00:22:12,559
instead of each device requiring a unique\xa0\n
207
00:22:14,640 --> 00:22:18,240
Which of the following dynamic NAT\xa0\n
208
00:22:18,240 --> 00:22:25,839
local addresses from 172.16.1.0/24 to\xa0\n
209
00:22:27,519 --> 00:22:29,599
Pause the video now to think about the answer.
210
00:22:34,400 --> 00:22:41,840
Okay, the answer is B. So, what’s wrong with\xa0\n
211
00:22:41,839 --> 00:22:56,240
255.255.255.128 is /25, but the address range is\xa0\n
212
00:22:56,240 --> 00:23:04,559
not fall in the 203.0.113.0/25 subnet, so the\xa0\n
213
00:23:05,359 --> 00:23:12,000
The ACL’s mask is 255.255.255.0, but\xa0\n
214
00:23:12,799 --> 00:23:18,720
so /24 should be 0.0.0.255.\xa0\nOkay, let’s go to question 3.
215
00:23:21,279 --> 00:23:26,799
Dynamic NAT is configured on R1 and a pool\xa0\n
216
00:23:27,920 --> 00:23:31,680
Currently, all 10 addresses\xa0\n
217
00:23:31,680 --> 00:23:35,039
but another inside host attempts\xa0\n
218
00:23:35,680 --> 00:23:40,400
What does R1 do with this packet? Pause\xa0\n
219
00:23:45,119 --> 00:23:47,839
Okay, the answer is B, it discards the packet.\xa0\xa0
220
00:23:48,880 --> 00:23:53,360
When dynamic NAT is being used and a packet\xa0\n
221
00:23:53,359 --> 00:23:59,359
addresses in the pool, the router will simply\xa0\n
222
00:24:00,720 --> 00:24:04,160
Which of the following dynamic NAT\xa0\n
223
00:24:04,160 --> 00:24:11,040
local addresses from 10.0.1.0/27 to use the\xa0\n
224
00:24:12,000 --> 00:24:17,839
Pause the video now to think about the answer.
225
00:24:19,279 --> 00:24:23,359
Okay the answer is A. It’s the\xa0\n
226
00:24:23,359 --> 00:24:27,759
/27 wildcard mask in the ACL,\xa0\n
227
00:24:28,400 --> 00:24:33,759
and assigns the inside and outside interfaces\xa0\n
228
00:24:36,400 --> 00:24:39,840
After specifying the inside\xa0\n
229
00:24:39,839 --> 00:24:45,839
you issue the following commands on R1. What\xa0\n
230
00:24:47,359 --> 00:24:50,639
subnet? Pause the video now\xa0\nto think about the answer.
231
00:24:55,920 --> 00:24:59,759
Okay, the answer is C, the packets\xa0\n
232
00:24:59,759 --> 00:25:05,039
R1. When an ACL is used to identify\xa0\n
233
00:25:05,039 --> 00:25:10,399
such as in dynamic NAT and PAT, packets\xa0\n
234
00:25:10,400 --> 00:25:16,480
and packets denied by the ACL won’t be translated.\xa0\n
235
00:25:16,480 --> 00:25:21,759
it doesn’t mean the router will drop the packets,\xa0\n
236
00:25:21,759 --> 00:25:27,839
for the quiz. Now let’s take a look at a bonus\xa0\n
237
00:25:30,240 --> 00:25:35,759
Okay, here's today's Boson ExSim practice\xa0\n
238
00:25:35,759 --> 00:25:42,799
an HTTP connection to HostB through a NAT router\xa0\n
239
00:25:42,799 --> 00:25:48,480
addresses. Here they are. Which of the following\xa0\n
240
00:25:48,480 --> 00:25:53,599
when you issue the SHOW IP NAT TRANSLATIONS\xa0\n
241
00:25:54,559 --> 00:25:58,879
Okay, pause the video now. Take a look at\xa0\n
242
00:26:04,319 --> 00:26:11,119
Okay let's check. So, first off, what should the\xa0\n
243
00:26:11,920 --> 00:26:19,600
They should be the IP address of the destination\xa0\n
244
00:26:19,599 --> 00:26:23,839
are correct. Now how about the inside\xa0\n
245
00:26:24,799 --> 00:26:31,440
That should be the IP address of the source host,\xa0\n
246
00:26:31,440 --> 00:26:42,400
this case. So, 10.1.7.7. So that means A and D are\xa0\n
247
00:26:42,960 --> 00:26:47,920
which is the IP address of RouterA's internal\xa0\n
248
00:26:47,920 --> 00:26:54,080
the correct answer is either B or C. Now, how\xa0\n
249
00:26:55,119 --> 00:27:06,399
10.1.7.1, like in B, or 203.0.113.62? So, 10.1.7.1\xa0\n
250
00:27:07,119 --> 00:27:14,319
and 203.0.113.62 is the IP address of RouterA's\xa0\n
251
00:27:15,039 --> 00:27:19,920
and translating to the IP address of the router's\xa0\n
252
00:27:19,920 --> 00:27:26,240
address of the external interface, the public IP\xa0\n
253
00:27:27,599 --> 00:27:34,559
So I will click on show answer and indeed that\xa0\n
254
00:27:34,559 --> 00:27:42,159
that answer. You can pause the video now to read\xa0\n
255
00:27:46,400 --> 00:27:49,920
Okay, so that was a quick look at\xa0\n
256
00:27:50,480 --> 00:27:54,799
These are without a doubt the best practice\xa0\n
257
00:27:54,799 --> 00:28:02,079
them. If you want to get Boson ExSim, please\xa0\n
258
00:28:02,079 --> 00:28:04,480
There are supplementary materials for this video.\xa0\xa0
259
00:28:05,440 --> 00:28:08,240
There is a flashcard deck to\xa0\n
260
00:28:09,359 --> 00:28:13,519
There will also be a packet tracer practice\xa0\n
261
00:28:14,319 --> 00:28:19,759
That will be in the next video. Sign up for my\xa0\n
262
00:28:19,759 --> 00:28:23,839
and I’ll send you all of the flashcards\xa0\n
263
00:28:26,000 --> 00:28:30,480
Before finishing today’s video I want\xa0\n
264
00:28:31,119 --> 00:28:38,000
To join, please click the ‘Join’ button under the\xa0\n
265
00:28:38,000 --> 00:28:45,599
Njoku, Viktor, Roger, Raj, Kenneth, Seamus, H\xa0\n
266
00:28:45,599 --> 00:28:52,319
Gustavo, Anthony, Benjamin, Justin, Prakaash,\xa0\n
267
00:28:52,319 --> 00:28:58,559
Funnydart, Velvijaykum, Mark, Yousif, Boson\xa0\n
268
00:28:58,559 --> 00:29:02,559
Sorry if I pronounced your name incorrectly,\xa0\n
269
00:29:03,519 --> 00:29:09,839
This is the list of JCNP-level members at the\xa0\n
270
00:29:10,720 --> 00:29:16,000
If you signed up recently and your name isn’t\xa0\n
271
00:29:17,759 --> 00:29:20,879
Thank you for watching. Please\xa0\n
272
00:29:20,880 --> 00:29:25,840
like the video, leave a comment, and share the\xa0\n
273
00:29:26,640 --> 00:29:32,240
If you want to leave a tip, check the links in the\xa0\n
274
00:29:32,240 --> 00:29:38,880
and accept BAT, or Basic Attention Token, tips\xa0\n
23453
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.