NAT with PAT and Verification
This is the NAT the real world runs: PAT (Port Address Translation), the overload configuration that lets an entire branch office share one public address. You will configure PAT in its two common forms, learn to prove it works with show ip nat statistics and show ip nat translations, and walk through the troubleshooting sequence the exam expects when translations do not appear.
PAT: many hosts, one address
PAT is NAT with port multiplexing. It is enabled by adding the overload keyword to an inside-source NAT translation, and it changes the address ratio from 1:1 to many:1. Every session leaving the inside is rewritten so that the source becomes the shared public address plus a unique source port. The router keeps a table mapping each (public IP, port) pair back to the exact private source, so replies know precisely which host to reach.
Why PAT and not the dynamic pool from Lesson 8? Because a busy office has far more simultaneous sessions than public addresses. Dynamic NAT would exhaust its pool the moment the number of active hosts exceeds the pool size. PAT survives because its limiting resource is sessions per address, not hosts — and one address holds plenty.
How the port multiplexing works
Follow two hosts inside the same network both talking to a public web server. The router rewrites their source addresses to the same public IP, and gives each session its own source port to keep them apart. Add sessions one at a time and watch what the router does when two hosts pick the same port.
Configuring PAT with overload
PAT comes in two common configurations. The most frequent — and the one used when your ISP gives you a single dynamic address on the outside interface — is PAT to the interface address:
R1(config)# interface gigabitEthernet 0/0 R1(config-if)# ip address 192.168.1.1 255.255.255.0 R1(config-if)# ip nat inside 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)# exit R1(config)# access-list 1 permit 192.168.1.0 0.0.0.255 R1(config)# ip nat inside source list 1 interface gigabitEthernet 0/1 overload
And the pool variant, used when you hold a small block of public addresses and want them all shared:
R1(config)# ip nat pool PUBLIC 200.100.10.10 200.100.10.12 netmask 255.255.255.0 R1(config)# ip nat inside source list 1 pool PUBLIC overload
ip nat inside source list 1 interface gigabitEthernet 0/1 overload — the public address is whatever the outside interface currently has (ideal for DHCP-assigned ISP addresses). ip nat inside source list 1 pool PUBLIC overload — sessions spread across the named pool instead. Both end in overload; missing that word turns the configuration back into plain dynamic NAT, which is a classic silent failure.A special case worth knowing: IOS will refuse to translate a packet whose destination is the router’s own outside address unless you also add a mapping for it. And if your public block overlaps the inside subnet, IOS may apply ip nat outside source to fix return routing — beyond CCNA depth, but the name of the command is a useful label for the exam.
Reading the translation table
With PAT running and a few sessions active, the table shows protocol detail that static and dynamic rows never had. Select a row to decode it.
The inside global port can differ from the inside local port when two hosts pick the same one — that is the collision rule from Part 2 made visible. A translated row that shows a different port in the inside global column than in the inside local column is the router resolving a clash.
Statistics and clearing
Translations tell you what is mapped; statistics tell you how healthy the mapping engine is.
R1# show ip nat statistics
Total active translations: 4 (0 static, 4 dynamic; 4 extended)
Outside interfaces:
GigabitEthernet0/1
Inside interfaces:
GigabitEthernet0/0
Hits: 22 Misses: 4
Expired translations: 9
Dynamic mappings:
-- Inside Source
[Id: 1] access-list 1 interface GigabitEthernet0/1 refcount 4
interface GigabitEthernet0/1
type dynamic, total addresses 1, allocated 1 (100%), misses 0
R1# clear ip nat translation * R1#
clear ip nat translation * tears down every dynamic translation on the router. Use it after reconfiguring NAT, after changing the outside address, or when a stale entry is sending a session to the wrong host. Static translations survive the clear; only dynamic/PAT entries are removed. Existing sessions will rebuild their mappings at the next packet — so it is a low-risk command, but expect momentarily interrupted sessions.Troubleshooting NAT/PAT
When NAT appears to do nothing, work the checklist top to bottom. Each step is the answer to an exam question on its own. Choose the symptom you are facing.
| Symptom | Most likely cause | Fix / verify |
|---|---|---|
| No translations appear at all | Interfaces never marked ip nat inside / ip nat outside. | show ip nat statistics lists the inside and outside interfaces; re-enter them and re-apply the commands. |
| Only some hosts translate | ACL permits the wrong range or mask. | Check access-list 1; a wildcard of 0.0.255.255 would miss part of 192.168.1.0/24. 0.0.0.255 is the /24 wildcard. |
| Pool-based translation stops partway through the day | Pool exhausted (all addresses allocated). | show ip nat statistics allocated/total 100%; enlarge the pool, or switch to overload. |
| PAT sessions die after reconfigure | Forgot overload, so it is running as plain dynamic NAT. | Re-issue the source list command ending in overload; clear stale entries with clear ip nat translation *. |
| Hosts reach the Internet but cannot reach a local public server | No static mapping for the inbound side, or destination is the router’s own outside address. | Add ip nat inside source static for the server; confirm the intended destination is not the router itself. |
| NAT works but is slow / CPU pegged | Heavy NAT load, or debug ip nat left on a production router. | Remove debugging (undebug all); consider whether PAT session limits are being exhausted. |
| Application fails across NAT | Protocol embeds addresses in the payload (active FTP, some SIP). | Enable the relevant ALG/application inspection for that protocol, or switch to a NAT-friendly mode (FTP passive). |
show ip nat translations tells you whether sessions are being created at all, and show ip nat statistics tells you whether the engine is healthy. If translations exist but connectivity still fails, the problem has moved past NAT — check routing, ACLs, and the host firewall next.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), including the address-mapping and port-mapping sections. rfc-editor.org/rfc/rfc3022.
- Cisco. NAT Configuration Guide, Cisco IOS — “Configuring NAT for IP Address Conservation” (overload) and NAT monitoring commands. cisco.com.
- Cisco. IP Addressing: NAT Configuration Guide,
show ip nat statisticsandclear ip nat translationcommand reference. cisco.com. - Cisco. CCNA (200-301) Exam Topics, Domain 4.0 IP Services (NAT, PAT). cisco.com.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.