Study guide

NAT, Easy IP, and NAT Server

Huawei Certified ICT Associate - Datacom HCIA-Datacom H12-811 V1.0

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About HCIA-Datacom H12-811 V1.0 Study Strategies and Exam Logistics

2 Chapter 1: Network Models and Ethernet Fundamentals

OSI and TCP/IP Models Ethernet Technology and MAC Addressing Data Forwarding and Campus Network Lifecycle

3 Chapter 2: IPv4 Addressing and Transport Protocols

IPv4 Addressing and Subnetting ARP and ICMP TCP and UDP Principles Common Ports and Application Protocols

4 Chapter 3: Huawei VRP Basics and Device Management

VRP CLI Views and Core Commands Configuration Save, Reset, and File System SSH, Telnet, and Console Access Display Commands and Basic Troubleshooting

5 Chapter 4: Ethernet Switching and VLANs

Switch Forwarding and MAC Address Tables VLAN Concepts and Segmentation Access, Trunk, and Hybrid Link Types VLANIF and Inter-VLAN Routing

6 Chapter 5: STP, RSTP/MSTP, and Link Aggregation

STP Concepts and Election RSTP and MSTP Eth-Trunk Static and LACP Stacking Basics for Campus Switches

7 Chapter 6: IP Routing Fundamentals

RIB, FIB, and Forwarding Decisions Static and Default Routes on VRP Route Preference and Longest Match Floating Static Routes and Blackhole Routes

8 Chapter 7: OSPF Fundamentals

OSPF Areas and Router Types Neighbor States and Adjacency LSA Types and LSDB DR/BDR Election and VRP OSPF Configuration

9 Chapter 8: ACLs and AAA

Basic and Advanced ACLs traffic-filter Application and Matching Order AAA with Local, RADIUS, and HWTACACS

10 Chapter 9: DHCP, NAT, and Network Services

DHCP Server, Relay, and Snooping NAT, Easy IP, and NAT Server FTP, TFTP, DNS, NTP, HTTP Basics

11 Chapter 10: WLAN Basics

WLAN Architecture: AC, AP, and Fit Mode CAPWAP Tunnels and Forwarding Modes WPA2, WPA3, and WLAN Security Basics Basic WLAN Configuration Concepts

12 Chapter 11: WAN Basics

WAN Concepts and Encapsulation PPP Authentication: PAP and CHAP PPPoE Basics and Client Configuration

13 Chapter 12: IPv6 Fundamentals

IPv6 Address Types and Format Neighbor Discovery and ICMPv6 Stateful and Stateless DHCPv6 IPv6 Static Routes on VRP

14 Chapter 13: SDN and NFV Fundamentals

SDN and NFV Fundamentals

15 Chapter 14: Network Management and O&M

Network Management, O&M, and Automation Basics

NAT, Easy IP, and NAT Server

Key Takeaways Explain This Topic AI

NAT translates private (RFC 1918) addresses to public addresses so many internal hosts can share scarce public IPv4 space and hide internal topology.

Source NAT rewrites the source address of outbound traffic; Easy IP is a common Huawei form that uses the outbound interface’s public IP as the translated address.

NAT Server (static destination mapping) publishes an internal server so unsolicited inbound traffic from the outside can reach a fixed inside host and port.

Inside and outside interface roles define translation direction: Easy IP primarily serves inside-to-outside sessions; NAT Server enables outside-to-inside access to specific services.

Exam traps mix Easy IP (outbound sharing) with NAT Server (inbound static publish)—pick the feature that matches traffic direction and whether a fixed public mapping is required.

Last updated: July 2026

NAT, Easy IP, and NAT Server

Quick Answer: NAT rewrites IP addresses at the edge so private hosts can use public connectivity. Easy IP is Huawei source NAT that uses the outbound interface address as the public source—ideal for many users sharing one WAN IP. NAT Server creates a static mapping so the Internet can initiate sessions to an internal server. Direction matters: Easy IP is for outbound ; NAT Server is for inbound publish .

IPv4 public addresses are scarce. Campus and branch networks almost always use private ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) on the inside and a small set of public addresses on the WAN. Network Address Translation (NAT) on the Huawei edge router or firewall-capable device rewrites packets so return traffic finds the correct session. HCIA-Datacom tests whether you choose the right NAT style for a requirement and whether you understand which address field changes in each direction.

Why NAT exists

  • Driver Effect
  • IPv4 address shortage Many inside hosts share few public IPs
  • Topology hiding Outside hosts see the public edge address, not every PC

Overlapping private designs Branches with identical RFC 1918 space can still reach shared services with careful NAT (advanced designs; know the problem exists)

Policy control Only traffic that matches a NAT interest ACL (or equivalent) is translated

NAT is not a full security system by itself, but it does block unsolicited inbound connections to unmapped private hosts—one reason NAT Server (or port mapping) must be added explicitly when you host a service for the Internet.

Private versus public addressing in exam language

Private addresses are not globally routable on the public Internet. When a PC at 192.168.1.10 sends to 8.8.8.8, the packet must leave the site with a public source the ISP will route and that the remote host can reply to. NAT performs that rewrite and maintains a translation table so replies can be de-translated back to 192.168.1.10.

Without NAT (or without public addressing on every host), inside systems cannot complete Internet sessions. With NAT but no inbound mapping , an outside client cannot open a new session to a random inside PC—by design.

Source NAT concepts

Source NAT changes the source IP (and often source port) of packets leaving the inside network:

Inside host sends packet: src = private IP, dst = Internet IP.

Edge device matches a NAT policy / ACL of interest traffic.

Device replaces src with a public address (pool or interface IP) and records the mapping.

Reply returns to the public address; device restores the original private source as destination for the inside hop.

