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:54] 114.119.130.33 old revision restored (2023/10/06 08:23) |
icnd1:nat [2024/06/11 00:56] (current) 3.149.243.18 old revision restored (2024/03/14 08:01) |
||
|---|---|---|---|
| Line 50: | Line 50: | ||
| R1#clear ip nat translation * | R1#clear ip nat translation * | ||
| </ | </ | ||
| + | |||
| + | ===== Chapter Questions ===== | ||
| + | ==== One ==== | ||
| + | **Examine the following show command output on a router configured for dynamic NAT:** | ||
| + | < | ||
| + | -- Inside Source | ||
| + | |||
| + | access-list 1 pool fred refcount 2288 | ||
| + | |||
| + | pool fred: netmask 255.255.255.240 | ||
| + | |||
| + | start 200.1.1.1 end 200.1.1.7 | ||
| + | |||
| + | type generic, total addresses 7, allocated 7 (100%), misses 965 | ||
| + | Users are complaining about not being able to reach the Internet. Which of the following is the most likely cause? | ||
| + | </ | ||
| + | |||
| + | '' | ||
| + | |||
| + | The problem is not related to NAT, based on the information in the command output. | ||
| + | |||
| + | The command output does not supply enough information to identify the problem. | ||
| + | |||
| + | Standard ACL 1 cannot be used; an extended ACL must be used. | ||
| + | You answered this question correctly. × | ||
| + | |||
| + | **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. | ||
| + | ==== 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.1710402860.txt.gz · Last modified: 2024/03/14 07:54 by 114.119.130.33
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
