In common IPv4 deployments, network address and port translation also maps transport ports, allowing multiple internal endpoints to share fewer externally routable addresses. Other NAT forms use static or dynamic one-to-one mappings.
For an outbound flow, the translator rewrites relevant packet-header fields, maintains a mapping, and reverses the translation for matching return traffic. Explicit inbound mappings can publish an internal service. NAT helps connect overlapping or private address realms and conserve IPv4 addresses, but it changes end-to-end addressing and can complicate protocols that carry addresses in their payloads.
Key points
Translation stateDefine mapping behavior, timeouts, port allocation, inbound rules, logging, and capacity for the protocols the deployment must support.
Application impactTest peer-to-peer communication, embedded address data, IPsec modes, failover, and troubleshooting; some applications need traversal techniques or application-aware assistance.
Operational evidenceWhere attribution matters, preserve time-synchronized records that connect internal addresses and ports to external mappings without treating those records as proof of user identity.
Important limitationNAT is not a firewall, encryption mechanism, or authorization control. Many NAT products also filter unsolicited inbound packets, but filtering is separate from translation and does not replace explicit security policy.