icnd1:nat
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
icnd1:nat [2024/03/14 07:44] 114.119.155.78 old revision restored (2023/10/10 22:29) |
icnd1:nat [2024/04/27 08:10] (current) 52.211.143.139 old revision restored (2023/11/01 22:20) |
||
|---|---|---|---|
| Line 53: | Line 53: | ||
| ===== Chapter Questions ===== | ===== Chapter Questions ===== | ||
| ==== One ==== | ==== One ==== | ||
| - | **Examine the following show command output on a router configured for dynamic NAT:** | + | Examine the following show command output on a router configured for dynamic NAT: |
| < | < | ||
| -- Inside Source | -- Inside Source | ||
| Line 67: | Line 67: | ||
| </ | </ | ||
| - | '' | + | The NAT pool does not have enough entries to satisfy all requests. |
| The problem is not related to NAT, based on the information in the command output. | The problem is not related to NAT, based on the information in the command output. | ||
| Line 76: | Line 76: | ||
| You answered this question correctly. × | You answered this question correctly. × | ||
| - | **Explanation: | + | Explanation: |
| The last line mentions that the pool has seven addresses, with all seven allocated, with the misses counter close to 1000 - meaning that close to 1000 new flows were rejected because of insufficient space in the NAT pool. | The last line mentions that the pool has seven addresses, with all seven allocated, with the misses counter close to 1000 - meaning that close to 1000 new flows were rejected because of insufficient space in the NAT pool. | ||
| - | ==== Two ==== | ||
| - | **Which of the following summarized subnets represent routes that could have been created for CIDR’s goal to reduce the size of Internet routing tables?** | ||
| - | |||
| - | |||
| - | 200.1.1.0 255.255.255.0 | ||
| - | |||
| - | '' | ||
| - | |||
| - | 10.1.0.0 255.255.0.0 | ||
| - | |||
| - | 10.0.0.0 255.255.255.0 | ||
| - | You answered this question correctly. × | ||
| - | |||
| - | **Explanation: | ||
| - | CIDR’s original intent was to allow the summarization of multiple Class A, B, and C networks to reduce the size of Internet routing tables. Of the answers, only 200.1.0.0 255.255.0.0 summarizes multiple networks. | ||
| - | |||
| - | ==== Three ==== | ||
| - | **With static NAT, performing translation for inside addresses only, what causes NAT table entries to be created?** | ||
| - | |||
| - | |||
| - | '' | ||
| - | |||
| - | The first packet from the inside network to the outside network | ||
| - | |||
| - | Configuration using the ip nat outside source command | ||
| - | |||
| - | The first packet from the outside network to the inside network | ||
| - | You answered this question correctly. × | ||
| - | |||
| - | Explanation: | ||
| - | With static NAT, the entries are statically configured. Because the question mentions translation for inside addresses, the inside keyword is needed in the command. | ||
icnd1/nat.1710402274.txt.gz · Last modified: 2024/03/14 07:44 by 114.119.155.78
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
