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 08:05] 114.119.155.78 old revision restored (2017/06/23 01:48) |
icnd1:nat [2024/06/02 15:50] (current) 18.221.86.245 old revision restored (2024/03/14 07:59) |
||
---|---|---|---|
Line 82: | Line 82: | ||
- | 200.1.1.0 255.255.255.0 | + | * 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. × | You answered this question correctly. × | ||
Line 97: | Line 94: | ||
**With static NAT, performing translation for inside addresses only, what causes NAT table entries to be created?** | **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. × | You answered this question correctly. × | ||
**Explanation: | **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. | **With static NAT, the entries are statically configured. Because the question mentions translation for inside addresses, the inside keyword is needed in the command. |