CloudLabBox
Try the free demo

HCIA-Datacom lab 15 of 22

NAT from Easy IP to NAT server

Connect a private network to the internet through an AR edge router. You start with Easy IP, move to NAPT with a public address pool, give one PC a one-to-one static mapping, and publish an inside server's service on a public address and port with NAT server, reading the NAT session table at every step.

Run this lab

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

In your workspace: Shared, then HCIA-Datacom H12-811 guided labs, then 15 - NAT from Easy IP to NAT server

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
Intermediate
Time
About 60 minutes
Nodes need
4 vCPU, 7,168 MB
Smallest plan
Lite

The scenario

Northwind's office LAN uses private addresses (192.168.1.0/24). The ISP router R2 has no route to them, and never will: private addresses aren't routed on the internet. The ISP has routed Northwind a public block, 192.0.2.0/24, towards the edge router R1. You'll make the office reach the internet, give one workstation a permanent public identity, and publish the Server's management service to the outside world.

ItemAddress
R1 GE0/0/0 (to ISP) / GE0/0/1 (LAN)203.0.113.1/24 / 192.168.1.254/24
PC1 / Server192.168.1.10 / 192.168.1.100
ISP R2 / "website"203.0.113.2 / 198.51.100.1
Public pool for users192.0.2.11 – 192.0.2.14
PC1's own public address192.0.2.10
Published server address192.0.2.20, TCP port 2323 → Server port 23

What you’ll practise

  • Explain why private addresses need translation, and the difference between NAT, NAPT and Easy IP
  • Configure source NAT with an ACL, nat outbound and an address group (with and without no-pat)
  • Configure static NAT and NAT server (destination NAT with port mapping)
  • Verify with display nat outbound, display nat static, display nat server and display nat session

The tasks

  1. Load the starting configuration
  2. See the problem
  3. Easy IP
  4. NAPT with a public pool
  5. One-to-one with no-pat
  6. Static NAT for PC1
  7. Publish the Server's service with NAT server

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 NAT from Easy IP to NAT server4 nodes and 1 network, 4 links. Every link is listed as text below the diagram.R1R2ServerPC1InsideLANGE0/0/1GE0/0/1eth0GE0/0/0GE0/0/0
4 nodes and 1 network, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • R1 GE0/0/1 to InsideLAN (network)
  • Server GE0/0/1 to InsideLAN (network)
  • PC1 eth0 to InsideLAN (network)
  • R1 GE0/0/0 to R2 GE0/0/0
Nodes in NAT from Easy IP to NAT server, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Huawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
R2Huawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
ServerHuawei AR1000V routerhuaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn1 vCPU, 2,048 MB
PC1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 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 HCIA-Datacom H12-811 guided labs.

  3. Open 15 - NAT from Easy IP to NAT server 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 HCIA-Datacom labs

All HCIA-Datacom labs

Related labs in other courses

CloudLabBox is independent of Huawei. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.