Understanding NAT and Private IP Addresses

Network Address Translation (NAT) is a technique that modifies IP address information in packet headers as traffic passes through a router. NAT is essential for conserving public IPv4 addresses and providing a layer of network abstraction.

Private IP Address Ranges

RFC 1918 defines three private IP address ranges that are not routable on the public internet: - 10.0.0.0 to 10.255.255.255 (10.0.0.0/8) - 172.16.0.0 to 172.31.255.255 (172.16.0.0/12) - 192.168.0.0 to 192.168.255.255 (192.168.0.0/16)

Devices using private addresses cannot communicate directly with the public internet without NAT.

How NAT Works

SNAT (Source NAT)

When a server with a private IP (10.0.1.5) sends traffic to the internet, the NAT router replaces the source IP with its own public IP and assigns a unique source port. The router maintains a translation table to map return traffic back to the original server.

DNAT (Destination NAT)

When external traffic arrives at the router's public IP on a specific port, the router translates the destination to the appropriate private IP and forwards the traffic. This is commonly used for port forwarding.

NAT in Cloud Infrastructure

Cloud platforms use NAT in several ways: - Virtual machines typically receive private IPs with NAT for internet access - Floating IP addresses use DNAT to map a public IP to a private VM IP - Port forwarding exposes specific services to the internet

Benefits of NAT

• Conserves public IPv4 addresses (many private devices share one public IP)
• Provides a layer of isolation (internal IPs are not directly addressable from outside)
• Enables flexible network re-addressing without affecting external connectivity

Limitations

• Breaks end-to-end connectivity (inbound connections require explicit port forwarding)
• Can complicate certain protocols (SIP, FTP) that embed IP addresses in application data
• Adds a small amount of latency for translation processing

Understanding NAT is essential for configuring server networking, especially when dealing with firewalls, port forwarding, and cloud infrastructure. ## Key Takeaways

• NAT translates private (RFC 1918) addresses to public addresses at the network boundary, allowing many devices to share a single public IP
• SNAT handles outbound traffic by rewriting the source address; DNAT handles inbound traffic by rewriting the destination (port forwarding)
• Cloud platforms use NAT extensively — VMs receive private IPs, and floating or elastic IPs use DNAT to expose services publicly
• NAT conserves address space and adds isolation, but it breaks end-to-end connectivity and can complicate protocols that embed IP addresses in application data