NAT (Network Address Translation)
NAT RFC 1631, May 1994 “The IP Network Address Translator (NAT)” It was evident by the beginnings of the 90s that many more IP addresses would be needed Many more devices IPv4 would not be enough The objective of NAT was to define a mechanism that allowed the sharing of IP addresses by numerous devices "provide temporarily relief while other, more complex and far-reaching solutions are worked out." Two decades later NAT is ubiquitous deployment across the Internet Eventhough IPv6 has been ready for 15 years
NAT (Network Address Translation) + 192.168.1.101 192.168.1.50 189.45.23.99 192.168.1.102 189.45.23.254 ISP 192.168.1.254 97.12.45.123 192.168.1.103
NAPT (Network Address Port Translation) 97.12.45.123 80 189.45.23.99 1505 Dir IP Puerto Dest Org 97.12.45.123 80 192.168.1.102 32655 Dir IP Puerto Dest Org ISP 189.45.23.254 189.45.23.99 192.168.1.102 192.168.1.254 97.12.45.123 80 189.45.23.99 1505 Dir IP Puerto Org Dest 97.12.45.123 80 192.168.1.102 32655 Dir IP Puerto Org Dest 97.12.45.123
NAT header translators 97.12.45.123 80 189.45.23.99 1505 Dir IP Puerto Dest Org Outgoing packet: IP source address, IP Checksum, and TCP checksum Incoming packet: IP destination address, IP checksum, and TCP checksum 97.12.45.123 80 189.45.23.99 1505 Dir IP Puerto Org Dest
NAT (Network Address Translation) Need for more IP addresses Without using IPv6 Balance load Migration from ISPs NAPT. Ideal for SOHO Security “Hide” machines from the exterior
NAT (Network Address Translation) Performance IP and TCP headers modification IP and TCP checksum recalculation Access to the table of addresses Search writing