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.
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
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.
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).
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:
- Outbound (inside → outside): source is rewritten 10.0.0.5 → 200.100.10.5.
- Inbound (outside → inside): destination is rewritten 200.100.10.5 → 10.0.0.5.
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 --- ---
--- 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.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:
- An inside host sends a packet destined for the outside.
- The router checks whether the host is authorised to be translated (an access-list match).
- If authorised and no translation exists yet, the router assigns the host one free address from the pool.
- When the session (or the timeout) ends, the address returns to the pool for someone else.
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
access-list 1 permit 10.0.0.0 0.0.0.255— a standard ACL that matches the inside hosts allowed to use NAT (source address only; wildcard 0.0.0.255 matches the /24). Hosts the ACL does not match are simply never translated.ip nat pool PUBLIC 200.100.10.10 200.100.10.20 netmask 255.255.255.0— a pool named PUBLIC spanning 200.100.10.10 through 200.100.10.20 (11 addresses), with a public netmask. The netmask must reflect the true size of the address block you were given.ip nat inside source list 1 pool PUBLIC— the engine: for inside traffic that matches ACL 1, translate the source into the next free address from pool PUBLIC.
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.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.
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.
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.
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.
Static vs dynamic compared
| Property | Static NAT | Dynamic NAT |
|---|---|---|
| How the mapping is created | Typed by the administrator | Automatically, when matched traffic starts |
| Persistence | Permanent, never expires | Temporary; removed after the session timeout |
| Address ratio | 1:1 (fixed pair) | 1:1 (any free pool address) |
| Inbound reachability | Yes — mapping always exists | No — no translation until an inside host speaks first |
| Requires | Just the ip nat inside source static line | An ACL, a pool, and the list ... pool binding |
| Typical use | Public web/email server reachable from the Internet | Outbound Internet access for a fixed group of inside users |
| Failure mode | None as such; the mapping is always there | Pool exhaustion: extra hosts get no translation and simply fail |
Review
Check what you have learned with these review questions.
Sources & references
- Srisuresh, P. & Egevang, K. RFC 3022: Traditional IP Network Address Translator (Traditional NAT) (2001). rfc-editor.org/rfc/rfc3022.
- Cisco. NAT Configuration Guide, Cisco IOS — “Configuring Inside Source Addresses” and the
ip nat,ip nat pool, and ACL prerequisite commands. cisco.com. - Arkko, J. & Cotton, M. RFC 5737: IPv4 Address Blocks Reserved for Documentation (2010). rfc-editor.org/rfc/rfc5737.
- 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.