How Does an IP Address Work? 32-Bit Header Architecture & Routing Explained

1. The Bitwise Architecture of an IPv4 Address

An IPv4 address consists of exactly 32 contiguous binary bits. For human readability, these 32 bits are divided into four 8-bit groupings known as octets, separated by periods, creating the standard dotted-decimal notation (such as 192.0.2.1).

Each octet can represent any integer value ranging from binary 00000000 (decimal 0) to binary 11111111 (decimal 255). As a mathematical result, the maximum theoretical pool of IPv4 addresses is 2^32, equaling exactly 4,294,967,296 unique addresses.

Importantly, an IP address is conceptually divided into two distinct components: the Network Identifier (Prefix), which designates the specific subnetwork or cloud VPC, and the Host Identifier, which uniquely distinguishes the individual interface, server, or container on that subnetwork.

Dotted Decimal:    192.168.1.100
Binary Octet 1:    11000000  (= 192)
Binary Octet 2:    10101000  (= 168)
Binary Octet 3:    00000001  (= 1)
Binary Octet 4:    01100100  (= 100)
-------------------------------------------------------------
Full 32-Bit Value: 11000000101010000000000101100100 (32 bits)

2. The IPv4 Packet Header: How Routers Read Addresses

In the Layer 3 (Network Layer) of the OSI model, data generated by application protocols (such as HTTP or SSH) is encapsulated within an IP packet. Under RFC 791, the base IPv4 header is 20 bytes long and contains critical control metadata.

The final 8 bytes of every standard IPv4 header are reserved for the Source IP Address (32 bits) and Destination IP Address (32 bits). When an intermediate router receives a packet, it reads the Destination IP address, performs a longest prefix match against its internal routing table, decrements the Time to Live (TTL) counter by 1, recalculates the Header Checksum, and forwards the packet toward the next-hop gateway.

3. Public vs. Private IP Addresses (RFC 1918 Scope)

Because the 4.3 billion address IPv4 space could not support every internet-connected smartphone, server, and IoT device, the IETF issued RFC 1918 to reserve three distinct private address blocks for internal enterprise and home local area networks (LANs):

1. 10.0.0.0/8 (10.0.0.0 to 10.255.255.255): Contains 16,777,216 addresses. Widely deployed in enterprise campus networks and cloud VPC architectures.

2. 172.16.0.0/12 (172.16.0.0 to 172.31.255.255): Contains 1,048,576 addresses across 16 contiguous /16 blocks. Heavily utilized in Docker containers and Kubernetes overlay networks.

3. 192.168.0.0/16 (192.168.0.0 to 192.168.255.255): Contains 65,536 addresses across 256 /24 subnets. The default standard for home consumer Wi-Fi routers.

Private IP addresses are strictly non-routable across the public internet. Internet Service Provider (ISP) border routers immediately discard packets with RFC 1918 source or destination addresses.

4. Network Address Translation (NAT) and Port Forwarding

To allow millions of devices with private RFC 1918 addresses to communicate across the single public IP assigned by an ISP, routers implement Network Address Translation (NAT), specifically Port Address Translation (PAT / NAPT - RFC 3022).

When an internal device (e.g., 192.168.1.50) opens an outbound TCP connection to a web server, the local gateway router rewrites the source IP in the packet header to the router's own public WAN IP and substitutes a unique ephemeral source port (e.g., port 54321).

The router registers this translation in its stateful NAT table. When return packets arrive from the remote web server at port 54321, the router reverses the translation, rewriting the destination back to 192.168.1.50 and forwarding it across the LAN.

5. Practical Sysadmin Inspection Commands

To inspect your local machine's IP address, subnet mask, default gateway, and public internet IP, use these verified terminal commands:

# Discover your public facing IP address via secure HTTPS API
curl -s https://ifconfig.me
# or
curl -s https://api.ipify.org

# Linux: Show private IP and active network interfaces
ip -4 addr show

# macOS: Show local Wi-Fi private IP address
ipconfig getifaddr en0

# Windows Command Prompt: Inspect full TCP/IP configuration
ipconfig /all

# Trace packet hops and inspect intermediate router IP addresses
traceroute 1.1.1.1
# Windows:
tracert 1.1.1.1