CCNP ENCOR lab 18 of 36
NAT and PAT at the internet edge
Publish a web server with static NAT and a port forward, give staff addresses from a public pool and put guests behind PAT, then read and clear the translation table like an operator.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 3,584 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENCOR 350-401 guided labs, then 18 - NAT and PAT at the internet edge
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 5 vCPU, 3,584 MB
- Smallest plan
- Lite
The scenario
Fernhill Freight's Leeds edge router (R1) has three inside networks and one public block, 192.0.2.0/24, which the provider routes to R1's outside address. Right now nothing inside can reach the internet. The requirements:
- The track-and-trace web server SRV1 must be reachable from the internet as 192.0.2.10 (all traffic) and also as 192.0.2.11 port 8080, for a partner whose firewall only allows outbound port 8080.
- Staff (10.10.10.0/24) get addresses from the pool 192.0.2.32–192.0.2.47, one public address per user, so partner sites can whitelist them.
- Guests (10.10.50.0/24) all share R1's outside address with PAT.
| Device | Interface | Address | Role |
|---|---|---|---|
| R1 | Gi0/0 | 203.0.113.2/30 | outside, to ISP 203.0.113.1 |
| R1 | Gi0/1 / Gi0/2 / Gi0/3 | 10.10.10.1/24 / 10.10.50.1/24 / 10.10.30.1/24 | inside: staff / guests / servers |
| SRV1 | Gi0/0 | 10.10.30.10/24, gateway 10.10.30.1 | web server (ip http server) |
| PC1 / PC2 | eth0 | 10.10.10.10/24 / 10.10.50.10/24 | staff / guest |
| ISP | Lo0 | 198.51.100.1/24 | an internet host |
R1 has a default route to the ISP. Don't change the ISP router.
Topology: PC1, PC2 and SRV1 connect to R1; R1 Gi0/0 — ISP.
What you’ll practise
- Use the four NAT address terms correctly and mark inside and outside interfaces
- Configure static NAT and static PAT (port forwarding) for an internal server
- Configure dynamic NAT from a pool and PAT overload on the outside interface
- Verify, debug and clear translations, and explain NAT's order of operations
The tasks
- Mark the boundary
- Publish the web server with static NAT
- Add the partner port forward
- Give staff addresses from a pool
- Put guests behind PAT
- Operate NAT
The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.
Topology and devices
The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.
Every link, as text
- R1
Gi0/0to ISPGi0/0 - R1
Gi0/1to PC1eth0 - R1
Gi0/2to PC2eth0 - R1
Gi0/3to SRV1Gi0/0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| ISP | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| SRV1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| PC1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PC2 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CCNP ENCOR 350-401 guided labs.Open
18 - NAT and PAT at the internet edgeand start its nodes, then open Lab Tasks for the scenario and the steps.
The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.
More CCNP ENCOR labs
Related labs in other courses
CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.