Linux Networking & TCP/IP for Developers · Aula

Tradução de Endereços de Rede (NAT)

Explore diferentes tipos de NAT e seu papel na economia de endereços IPv4 e na segurança da rede.

Aula 3 de 412 etapas

Tradução de Endereços de Rede (NAT) é uma aula grátis de Linux Networking & TCP/IP for Developers no CoddyKit. Esta é a aula 3 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Linux Networking & TCP/IP for Developers, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Linux Networking & TCP/IP for Developers inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em 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:

  1. Your laptop (192.168.1.10) sends a request to a website.
  2. Your router intercepts it, changes the source IP to its public IP (e.g., 203.0.113.5), and sends it to the internet.
  3. The website replies to 203.0.113.5.
  4. 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:

  1. Your friend connects to your router's public IP (e.g., 203.0.113.5) on a specific port (e.g., 25565).
  2. Your router has a DNAT rule: any traffic to 203.0.113.5:25565 should be forwarded to 192.168.1.100:25565.
  3. The router translates the destination and sends the packet to your game server.
  4. 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!

Grátis para começar

Aprenda Linux Networking & TCP/IP for Developers com um tutor de IA — grátis

Escreva e execute código real no seu navegador, obtenha ajuda instantânea de um tutor de IA 24/7 e continue de onde parou na web ou no app.

Cursos
12
Aulas
48

Perguntas Frequentes

A aula “Tradução de Endereços de Rede (NAT)” é grátis?

Sim — o texto completo de “Tradução de Endereços de Rede (NAT)” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Linux Networking & TCP/IP for Developers, atualize para CoddyKit PRO. O curso de Linux Networking & TCP/IP for Developers inclui 4 aulas no total.

O que vou aprender em “Tradução de Endereços de Rede (NAT)”?

Explore diferentes tipos de NAT e seu papel na economia de endereços IPv4 e na segurança da rede. Você pratica Linux Networking & TCP/IP for Developers com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar Linux Networking & TCP/IP for Developers?

Nenhuma experiência prévia é necessária. Linux Networking & TCP/IP for Developers no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 3 de 4.

Quanto tempo leva a aula “Tradução de Endereços de Rede (NAT)”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de Linux Networking & TCP/IP for Developers?

Sim. Cada aula de Linux Networking & TCP/IP for Developers inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Endereçamento e Conceitos de IPv6
  2. Protocolos Avançados de Roteamento (RIP/OSPF)
  3. Tradução de Endereços de Rede (NAT)
  4. Sub-redes e CIDR em profundidade
← Voltar para Linux Networking & TCP/IP for Developers