Coursify

Short Notes on NAT (Network Address Translation)

Short Notes on NAT (Network Address Translation)

Verified Sources
Nov 4, 2026

NAT (Network Address Translation) is used to let multiple devices in a private IP network share a smaller set of public IP addresses when communicating with the Internet. Conceptually, a NAT device maintains a translation table that maps internal (private) address/port tuples to external (public) address/port tuples, and applies these translations to packets in both directions. This approach is closely associated with RFC-defined private address ranges and with the growth of IPv4 address scarcity.

Key terms you’ll need for short notes: Private IP (e.g., 192.168.0.0/16), Public IP, and NAT table used by the NAT device to translate traffic consistently.

Important: NAT is often implemented as part of a firewall and is typically stateful—it remembers mappings for active connections to translate return traffic correctly.

NAT explained (Network Address Translation basics)

Why NAT is needed

In IPv4, public addresses are limited. NAT reduces the demand for public IPv4 addresses by allowing many inside hosts to share a single public IPv4 address (or a small pool). In practice, most consumer and enterprise networks use NAT (commonly with port translation) so that outbound traffic from many internal devices can reach external servers using shared public connectivity.

NAT also has operational effects that are useful to mention in short notes:

  • It changes packet header addressing as traffic crosses the boundary between inside and outside networks.
  • It can affect certain protocols that embed IP address information in payloads (not purely headers), requiring helpers/ALG features in some implementations.
  • It influences end-to-end troubleshooting because “who is talking to whom” is not directly visible from outside once translation occurs.

How NAT works (core idea)

When an internal host sends a packet to an external destination:

  1. The NAT device identifies the internal source address (and typically source port).
  2. It chooses/assigns a corresponding external address (and source port if using port-based NAT).
  3. It rewrites the outgoing packet header and records the mapping in the NAT table.
  4. When the return packet arrives from the Internet, the NAT uses the mapping to rewrite the destination back to the internal host/port.

This “mapping + rewrite + state” is the essence of NAT behavior.

Key terms: Translation mapping, Stateful translation, and Timeout.

NAT translation flow (outbound then inbound)

  1. 1
    Step 1

    NAT receives a packet from the inside network; it inspects the source IP (and often source port) to identify the flow.

  2. 2
    Step 2

    If no mapping exists, NAT allocates one in the NAT table; otherwise it reuses the existing mapping for the flow.

  3. 3
    Step 3

    NAT replaces the inside source address with the chosen outside public address; with PAT it also rewrites the source port.

  4. 4
    Step 4

    The rewritten packet is sent to the destination on the outside network.

  5. 5
    Step 5

    When return traffic comes back, NAT looks up the mapping using the translated destination (and port).

  6. 6
    Step 6

    NAT changes the packet’s destination address (and port if applicable) to the original inside host.

  7. 7
    Step 7

    Mappings are removed after connection close or inactivity timeout, to keep the NAT table accurate and bounded.

Common types of NAT (what to write in short notes)

In short notes, it’s enough to describe each type by what it translates and how many hosts share addresses.

  1. Static NAT

    • A fixed private-to-public address mapping.
    • Useful when an internal host must be reachable from outside (e.g., certain server scenarios).

  2. Dynamic NAT

    • NAT assigns a public address from a pool when a private host needs it.
    • Mapping changes over time.

  3. PAT / NAT overload

    • Most common in home/enterprise edge routers.
    • Distinguishes flows using transport-layer ports in addition to IP addresses.

Quick comparison of NAT types (note-friendly)

A conceptual comparison: how many inside hosts can typically share public addresses.

Pro Tip for exam-style short notes

Mention the triad: (1) translation table, (2) header rewriting of IP (and ports for PAT), and (3) state/timeout for mapping—then add one advantage and one limitation.

Common limitations to include

NAT can break or complicate protocols that require inbound connections, embedded address information, or strict end-to-end addressing. It can also complicate logging and troubleshooting because the public view differs from internal host identities.

What else can you write in short notes?

Where NAT sits in typical network architecture

Private addressing

Inside network

Hosts use private IPs and send traffic toward the edge gateway."

NAT gateway/router

Edge boundary

Inspects packets, performs address/port translation, updates NAT table."

Public Internet

Outside network

Packets use translated public addressing; return traffic is mapped back."

Mapping creation and expiry

Session lifecycle

Mappings created per flow and removed after inactivity."

NAT short-notes quick revision

1 / 5
Question · Term

NAT stands for?

Click to reveal
Answer · Definition

Network Address Translation.

Knowledge Check

Question 1 of 4
Q1Single choice

Which statement best describes NAT?

Explore Related Topics

1

Natural Language Processing (NLP): A Comprehensive Short Note

2

Inverted Page Table

An inverted page table (IPT) is a global paging structure that keeps one entry per physical frame, recording the virtual page, process ID, and status bits, thus reducing page‑table memory.

  • Fields: frame index, VPN, PID/ASID, control bits, hash/link.
  • Entries = Physical memory ÷ page size (e.g., 4GB/4KB=2204\text{GB}/4\text{KB}=2^{20}).
  • Lookup uses PID + VPN key; hashing and TLB hide most cost.
  • Benefit: memory usage depends on frames, not on all virtual pages.
  • Cost: slower translation than direct indexing; relies on hashing/TLB.
3

Short Notes on Firewalls (Network Security)

Browse all research articles