Everyday Guidebooks
Cover of CCNA Course for Beginners

Cybersecurity & IT

CCNA Course for Beginners: Network Address Translation

An Unofficial Guide to Static NAT, Dynamic NAT, PAT, and Translation Troubleshooting

by Todd Michael

Available now

When a packet crosses a network boundary, which address changes—and how can you tell whether the translation worked? This focused guide makes network address translation understandable one packet at a time.

Designed as a companion to a ccna course for beginners, it explains static NAT, dynamic NAT, and port address translation through plain-English walkthroughs, text-based configurations, and original exercises. Follow outbound and return traffic, connect configuration lines to translation-table entries, and learn to recognize mistakes such as incorrect inside and outside assignments, mismatched access lists, exhausted pools, and missing return routes.

Each chapter builds on a consistent set of example networks, with practice questions and worked explanations that help you check your reasoning. You will finish with a repeatable method for investigating NAT problems and a clearer understanding of what translation can—and cannot—do.

This independent resource focuses on NAT; it is not a complete CCNA exam guide and is not affiliated with or endorsed by Cisco.

Contents
  1. 1. Why Networks Translate Addresses
  2. 2. Following a Packet Across the Boundary
  3. 3. Static NAT: One Address to One Address
  4. 4. Configuring and Checking Static NAT
  5. 5. Dynamic NAT: Selecting from a Pool
  6. 6. Configuring and Checking Dynamic NAT
  7. 7. PAT: Many Hosts, One Public Address
  8. 8. Configuring and Checking PAT
  9. 9. Reading Translation Tables and Statistics
  10. 10. Access Lists and NAT Eligibility
  11. 11. Routing and Return-Path Dependencies
  12. 12. A Repeatable NAT Troubleshooting Method
  13. 13. Mixed-Scenario Practice
  14. 14. Final Review and Diagnostic Challenge
  15. Other Books by Todd Michael

Read a sample: 1. Why Networks Translate Addresses

A laptop on a small office network sends a request to a website. The laptop’s IPv4 address is 192.168.10.10, an address chosen for use inside the office. The website, however, cannot send a reply across the public internet to that private address. Somewhere between the laptop and the website, the packet needs an address that makes sense beyond the office network.

Network Address Translation, or NAT, provides a way to change address information as traffic crosses a network boundary. A router can replace the laptop’s private source address with an address used on the outside network, remember the relationship, and apply the corresponding translation to returning traffic.

That description is useful, but it leaves room for several important questions. What exactly counts as “inside”? Which address does the website see? How can multiple devices use one outside address? And if a translation exists, does that prove the destination is reachable?

This chapter establishes the vocabulary and the example network you will use throughout the book. The goal is not to memorize configuration commands yet. It is to understand the problem NAT addresses and to separate translation from the other jobs a network must perform.

An IPv4 address identifies an interface within an addressing scheme. For devices to communicate across interconnected networks, routers need addresses that can be used to make forwarding decisions. Not every IPv4 address, however, is intended to be routed across the public internet.

Three IPv4 blocks are reserved for private addressing:

- 10.0.0.0/8 - 172.16.0.0/12 - 192.168.0.0/16

An organization can use addresses from these blocks within its own network without requiring those addresses to be unique across the entire internet. Another organization can independently use the same private addresses.

For example, two unrelated offices might each have a laptop at 192.168.10.10. That duplication is not inherently a problem while the addresses are used within separate private networks. It does mean that the address alone cannot identify one of those laptops uniquely across the public internet.

Public IPv4 addresses, by contrast, are used for communication on public networks and must be globally unique when publicly routed. Organizations obtain the right to use public addresses through appropriate allocation or assignment arrangements, often involving a service provider. Not every address outside the three private blocks is automatically suitable for ordinary public use; IPv4 also includes other special-purpose ranges.

The examples in this book use the documentation ranges 192.0.2.0/24 and 198.51.100.0/24 to represent outside addresses. These ranges are reserved for examples, not for real public internet connectivity. Treat them as stand-ins for usable public addresses in a lab or a diagram.

IPv4 has a finite address space. If every device on every private network needed its own globally unique public IPv4 address, the demand for public addresses would be much greater. NAT allows an organization to use private addresses internally while presenting one or more different addresses externally.

The amount of address conservation depends on the kind of translation used. A one-to-one mapping associates one inside address with one outside-facing address. That mapping is useful, but it does not let several inside devices simultaneously share that same outside address through a simple address-only mapping.

Port Address Translation, usually called PAT, extends the idea. For supported traffic such as TCP and UDP, PAT can distinguish concurrent conversations using port numbers as well as addresses. Many inside devices can therefore share a single outside IPv4 address for outbound communication.

NAT can also help an organization use one addressing scheme internally and another at a boundary. This book focuses on the common case of translating private inside IPv4 addresses to outside-facing addresses. NAT can be used in other arrangements, but learning this basic case first gives you a reliable foundation.

The important point is that translation changes information in a packet. It does not make the original private address globally routable.

Consider a small office connected through a router to an outside network:

text Inside network Outside network

PC-A Web server 192.168.10.10 198.51.100.80 | | | | +---- 192.168.10.1 R1 192.0.2.2 ---- Outside network | NAT boundary router

Inside subnet: 192.168.10.0/24 R1 inside interface: 192.168.10.1 R1 outside interface: 192.0.2.2 Additional example translation addresses: 192.0.2.10–192.0.2.20

R1 connects the office’s inside subnet to the outside network. PC-A uses 192.168.10.1 as its default gateway. The web server is an outside destination at 198.51.100.80.

The diagram leaves out intermediate outside routers. Assume that appropriate routes exist when an example asks you to focus on translation. Later, you will examine what happens when that assumption is wrong.

The address 192.0.2.2 belongs to R1’s outside interface. Depending on the NAT configuration, R1 may use that interface address for PAT. The additional addresses 192.0.2.10 through 192.0.2.20 are available in the example addressing plan for other translation scenarios. Their presence in the plan does not mean R1 automatically translates traffic using them. Translation must be configured, and the surrounding network must be able to deliver return traffic for any translated address to R1.

Throughout the book, “inside” and “outside” describe roles relative to the NAT boundary. Inside is the side containing the addresses being translated in these examples; outside is the other side. These labels do not mean that one interface is physically indoors or that the outside network must always be the public internet.

Suppose PC-A sends a packet to the web server. Before translation, its IPv4 header contains:

text Source: 192.168.10.10 Destination: 198.51.100.80

For this example, suppose R1 has an…

More Cybersecurity & IT

Cover of The White Hat Bible, Volume 1The White Hat Bible, Volume 1Available nowCover of The White Hat Bible, Volume 2The White Hat Bible, Volume 2Available nowCover of The White Hat Bible, Volume 3The White Hat Bible, Volume 3Available nowCover of The White Hat Bible, Volume 4The White Hat Bible, Volume 4Available nowThe White Hat Bible, Volume 5Available nowCover of The White Hat Pocket GuideThe White Hat Pocket GuideAvailable now

About Todd Michael

Todd Michael is an American author and the founder of ToddMichael.tv. He writes practical, plain-English books on money, health, preparedness, technology, games, humor and more.

About the author Todd Michael · Todd Michael’s author site

Part of the ToddMichael.tv network.