What Is Internet Protocol Version 4 (IPv4) and How Does It Work?

If you've ever glanced at your router settings or network diagnostics, you've likely seen a string of numbers like 192.168.1.1 staring back at you. That's IPv4 in action — the addressing system that has powered the internet for decades. Understanding what it is, how it works, and where its limits lie helps make sense of a lot of modern networking decisions.

The Core Idea: What IPv4 Actually Does

Internet Protocol Version 4 (IPv4) is the fourth revision of the Internet Protocol, and it serves one fundamental purpose: giving every device on a network a unique address so that data knows where to go.

Think of it like a postal system. When you send a letter, it needs a destination address and a return address. IPv4 does the same thing for data packets traveling across networks. Every device — your laptop, phone, smart TV, router — gets assigned an IPv4 address, and the protocol governs how packets are routed from source to destination.

IPv4 was defined in RFC 791, published in 1981. Despite being over 40 years old, it remains the dominant protocol in use today.

What an IPv4 Address Looks Like

An IPv4 address is a 32-bit number, typically written in dotted-decimal notation — four groups of numbers separated by periods, each ranging from 0 to 255.

Example:192.168.0.105

Each of those four groups is called an octet (because it represents 8 bits). Four octets × 8 bits = 32 bits total.

That 32-bit structure means IPv4 can support a theoretical maximum of approximately 4.3 billion unique addresses (2³²). In the early 1980s, that seemed enormous. Today, it's a well-known bottleneck.

Public vs. Private IPv4 Addresses

Not all IPv4 addresses work the same way. There's an important distinction between public and private addresses.

Your home router uses Network Address Translation (NAT) to let multiple devices share a single public IP address. Your phone, laptop, and smart speaker each get a private IP on your local network, while your router presents one public IP to the wider internet. This NAT workaround has been one of the main strategies for stretching IPv4's limited address pool.

How IPv4 Packets Work 🌐

Data doesn't travel across the internet as one continuous stream — it's broken into packets. Each IPv4 packet contains:

• Header: Metadata including the source IP, destination IP, time-to-live (TTL), and protocol type
• Payload: The actual data being transmitted

The TTL field is particularly important. It's a counter that decrements every time the packet passes through a router (a "hop"). If it reaches zero, the packet is discarded — this prevents lost packets from circulating indefinitely.

IPv4 is a connectionless protocol, meaning it doesn't establish a dedicated path before sending data. Packets may take different routes and arrive out of order. Higher-level protocols like TCP handle reassembly and error correction.

Subnetting and CIDR: Dividing the Address Space

Large networks don't hand out addresses randomly. They use subnetting to divide an address range into smaller logical segments.

CIDR notation (Classless Inter-Domain Routing) expresses this efficiently. For example:

• 192.168.1.0/24 means the first 24 bits are the network portion, leaving 8 bits for host addresses — that's 254 usable device addresses.
• 10.0.0.0/8 is a much larger block, common in enterprise environments.

Understanding subnetting matters for network administrators, but even home users encounter it in router settings when configuring static IPs or setting up VLANs.

The Address Exhaustion Problem

IPv4's biggest structural issue is its limited address space. The Internet Assigned Numbers Authority (IANA) allocated the last blocks of unassigned IPv4 addresses to regional registries in 2011. Regional registries have since run dry as well.

Workarounds like NAT, private address ranges, and IP address leasing have extended IPv4's lifespan. But these are patches, not solutions. This exhaustion is the primary reason IPv6 was developed — it uses 128-bit addresses, offering a practically inexhaustible pool (approximately 3.4 × 10³⁸ addresses).

Many networks now run dual-stack configurations, supporting both IPv4 and IPv6 simultaneously. Your device likely connects over one or the other depending on what the destination server and your ISP support.

IPv4 vs. IPv6: The Key Differences

What Affects Your IPv4 Experience 🔧

IPv4 itself is a standard — but several variables influence how it behaves in practice:

• ISP infrastructure: Whether your provider uses carrier-grade NAT (CGNAT), which adds another layer between you and your public IP
• Router capabilities: Consumer routers handle NAT differently, and some have limits on concurrent connections
• Network size: A home network with 5 devices behaves very differently from an enterprise network with thousands
• Application requirements: Some applications, gaming platforms, or VoIP services behave better with a dedicated public IP rather than shared NAT
• IPv6 support: If your ISP and devices support IPv6, certain traffic may bypass IPv4 entirely

Whether IPv4's limitations create friction in your setup — or whether you'd benefit from a static IP, IPv6 enablement, or a different network configuration — depends entirely on how you're using your connection and what your current infrastructure looks like.