##### ###### ##### ### # # ### # # ###### ## ## ## ## ## ## ## # # # # # ## ##### #### ##### # # # # # # # #### ## # ## ## ## ## # # # # # ## ## # ###### ## ### # ### # ######
##### ###### ##### ### # # ### # # ###### ## ## ## ## ## ## ## # # # # # ## ##### #### ##### # # # # # # # #### ## # ## ## ## ## # # # # # ## ## # ###### ## ### # ### # ######
##### ###### ##### ### # # ### # # ###### ## ## ## ## ## ## ## # # # # # ## ##### #### ##### # # # # # # # #### ## # ## ## ## ## # # # # # ## ## # ###### ## ### # ### # ######
Address translation techniques
Why NAT exists
The problem NAT solves
Two address spaces
The three private ranges
Address translation basics
Step by step translation
Inside, outside, local, global
One-to-one mapping
Pool-based translation
Many-to-one translation
Port differentiation
Tracking connections
Why NAT is useful
The downsides of NAT
Protocol-specific issues
Getting through NAT
Full cone, symmetric, and more
NAT at ISP scale
IPv6 to IPv4 translation
Allowing inbound connections
Exposing a device completely
Internal to internal via public IP
Cisco router setup
One-to-one mapping setup
The transition path
Resource usage and scaling
Common issues and fixes
AWS, Azure, GCP patterns
Test your understanding
Address classifications
Protocol problems
Summary of NAT and PAT