IntermediatePublished 2026-07-02
Static PAT: Port Forwarding to an Inside Server
Bundle lab
Configure static PAT (port forwarding) on a Cisco IOS edge router so an outside client can reach an inside HTTP service on TCP/8080 using a dedicated public IP that is not the router's interface. Validate using curl from the outside host and NAT show commands on the router.
Learning objectives
- Mark inside and outside interfaces correctly so translations occur only across the router edge
- Implement static PAT to forward TCP/8080 from a dedicated public IP to an inside server IP/port
- Retain working routing before translation with a default route toward the ISP
- Verify static port-forwarding from the outside using curl and confirm translations with IOS show commands
- Differentiate between static PAT for inbound access and PAT/overload used for outbound flows
Troubleshooting focus
- Outside host cannot connect to 203.0.113.3:8080 because ip nat inside/outside roles are reversed on the router
- Static PAT uses the router’s interface IP instead of the dedicated public IP, breaking the test plan
- Public NAT address is not on the connected outside segment, so return traffic never arrives
- Inside server is not listening on 8080 or the process crashed; port-forwarding appears correct but connection resets
- Default route missing on the NAT router; SYNs arrive but the server’s replies cannot reach the outside network
- Port number mismatch (mapped 8080 but testing 80) resulting in timeouts
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.