• NAT (Network Address Translation) rewrites IP addresses at the edge of your network.
    You already built every variant in the NAT module of the CCNA path.

    Let's put everything back in place in one lesson.

    Private Addresses Stop at the Edge

    Your internal hosts use private addresses defined by RFC 1918: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16.
    These ranges are not routable on the public Internet.

    Watch what happens when 192.168.1.5 sends a packet to 8.8.8.8 without translation.

    Packet sourced from private IP 192.168.1.5 dropped at the network edge, showing why NAT is required before configuring NAT and PAT

    Figure 1 – Without NAT, the packet from 192.168.1.5 is blocked

    The packet is dropped at the edge.
    No provider forwards traffic sourced from a private address.

    Your host needs a public address before it can leave.

    Answer the question below

    What happens to a packet sourced from a private address at the edge?

    Translation at the Edge

    Your router provides that public address.
    The translation mechanism is defined in RFC 3022.

    Edge router translating a private source IP into its public IP so internal hosts can reach the Internet, the core NAT mechanism

    Figure 2 – R1 replaces the private source IP with its public IP

    R1 swaps the source 192.168.1.5 for its public address 37.5.55.103.
    It records the mapping in its NAT table.
    When the reply comes back, the table tells R1 which internal host gets the packet.

    Static, Dynamic and PAT are all variations of this mechanism.

    Answer the question below

    Where does the router record each active translation?