CloudLabBox
Try the free demo

Cisco ASA lab 5 of 15

Twice NAT and NAT order: identity NAT, policy PAT and destination NAT

Meet three partner and user requirements that object NAT cannot express, with manual (twice) NAT: identity NAT for one partner, a dedicated PAT address for another, and destination NAT so staff reach the web server by its public address. Then break and fix the NAT order on purpose.

Run this lab

It needs Lite: its 4 nodes are set to 4 vCPU and 3,584 MB in total. That fits the free demo too.

In your workspace: Shared, then Cisco ASA Firewall SCOR 350-701 guided labs, then 05 - Twice NAT and NAT order - identity NAT policy PAT and destination NAT

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Advanced
Time
About 75 minutes
Nodes need
4 vCPU, 3,584 MB
Smallest plan
Lite

The scenario

HQ-FW now runs the NAT from lab 4: interface PAT for the office and the DMZ, and the web site published at 203.0.113.10:80. Three new requests arrive in the same week:

  1. Partner A (192.0.2.10) has a private interconnect over the ISP and allow-lists Kestrel's real office range. Traffic from 10.10.10.0/24 to Partner A must not be translated. (The ISP already routes 10.10.10.0/24 to HQ-FW for this.)
  2. Partner B (192.0.2.20) allow-lists a single address. Office traffic to Partner B must appear from 203.0.113.20; all other internet traffic keeps using the interface address.
  3. Staff browse to the company web site by its public address, 203.0.113.10. Today that fails from inside. Make it work without changing DNS or the server.

What you’ll practise

  • Write manual (twice) NAT rules that match on source and destination
  • Configure identity NAT with no-proxy-arp and route-lookup
  • Configure policy-based dynamic PAT to a dedicated address
  • Translate a destination address so inside users reach a DMZ server by its public IP
  • Explain the three NAT sections and prove the order with show nat detail and packet-tracer

The tasks

  1. Measure the starting point
  2. Identity NAT for Partner A
  3. Dedicated PAT address for Partner B
  4. Reach the web site by its public address
  5. Break the order on purpose

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.

Topology of Twice NAT and NAT order - identity NAT policy PAT and destination NAT4 nodes, 3 links. Every link is listed as text below the diagram.HQ-FWPC1WEBISPGi0/1Gi0/0Gi0/0Gi0/0Gi0/2Gi0/0
4 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • HQ-FW Gi0/0 to PC1 Gi0/0
  • HQ-FW Gi0/1 to ISP Gi0/0
  • HQ-FW Gi0/2 to WEB Gi0/0
Nodes in Twice NAT and NAT order: identity NAT, policy PAT and destination NAT, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
HQ-FWCisco ASAvasav-9.22.1.1-PLR-Licensed1 vCPU, 2,048 MB
PC1Cisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 512 MB
WEBCisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 512 MB
ISPCisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder Cisco ASA Firewall SCOR 350-701 guided labs.

  3. Open 05 - Twice NAT and NAT order - identity NAT policy PAT and destination NAT and 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 Cisco ASA labs

All Cisco ASA 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.