Traducción de direcciones de red (NAT)
Explore los distintos tipos de NAT y su función en la conservación de direcciones IPv4 y la seguridad de la red.
Traducción de direcciones de red (NAT) es una lección gratuita de Linux Networking & TCP/IP for Developers en CoddyKit. Esta es la lección 3 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de Linux Networking & TCP/IP for Developers, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de Linux Networking & TCP/IP for Developers incluye 4 lecciones en total.
Partes de esta lección aún no han sido traducidas y se muestran en inglés.
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!
Aprende Linux Networking & TCP/IP for Developers con un tutor de IA — gratis
Escribe y ejecuta código real en tu navegador, obtén ayuda instantánea de un tutor de IA disponible 24/7 y continúa donde lo dejaste en la web o en la aplicación.
- Cursos
- 12
- Lecciones
- 48
Preguntas frecuentes
¿La lección «Traducción de direcciones de red (NAT)» es gratis?
Sí — el texto completo de «Traducción de direcciones de red (NAT)» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de Linux Networking & TCP/IP for Developers, actualiza a CoddyKit PRO. El curso de Linux Networking & TCP/IP for Developers incluye 4 lecciones en total.
¿Qué aprenderé en «Traducción de direcciones de red (NAT)»?
Explore los distintos tipos de NAT y su función en la conservación de direcciones IPv4 y la seguridad de la red. Practicas Linux Networking & TCP/IP for Developers con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.
¿Necesito experiencia previa para empezar Linux Networking & TCP/IP for Developers?
No se requiere experiencia previa. Linux Networking & TCP/IP for Developers en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 3 de 4.
¿Cuánto tiempo toma la lección «Traducción de direcciones de red (NAT)»?
La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.
¿Puedo escribir y ejecutar código en esta lección de Linux Networking & TCP/IP for Developers?
Sí. Cada lección de Linux Networking & TCP/IP for Developers incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.
Todas las lecciones de este curso
- Direccionamiento y conceptos de IPv6
- Protocolos de enrutamiento avanzados (RIP/OSPF)
- Traducción de direcciones de red (NAT)
- Subnetting y CIDR en profundidad