Week 9 · Lesson 7

NAT Concepts

Millions of private addresses live behind a handful of public ones. The mechanism that makes that possible is Network Address Translation (NAT) — a router rewriting IP addresses as packets cross its boundaries. This lesson builds the vocabulary you need before touching a single command: public versus private addressing, why NAT exists, and the four-way inside/outside, local/global terminology that the exam loves.

CCNA 200-301 Domain 4.0 IP Services Verified 2026-10-11
Part 1

Public vs private addressing

Every interface on the Internet needs an address that is globally unique so packets can be routed to exactly one destination. Such an address — assigned by an ISP or an address registry, and advertised in the public routing tables — is a public (or global) address. Public addresses are a scarce resource: IPv4 address space is only 32 bits, and the last blocks were allocated from the registries years ago.

The response to scarcity was private addressing. RFC 1918 set aside three ranges that are not routed on the public Internet and may be reused freely inside any organisation:

RangePrefixHosts per network (max)Typical use
10.0.0.0 – 10.255.255.255/816,777,214Large enterprise networks
172.16.0.0 – 172.31.255.255/121,048,574Mid-size networks
192.168.0.0 – 192.168.255.255/1665,534Small office / home
Exam tip. The three RFC 1918 ranges are tested constantly: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16. Watch the trap answers: 172.31.x.x is private (it sits inside /12), but 172.32.x.x is not. A private address can never be a public destination on the Internet; anything addressed with those ranges must be translated before it leaves the enterprise edge, which is exactly what NAT does.

Remember the other reserved blocks that are often named in the same breath: APIPA / link-local 169.254.0.0/16 (self-assigned when no DHCP lease can be reached), CGN (carrier-grade NAT) 100.64.0.0/10 used by ISPs for their own subscribers, and the documentation addresses 192.0.2.0/24, 198.51.100.0/24, and 203.0.113.0/24 (RFC 5737) — used in textbooks and examples precisely so they are never confused with real public addresses.

Address range checker · type an IPv4 address

Part 2

Why NAT exists

NAT (Network Address Translation) is the process of rewriting the IP address (and often the TCP/UDP port) in a packet header as it passes through a router. The classic driver is simple: an organisation may hold thousands of hosts addressed from RFC 1918 space, but only one or a few public addresses. NAT maps the private addresses to the public ones at the edge.

Definition — NAT. NAT is a router function that translates IP addresses in packet headers as they cross from one side of a network boundary to the other, typically between an internal private network and a public network. It hides the internal topology and allows many private hosts to share fewer public addresses.

Two forces made NAT essential. First, address conservation: the number of connected devices far exceeds the IPv4 space (the original design assumption of a unique address per device is long gone). Second, renumbering avoidance: an organisation can keep its internal numbering stable (even overlapping another company’s, such as two businesses that merge) and let the edge router bridge to the public world.

NAT also delivers a side benefit that is really a security property: internal addresses are not visible from outside, so external hosts cannot directly initiate connections into the internal network unless an explicit translation exists. Do not call NAT a firewall — it is not a security device — but the exam expects you to know the masking effect.

Part 3

The four addresses: inside/outside, local/global

This is the single most misunderstood part of NAT and a favourite theme of the CCNA exam. NAT uses two physical views (inside versus outside) and two visibility views (local versus global) — giving exactly four terms. Keep the definitions attached to the router’s point of view:

Which term applies? · select the situation

A naming trick that works. Read the two words independently. Inside/outside tells you whose point of view and which side of the router the owner of the address lives on. Local/global tells you how that address appears — local = private/internal view, global = public/external view. So “inside global” literally means: a host on the inside, wearing its public face for the outside world. Systematically decode every term this way and the exam questions stop being guesswork.

In the lab and in show ip nat translations, the table always lists four columns in the order Inside global, Inside local, Outside local, Outside global. Practise reading one row now: --- 200.100.10.5 10.0.0.5 --- --- means inside host 10.0.0.5 is presented to the outside as 200.100.10.5. The far end was not translated, so the outside columns are empty.

