Network guides
IPv4 vs IPv6: Address Exhaustion, NAT and How to Diagnose Both
The internet runs on two versions of the IP protocol. IPv4, the older one, has been the foundation of networking for decades and still carries most traffic. IPv6 is its successor, designed to solve the central problem that has shaped modern networking: IPv4 addresses are a finite, exhausted resource. Both run in parallel today, and understanding how they differ is essential for anyone who diagnoses networks.
The differences go beyond the length of an address. IPv4 uses 32-bit addresses, which gives about 4.3 billion possible addresses - nowhere near enough for every device. IPv6 uses 128-bit addresses, providing a practically limitless pool. This change, and the workarounds it forced, explains NAT, address complexity and much of the confusion you encounter when troubleshooting.
-
1981
IPv4 is standardized
RFC 791 defines the 32-bit addressing scheme that will carry the internet, with roughly 4.3 billion addresses.
-
1998
IPv6 is introduced
RFC 2460 defines the 128-bit successor, aiming to solve the impending address shortage with an effectively unlimited pool.
-
2011
The IPv4 pool runs out
The Internet Assigned Numbers Authority allocates the last IPv4 address blocks, accelerating the transition to IPv6.
-
2020s
IPv6 becomes mainstream
Major ISPs, cloud providers and operating systems enable IPv6 by default, and it carries a growing share of global traffic.
The fundamental difference: address space
The core difference between IPv4 and IPv6 is the size of their address space. IPv4 uses 32-bit addresses, written as four decimal numbers separated by dots, such as 192.168.1.1. This gives about 4.3 billion unique addresses. IPv6 uses 128-bit addresses, written as eight groups of hexadecimal digits separated by colons, which yields an effectively unlimited number of addresses.
This difference is not cosmetic. The exhaustion of IPv4 addresses forced the development of techniques like NAT and address sharing, which add complexity and break end-to-end connectivity. IPv6 was designed from the ground up with enough addresses for every device to have a globally routable address, removing the need for those workarounds.
How IPv4 addresses ran out
IPv4 was designed in the early 1980s, when the internet was a research network with a few hundred computers. Nobody anticipated billions of devices. By the 1990s it became clear that 4.3 billion addresses would not suffice, and measures like subnetting, CIDR and private address ranges were introduced to delay the exhaustion.
The private ranges - 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 - are the foundation of home and office networks. They are reused everywhere, and Network Address Translation (NAT) maps them to a single public address. NAT allowed the internet to keep growing, but it introduces complexity, breaks some peer-to-peer connections, and is one of the most common sources of troubleshooting headaches.
Reading and diagnosing IPv4 and IPv6
The two address formats demand different habits. An IPv4 address is easy to recognize and commonly appears in logs, while IPv6 addresses are long, include hexadecimal letters, and often contain long runs of zeros that can be compressed. Correctly interpreting them is the first step in diagnosing connectivity problems, since a missing bracket in a URL or a wrong prefix will break a connection.
Diagnosing also means checking whether IPv6 is actually in use. Many networks have both stacks running, and a failure in one can go unnoticed while the other still works. Tools like ping, traceroute and ipconfig or ip addr reveal which address family is active, and whether a host has an IPv6 address, a default gateway, or is falling back to IPv4.
What the transition means for you
For most users, IPv6 is invisible: their operating system, router and ISP handle both protocols automatically. The practical impact shows up when things break. A service that only listens on IPv4 may be unreachable over an IPv6-only connection, and some networks fail to route IPv6 correctly, causing delays and connectivity that silently falls back.
The takeaway is to treat IPv4 and IPv6 as two separate networks that must both work. When troubleshooting, check both address families, verify routing and DNS resolution for each, and remember that a symptom on one version does not prove the other is healthy.
要点总结
IPv4 and IPv6 are two networks sharing one internet. Knowing how their addresses differ, why NAT exists, and how to check both families turns confusing failures into clear, fixable problems.