Network Address Translation (NAT)
Explore different types of NAT and its role in conserving IPv4 addresses and providing network security.
Network Address Translation (NAT) is a free Linux Networking & TCP/IP for Developers lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Linux Networking & TCP/IP for Developers learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
What is Network Address Translation?
Welcome to the lesson on Network Address Translation (NAT)! NAT is a crucial technique used in computer networking, especially with IPv4.
Think of NAT as a clever translator for network addresses. It allows devices on a private network to communicate with the internet using a single public IP address.
Why NAT is Essential for IPv4
The main reason NAT became so important is the limited supply of IPv4 addresses. There simply aren't enough unique public IPv4 addresses for every device in the world.
- IPv4 Conservation: NAT helps conserve public IPv4 addresses by allowing many private devices to share one.
- Network Isolation: It also adds a layer of security by hiding the internal network structure from the outside world.
Private vs. Public IP Addresses
To understand NAT, you need to know about private and public IP addresses:
- Private IPs: Used within a local network (e.g., your home or office). They are not routable on the internet. Examples:
192.168.1.10,10.0.0.5. - Public IPs: Unique, globally routable addresses used on the internet. Your home router gets one from your Internet Service Provider (ISP).
NAT bridges these two worlds.
How NAT Works: The Core Idea
Imagine your router as a post office. When a letter (data packet) leaves your house (private network) for the outside world (internet), the post office changes the return address to its own (public IP).
When a reply comes back, the post office knows which house (private IP) to send it to. This is the basic idea behind NAT: translating addresses at the network boundary.
Source NAT (SNAT): Outbound Traffic
Source NAT (SNAT) is used for outbound connections, meaning when devices inside your private network want to reach the internet.
When a packet leaves your private network, the router changes the packet's source IP address from a private one to the router's public IP address. This is often called IP Masquerading.
SNAT Example: Accessing the Web
Here's how SNAT works when your laptop browses a website:
- Your laptop (
192.168.1.10) sends a request to a website. - Your router intercepts it, changes the source IP to its public IP (e.g.,
203.0.113.5), and sends it to the internet. - The website replies to
203.0.113.5. - Your router receives the reply and translates the destination IP back to
192.168.1.10, forwarding it to your laptop.
Destination NAT (DNAT): Inbound Traffic
Destination NAT (DNAT), also known as Port Forwarding, is used for inbound connections. It allows external devices to connect to specific services running on a private device.
When a packet arrives from the internet, the router changes the packet's destination IP address from its public IP to a specific private IP and port within the network.
DNAT Example: Hosting a Game Server
If you host a game server on your PC (192.168.1.100) and want friends to connect:
- Your friend connects to your router's public IP (e.g.,
203.0.113.5) on a specific port (e.g.,25565). - Your router has a DNAT rule: any traffic to
203.0.113.5:25565should be forwarded to192.168.1.100:25565. - The router translates the destination and sends the packet to your game server.
- The server's replies are then SNAT'd back out to your friend.
PAT: Port Address Translation
Most home routers use a type of NAT called Port Address Translation (PAT), also known as NAPT or IP Masquerading.
PAT allows multiple devices on a private network to share a single public IP address simultaneously. It does this by using different source port numbers for each outgoing connection to keep track of which internal device gets which incoming reply.
NAT's Security and Limitations
While NAT is great for address conservation and offers a basic security layer by hiding internal IPs, it's not a firewall:
- Security: Hides internal network topology, making direct attacks harder.
- Limitations: Can complicate peer-to-peer applications and some VPNs, as it breaks end-to-end connectivity. IPv6 aims to solve address scarcity without NAT.
Quick Check: Understanding NAT
Which type of NAT is primarily used to allow multiple internal devices to share a single public IP address when accessing the internet, often by modifying port numbers?
Recap: NAT's Role in Networking
We've explored Network Address Translation (NAT) and its vital role in modern networking. You now understand:
- Why NAT is crucial for conserving IPv4 addresses.
- The difference between private and public IP addresses.
- How Source NAT (SNAT) handles outbound traffic.
- How Destination NAT (DNAT) enables inbound access (port forwarding).
- The common use of Port Address Translation (PAT) to share a single public IP.
NAT is a fundamental concept that enables the internet as we know it today!
Frequently asked questions
Is the “Network Address Translation (NAT)” lesson free?
Yes — the full text of “Network Address Translation (NAT)” is free to read here on the web, and the Linux Networking & TCP/IP for Developers course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Linux Networking & TCP/IP for Developers course, upgrade to CoddyKit PRO.
What will I learn in “Network Address Translation (NAT)”?
Explore different types of NAT and its role in conserving IPv4 addresses and providing network security. You practise Linux Networking & TCP/IP for Developers with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Linux Networking & TCP/IP for Developers?
No prior experience is required. Linux Networking & TCP/IP for Developers on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Network Address Translation (NAT)” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Linux Networking & TCP/IP for Developers lesson?
Yes. Every Linux Networking & TCP/IP for Developers lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- IPv6 Addressing & Concepts
- Advanced Routing Protocols (RIP/OSPF)
- Network Address Translation (NAT)
- Subnetting and CIDR in Depth