Port rewriting (sometimes called PAT or NAPT in multi-vendor texts) lets thousands of inside sessions share one public IP by differentiating source ports . HCIA language on Huawei gear emphasizes Easy IP and NAT address groups rather than Cisco PAT branding, but the idea is the same: many-to-one source translation.

Easy IP on Huawei

Easy IP is the associate-level workhorse for branch Internet access:

Characteristic Easy IP behavior

Public address used The IP address of the outbound (outside) interface —often the dialer or GE WAN address learned or configured on that link

  • Direction Inside → outside session initiation by internal users
  • Address planning No separate public NAT pool required for basic sharing
  • Typical match ACL defining which inside sources (and sometimes destinations) may be translated
  • Operational win Simple: when the WAN IP changes (PPPoE, DHCP WAN), translation follows the interface address

Conceptual configuration pattern (understand the pieces; exact CLI varies by VRP version):

Define an ACL that permits inside subnets that should access the Internet (interest traffic).

On the NAT device, associate that ACL with Easy IP outbound on the WAN interface.

Ensure routing sends Internet-bound traffic out that interface.

Optionally combine with security zones or firewall policies on platforms that separate trust domains.

Exam trap: Configuring Easy IP but forgetting the ACL match—or writing a deny-heavy ACL—so no traffic is translated. Another trap: applying Easy IP on the wrong interface (inside LAN instead of outside WAN), so translation never sees outbound Internet flows correctly.

NAT address groups (pool-based source NAT)

When one interface address is not enough—or policy requires a dedicated public range—Huawei uses a NAT address group (pool) of public IPs for source translation. Compare:

  • Mode Public addresses Best fit
  • Easy IP Single interface IP Small branch, simple shared Internet

NAT address group One or more configured public IPs Need multiple publics, or interface IP must stay separate from NAT

Both are still source NAT for outbound sessions. The difference is where the public source addresses come from , not the inside/outside direction model.

NAT Server (static mapping for inbound services)

NAT Server publishes an internal server to the outside world. You map a public IP + protocol/port (or a public IP alone for full host mapping) to an inside IP + port . Unsolicited traffic that arrives on the outside matching that mapping is translated destination-wise toward the private server; return traffic is source-translated back.

  • Requirement Feature choice
  • Users on LAN need Internet; no inbound services Easy IP (or source NAT pool)
  • Internet users must reach internal web/mail/VPN concentrator NAT Server (plus permit policies)
  • Both browsing and a published server Easy IP and NAT Server together

Example story: Public 203.0.113.5 TCP 443 maps to inside 10.1.1.20 TCP 443. Outside clients connect to 203.0.113.5:443; the router rewrites destination to 10.1.1.20:443. Inside server replies; the router ensures the outside client still sees 203.0.113.5 as the peer.

Exam trap: Using Easy IP alone and expecting inbound server access—Easy IP does not create a stable public destination mapping for unsolicited inbound sessions. Conversely, NAT Server alone does not give every PC shared outbound Internet access unless source NAT is also present.

Inside and outside interfaces (HCIA-level model)

Associate-level questions use a simple edge model:

  • Side Typical interfaces Address types
  • Inside LAN, VLANIF user networks Private RFC 1918
  • Outside WAN, Internet-facing GE, dialer Public or provider-facing

Translation direction follows session flow:

Outbound user traffic: source private → source public (Easy IP / source NAT) on the path toward outside.

Inbound published service: destination public → destination private (NAT Server) when traffic arrives from outside.

Some platforms also speak of “inside local / inside global / outside local / outside global” address roles. For HCIA, keep the mental model tighter: local private host address , global public address seen on the Internet , and which feature maps them for each direction.

ACL interest traffic and order of operations

NAT often consults an ACL to decide which packets are eligible:

Permit lines define inside sources (and optionally destinations) that receive source NAT.

Packets not matched may be routed without translation—usually failing on the Internet if sources are private.

Overly broad permits can translate traffic you meant to keep private on a partner link; overly narrow permits break browsing for some subnets.

Think of ACL + NAT as a pair: routing decides where the packet goes; NAT decides how addresses look when they leave. Both must be correct.

Common failure modes

Symptom Likely NAT-related cause

Inside PCs cannot reach Internet; ping to WAN IP works from router Missing Easy IP/source NAT or ACL does not match PC subnets

One subnet works, another does not ACL interest traffic omits the second subnet

Web server unreachable from Internet; LAN users browse fine Easy IP present but NAT Server missing or wrong public IP/port

Server reachable on wrong port NAT Server protocol/port mapping mismatch

Intermittent access after WAN IP change Static NAT used interface-old IP; Easy IP would have followed interface

  • Asymmetric paths Return traffic bypasses the NAT device so de-translation never happens
  • Worked mini-scenarios

Scenario A — Branch office: 50 PCs on 192.168.10.0/24; single PPPoE WAN IP. Solution: ACL permit 192.168.10.0/24, Easy IP on dialer/WAN. No NAT Server.

Scenario B — Publish intranet HTTPS: Same branch plus server 192.168.10.50 needing public 203.0.113.10:443. Solution: keep Easy IP for users; add NAT Server mapping 203.0.113.10:443 → 192.168.10.50:443; open security policy if the platform filters.

Scenario C — Wrong tool: Stem says “allow Internet users to open the internal FTP server” and options include only Easy IP— Easy IP is insufficient ; choose NAT Server (or equivalent static destination NAT).

Practice goals before the next section

Label private vs public addresses on an edge diagram and mark inside/outside.

Choose Easy IP vs NAT Server for five one-sentence requirements.

Explain why many-to-one source NAT needs port differentiation in the translation table.

Predict the failure if NAT Server maps the wrong inside IP or TCP port.

With addressing and translation in place, day-2 operations still need file transfer, name resolution, time sync, and web access—covered next as core network services.