Week 9 · Lesson 8

Static NAT and NAT Pools

Lesson 7 gave you the vocabulary. Now you configure it. This lesson covers the two 1:1 forms of NAT — static NAT, where a translation is typed in by hand and never changes, and dynamic NAT, where a router hands out addresses from a pool to whichever inside hosts asked first. Both are the foundation for the PAT overload configuration of the next lesson.

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

The inside/outside boundary first

Every NAT configuration, whatever its type, begins with the same two interface declarations from Lesson 7:

R1# configure terminal
R1(config)# interface gigabitEthernet 0/0
R1(config-if)# ip address 10.0.0.1 255.255.255.0
R1(config-if)# ip nat inside
R1(config-if)# no shutdown
R1(config-if)# exit
R1(config)# interface gigabitEthernet 0/1
R1(config-if)# ip address 200.100.10.1 255.255.255.0
R1(config-if)# ip nat outside
R1(config-if)# no shutdown
R1(config-if)# end
Definition — inside source translation. Both forms you learn today are inside source translations: the router rewrites the source address of packets leaving the inside network. The CLI family is ip nat inside source .... A related but different family, ip nat outside source ..., translates far-end addresses instead and is beyond the CCNA depth you need.

A natural trap: the LAN in this lesson uses private address 10.0.0.0/24 on the inside, and the outside link uses a public test range 200.100.10.0/24 from the publications RFC 5737 blocks (safe to type in labs and examples). Real networks would use an address range assigned by the ISP on the outside link.

Which command builds which NAT? · select a type

      

Part 2

Static NAT: one fixed mapping

Static NAT creates a permanent, hand-entered 1:1 mapping between an inside local address and an inside global address. Because the mapping never expires, an outside host can always reach the inside host through its public address — which makes static NAT the tool for servers that must be visible on the Internet (a public web server, an email server, a reachable management device).

Note — why static, and where it is used. Dynamic translations are created only when an inside host initiates traffic. A public web server cannot rely on that — entirely outside-initiated traffic arrives with no translation in the table, so nothing would happen. Static NAT guarantees a mapping is always present. That is why the exam associates static NAT with servers reachable from the Internet and dynamic NAT with outbound access for a group of users.

One command, in global configuration mode, ties an inside local address to an inside global address:

R1(config)# ip nat inside source static 10.0.0.5 200.100.10.5

Read it left to right: for traffic originating inside, take local address 10.0.0.5 and present it to the outside as 200.100.10.5. The before/after behaviour:

That single statement gives you both directions automatically, which is exactly what a public server needs. The translation table immediately shows the mapping even before any traffic:

R1# show ip nat translations
Pro  Inside global      Inside local       Outside local      Outside global
---  200.100.10.5       10.0.0.5           ---                 ---
Exam tip — reading a static row. The columns are always Inside global, Inside local, Outside local, Outside global. In a static row the outside columns are empty (no far-end translation) and the protocol column shows --- because this is an address-only mapping. A question that shows this table and asks “which command produced it?” is answered by ip nat inside source static 10.0.0.5 200.100.10.5.
PC 10.0.0.10 Switch S1 Web server R1 NAT g0/0 in · g0/1 out Internet user static map 10.0.0.5 to 200.100.10.5 always in the table, both directions LAN 10.0.0.0/24 (inside) public side 200.100.10.0/24 (outside)
Part 3

Dynamic NAT: a pool of public addresses

Dynamic NAT also translates 1:1, but the mapping is created automatically, temporarily, and from a pool — a list of public addresses the router is allowed to hand out. The process:

  1. An inside host sends a packet destined for the outside.
  2. The router checks whether the host is authorised to be translated (an access-list match).
  3. If authorised and no translation exists yet, the router assigns the host one free address from the pool.
  4. When the session (or the timeout) ends, the address returns to the pool for someone else.
Warning — the pool can run out. A pool has a finite number of addresses. If every address is already assigned and a new host asks for a translation, that host gets none — its traffic is not translated and fails. This is why dynamic NAT is a poor fit for a network with more simultaneous inside users than public addresses, and why PAT (next lesson) exists. The exam will happily give you a pool of 5 addresses and 100 hosts and ask what happens.