PC-A on LAN Inside local 10.0.0.5 NAT router g0/0 = inside g0/1 = outside Web server 8.8.8.8 private source rewritten to inside global 200.100.10.5 reply returns to 200.100.10.5, translated back to 10.0.0.5
Part 4

Inside and outside interfaces

Before NAT can decide anything, it must know which interfaces are inside and which are outside. Every packet is then examined for translations in both directions. In IOS you declare this per interface:

R1(config)# interface gigabitEthernet 0/0
R1(config-if)# ip nat inside
R1(config-if)# exit
R1(config)# interface gigabitEthernet 0/1
R1(config-if)# ip nat outside

Inside hosts receive private addresses via DHCP or static configuration, and outside hosts are anything reachable beyond the edge interface — typically the ISP link. A common exam scenario gives you exactly this topology: LAN (inside) → NAT router → public Internet/SERVER (outside). Notice that ip nat inside and ip nat outside do not create any translation by themselves; they only mark which side is which so that the actual ip nat inside source ... statements (Lessons 8 and 9) know what to translate.

Part 5

Static vs dynamic vs PAT

Three ways to run NAT answer three different questions. The exam expects you to distinguish them on two axes: is the mapping fixed or temporary? and how many public addresses do you need?

TypeMapping1:1 or many:1?Public addresses neededTypical use
Static NATManually configured, never expires; the same inside local always maps to the same inside global.1:1One public address per hostA public web/email server that must be reachable from the Internet.
Dynamic NATAutomatic, temporary; an inside host grabs any free address from a pool of public addresses.1:1 while it livesOne public address per concurrent hostA group of hosts needing outbound access; the pool must be big enough.
PAT (overload)Automatic, temporary; many inside hosts share one public address, distinguished by unique source port numbers.many:1One (or a few) public address(es)Almost every home and small-office router on the planet.
Pick the NAT type · select the requirement

Definition — PAT. Port Address Translation (PAT) — enabled with the overload keyword — is NAT with multiplexing. Because TCP and UDP sessions can be told apart by their source port number, thousands of private hosts can share a single public address at once. The router tracks which private host owns which (public IP + port) combination.

The key mental model: static and dynamic NAT are both 1:1 (they change only the IP address), whereas PAT is many:1 (it changes both address and port). A pool that is too small, or a static setup with too few addresses, means hosts simply cannot get a translation when the pool is exhausted — a classic dynamic-NAT failure mode that PAT avoids.

Part 6

Benefits and limitations of NAT

NAT conserves public IPv4 address space and hides the internal numbering — but it is not free. Pick a side to see the arguments.

The score sheet · select a side

Exam framing of the pros and cons. You will meet questions like “Which is a benefit of NAT?” and “Which is a limitation?”. Exam-accepted benefits include address conservation and hiding the internal network. Exam-accepted limitations include added delay, stateful dependency, and breaking protocols that carry addresses in the payload. Saying NAT “encrypts traffic” or “provides strong security” is always wrong — NAT changes addresses, it does not authenticate, encrypt, or filter on policy.

NAT also interacts directly with other IP Services skills from this week: NAT traversal matters for FTP (recall passive mode from Lesson 6, which exists precisely because active mode dies behind NAT), and the time synchronisation you configure in Lesson 10 must reference reachable addresses — which, inside a NATed network, means addressing the translation correctly.

Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Rekhter, Y. et al. RFC 1918: Address Allocation for Private Internets (1996). rfc-editor.org/rfc/rfc1918.
  2. Arkko, J. & Cotton, M. RFC 5737: IPv4 Address Blocks Reserved for Documentation (2010). rfc-editor.org/rfc/rfc5737.
  3. Srisuresh, P. & Egevang, K. RFC 3022: Traditional IP Network Address Translator (Traditional NAT) (2001). rfc-editor.org/rfc/rfc3022.
  4. IANA. Special-Purpose IP Address Registries. iana.org.
  5. Cisco. CCNA (200-301) Exam Topics, Domain 4.0 IP Services (NAT). cisco.com.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.