BeginnerPublished 2026-07-17
CCNA Foundations: Static NAT — One-to-One Inside/Outside Mapping
Archive lab
Deploy a single-edge router performing static one-to-one NAT so an inside host has a fixed public address. You will mark inside/outside interfaces, create the static NAT mapping, and verify reachability to an internet host and the translation table. The lab is intentionally small but enterprise-clean, with a routed inside transit, an access switch for the user LAN, and an external host representing the internet.
Learning objectives
- Identify and mark NAT inside and outside interfaces on an edge router
- Configure a one-to-one static NAT mapping for a specific inside host
- Verify NAT operation using translation tables and end-to-end tests from hosts
- Apply static routing to ensure return reachability for NATed flows
Troubleshooting focus
- If CLIENT10 cannot reach the outside host: Verify CLIENT10 IP and default gateway (10.10.10.10/24 via 10.10.10.1) and that RTR-DIST has a default route to RTR-EDGE.; On RTR-EDGE, ensure the internal transit interface is marked as NAT inside and the public interface as NAT outside.; Confirm the static mapping pairs 10.10.10.10 with 203.0.113.3 exactly.; Run
show ip nat translationsand initiate fresh pings to watch for entries. - If the outside host cannot reach the inside-global 203.0.113.3: Ensure INTERNET-HOST’s default route points to 203.0.113.1 and that it can ARP for 203.0.113.3 (the edge should respond).; Confirm RTR-EDGE still has a route to 10.10.10.0/24 via 10.0.12.1 so post-NAT traffic forwards internally.
- If translations appear but traffic still fails: check interface status (up/up), masks, and that you didn’t mix up the /29 and /30 subnets.
Topology
Subscribe to preview this lab's topology.
See plansGrade your work
How this lab is graded
- Build it your way. Where a lab lets you choose a value — a VLAN name, an interface description — grading checks that you configured it, not which name you picked. Names that another line has to reference, like an ACL applied with
access-class, are stated in the guide and do have to match. - Addresses, modes and protocol keywords are exact. An IP address, a subnet mask,
switchport mode trunk, an encapsulation — these carry the meaning of the lab, so they are graded as written in the guide. - Grading reads your saved configuration. Export the lab from CML after you have configured it, and make sure anything you set is in the running-config — a change that only exists in a terminal session never reaches the grader.
- You can submit as many times as you like. Your best score stands, and each attempt tells you which checks passed so you can work the gaps.
- Scored something you believe is correct? Use Report an issue on this page — that is exactly how the grading fixes in the changelog got found.
Create a free account to submit your lab for grading.
Create a free accountFound a problem with this lab?
Please sign in to report a problem — tying it to your attempts lets us reproduce and fix it faster.