NAT: Connecting Private Networks to the Internet

1. The Big Idea: NAT as a Receptionist

At its core, NAT is a process run by your router that rewrites the source and destination IP addresses in packets as they cross the boundary between your private network and the public internet.

A great way to think about this is to use an analogy. Imagine a large office building where each employee has a unique internal phone extension (like a private IP), but the entire company has only one public phone number (like a public IP).

As the article explains, the NAT router acts like the company receptionist. When an internal device wants to talk to the internet, it tells the router. The router makes the connection on its behalf using the single public IP address and keeps a record of who made the request. When a reply comes back, the router checks its records and forwards the response to the correct internal device. To the outside world, it looks like the router itself is the one communicating.

This diagram shows this exact scenario:

2. The Real Magic: Port Address Translation (PAT)

The receptionist analogy is great, but it raises a technical question: if multiple devices (your phone and laptop) are browsing different websites at the same time, how does the router know which returning packet belongs to which device? They all use the same public IP address.

The answer is the most common form of NAT, called NAT Overloading or Port Address Translation (PAT).

PAT extends the translation process by not only changing the IP address but also the source port number. Here’s how it works step-by-step:

1. Outbound Packet: Your laptop (private IP 192.168.1.100) sends a packet to a web server. The packet has a source IP:port pair, for example, 192.168.1.100:54321.
2. Translation: The NAT router receives this packet. It replaces the private source IP and port with its own public IP and a unique port number, for example, 88.77.66.55:12345.
3. NAT Table Entry: The router records this translation in a special table called the NAT translation table:
   Internal (192.168.1.100:54321) <---> External (88.77.66.55:12345)
4. Inbound Packet: The web server sends its reply to the public address 88.77.66.55:12345.
5. Reverse Translation: The router receives the reply. It looks up the destination port 12345 in its translation table, finds the corresponding internal address 192.168.1.100:54321, rewrites the destination IP and port, and forwards the packet to your laptop.

If your phone starts a new connection, the router will do the same thing but assign a different external port (e.g., 12346), allowing it to handle both connections simultaneously.

This video provides a great animated explanation of PAT.

For a detailed textual breakdown of this process, you can refer back to the HowStuffWorks article.

3. Seeing NAT in Action

Theory is great, but seeing is believing. The following video demonstrates NAT in practice using Wireshark. The host initiates an SSH connection from a computer on a private network to a server on the public internet. He captures packets on both the client-side (inside the private network) and the server-side (on the public internet) to show you exactly how the source IP address is translated.

While watching, you'll hear the terms inside local and inside global. This is standard terminology for describing the translation:

• Inside Local: The private IP of a device inside your network.
• Inside Global: The public IP that same device appears as to the global internet (i.e., your router's public IP).

This demonstration perfectly illustrates your goal of connecting "book knowledge" to real-life internet functionality. You can see the IP address in the packet header being rewritten, just as we discussed.

4. Other Flavors of NAT

While PAT/Overloading is what your home network uses, it's helpful to be aware of two other, less common types of NAT.

• Static NAT: Creates a permanent, one-to-one mapping between a single private IP and a single public IP. This is used when you need a device on your private network (like a web server) to be accessible from the internet. The router will always forward traffic coming to that specific public IP to the designated private IP.
• Dynamic NAT: A router has a pool of public IP addresses. When an internal device wants to connect to the internet, the router picks an available public IP from the pool and assigns it for the duration of the session. It's still a one-to-one mapping, but it's temporary rather than permanent.

The CertBros video you watched earlier also gives a quick, clear explanation of these two types.

Conclusion

You've now uncovered the "magic" that connects the private and public internet. NAT, and specifically PAT, is a clever and essential technology that has massively extended the life of the IPv4 protocol.

Key Takeaways:

• NAT is the process of a router rewriting IP addresses in packets that cross between a private network and the public internet.
• PAT (NAT Overloading) is the most common form. It allows many devices with private IPs to share a single public IP by using unique port numbers to track each connection.
• A router running NAT maintains a translation table to map internal IP:port pairs to external IP:port pairs, ensuring reply packets get to the right device.
• NAT provides a basic security benefit by hiding the internal IP structure from the public internet.

Preview of the Next Lesson:
We've now covered the fundamentals of addressing: binary-to-decimal, subnetting, public vs. private IPs, and NAT. The next module will introduce you to a few core "helper" protocols that work alongside IP to make a network function smoothly. We'll start by exploring ARP, the protocol that answers the question: "I know the IP address I want to talk to on my local network, but how do I physically send the data to that specific machine?" We'll also cover ping (ICMP) and DHCP.