Palo Alto NGFW lab 7 of 30
NAT: source, destination, port translation and U-turn
Build every NAT type an exam expects: dynamic IP and port for users, a bidirectional static NAT for a server's own outbound traffic, destination NAT with port translation to publish the intranet, and U-turn access for inside users. Learn the pre-NAT address, post-NAT zone rule for security policy and prove each translation in the session table.
Run this lab
It needs Lite: its 4 nodes are set to 5 vCPU and 7,680 MB in total. That fits the free demo too.
In your workspace: Shared, then Palo Alto NGFW PAN-OS 11 guided labs, then 07 - NAT - source destination port translation and U-turn
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 5 vCPU, 7,680 MB
- Smallest plan
- Lite
The scenario
The security rules allow depot users out to the internet, yet nothing works: the ISP routes only Calder's public block 203.0.113.0/24, and the test sites have no route back to 10.1.1.0/24. Calder needs:
| Need | NAT type | Public address |
|---|---|---|
| Users browse the internet | Source NAT, dynamic IP and port (PAT) | 203.0.113.2 (the interface) |
| web01 fetches its own updates from a fixed address the vendor can allow-list | Static source NAT, bidirectional | 203.0.113.10 |
Customers reach the intranet page from the internet at http://203.0.113.20:8080 | Destination NAT with port translation | 203.0.113.20:8080 to web01:80 |
| Depot staff use the same public URL from inside | U-turn | 203.0.113.20:8080 |
The Internet node is your customer: on its console, curl --interface 198.51.100.10 ... makes requests from a real internet address. Logins: FW1 admin / Lab-Access-1.
Before you start. Start all the nodes. The firewall takes 6-8 minutes to boot and comes up with this lab's starting configuration already loaded. Wait until the FW1 console shows
FW1 login:, then log in asadmin/Lab-Access-1. Until the management plane is ready it answers Login incorrect, even with the right password. The Linux hosts are ready within seconds.
What you’ll practise
- Configure source NAT with dynamic IP and port on the egress interface
- Configure a static bidirectional source NAT for a server
- Publish a DMZ server with destination NAT and port translation
- Write the matching security rule with the pre-NAT address and the post-NAT zone
- Make the public address work from inside (U-turn) and verify with test nat-policy-match and the session table
The tasks
- Source NAT for depot users
- Static bidirectional NAT for web01's own traffic
- Publish the intranet with destination NAT and port translation
- U-turn: the public URL from inside
- Test NAT without traffic
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
- FW1
mgmtto Inside (network) - FW1
ethernet1/1to Outside (network) - FW1
ethernet1/2to Inside (network) - FW1
ethernet1/3to DMZ (network) - Client-PC
eth0to Inside (network) - web01
eth0to DMZ (network) - Internet
eth0to Outside (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| FW1 | Palo Alto Networks VM-Series (PAN-OS) | paloalto-11.2.5 | 2 vCPU, 5,632 MB |
| Client-PC | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
| web01 | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 512 MB |
| Internet | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
Palo Alto NGFW PAN-OS 11 guided labs.Open
07 - NAT - source destination port translation and U-turnand 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 Palo Alto NGFW labs
Related labs in other courses
CloudLabBox is independent of Palo Alto Networks and Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.