Configuring dynamic NAT

Three pieces: an ACL to say who may be translated, a pool to say into what, and a source-list statement to tie them together.

R1(config)# access-list 1 permit 10.0.0.0 0.0.0.255
R1(config)# ip nat pool PUBLIC 200.100.10.10 200.100.10.20 netmask 255.255.255.0
R1(config)# ip nat inside source list 1 pool PUBLIC
Exam tip — which order? You must declare the ACL and pool before the ip nat inside source list line in the running configuration. If a scenario shows NAT not firing, check three things in exactly this order: (1) interfaces marked ip nat inside/outside? (2) does the ACL actually permit the host? (wildcard mistakes here are the single most common lab error) (3) is there a free address in the pool? A permit that names the wrong subnet, or a pool whose range includes only addresses you already used elsewhere, produces a silent no-translation failure.
Pool exhaustion simulator · set the pool and the host count

The ip nat inside source list <ACL> pool <NAME> syntax is also the exact skeleton that becomes PAT in the next lesson — dynamic NAT plus overload swaps the pool behaviour for the address-multiplexing behaviour of PAT.

Part 4

Verifying translations

After a few inside hosts generate traffic, ask the router what it has mapped. The columns you saw in Lesson 7 now fill in with real sessions. Click a row to have it decoded.

show ip nat translations · select a row
ProInside globalInside localOutside localOutside global
---200.100.10.510.0.0.5------
---200.100.10.1110.0.0.10------
---200.100.10.1210.0.0.118.8.8.88.8.8.8

Read the rows: the first is the static mapping from earlier (it persists). The second is a dynamic translation where host 10.0.0.10 took 200.100.10.11 — and because no return traffic has been seen yet, the outside columns are empty. The third shows a session actually in flight toward public server 8.8.8.8: the inside host 10.0.0.11 presents itself to that server as 200.100.10.12, and the outside local/global pair is the server’s own address.

Drill into a single translation. Use show ip nat translations verbose for timestamps, use times, and expiry timers per entry, and show ip nat statistics for pool utilisation and hit counters (you configure that fuller picture in Lesson 9). For an exam, show ip nat translations is the one command you must be able to read without thinking.

You can also trigger a translation deliberately. Once PC-A (10.0.0.10) pings the public server, its ping packet becomes the outbound packet that creates the mapping. Watch the table before and after the ping and you will see dynamic NAT happen. Be careful with debug ip nat on a busy router — it prints a line per translated packet and can flood the console; use it on quiet test equipment and remove it afterwards.

Part 5

Static vs dynamic compared

Which one does this scenario need? · select the requirement

PropertyStatic NATDynamic NAT
How the mapping is createdTyped by the administratorAutomatically, when matched traffic starts
PersistencePermanent, never expiresTemporary; removed after the session timeout
Address ratio1:1 (fixed pair)1:1 (any free pool address)
Inbound reachabilityYes — mapping always existsNo — no translation until an inside host speaks first
RequiresJust the ip nat inside source static lineAn ACL, a pool, and the list ... pool binding
Typical usePublic web/email server reachable from the InternetOutbound Internet access for a fixed group of inside users
Failure modeNone as such; the mapping is always therePool exhaustion: extra hosts get no translation and simply fail
Remember. Both of today’s NAT types are 1:1: they change IP addresses only. The moment a question says “many users · one public address” or mentions ports, you have left these two behind and you are in PAT territory — the entire subject of Lesson 9.
Part 6 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Srisuresh, P. & Egevang, K. RFC 3022: Traditional IP Network Address Translator (Traditional NAT) (2001). rfc-editor.org/rfc/rfc3022.
  2. Cisco. NAT Configuration Guide, Cisco IOS — “Configuring Inside Source Addresses” and the ip nat, ip nat pool, and ACL prerequisite commands. cisco.com.
  3. Arkko, J. & Cotton, M. RFC 5737: IPv4 Address Blocks Reserved for Documentation (2010). rfc-editor.org/rfc/rfc5737.
  4. 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.