IPv4 uses 32-bit addresses to identify devices on networks. Routers forward data by matching an address to routing rules. IPv4 runs out of public addresses, so NAT is commonly used today. Some networks still rely on IPv4 alongside newer protocols. IPv4 has practical limits that affect connectivity and configuration.

What is IPv4? | Exalo VPN

IPv4 in one clear definition

IPv4 (Internet Protocol version 4) is a standard method for addressing and routing data across networks. It assigns an IP address to devices so that network equipment (especially routers) can decide where to send packets.

A typical IPv4 address is written in four numbers separated by dots (for example, 192.0.2.10). Under the hood, each IPv4 address is 32 bits long, which results in a finite address space.

A simple model of how IPv4 works

Think of IPv4 communication as sending small chunks of data called packets. Each packet includes:

A source IPv4 address (where the packet is coming from)
A destination IPv4 address (where the packet should go)
Other header information used for forwarding

Routers use the destination address to forward packets toward their target network. Along the way, packets may pass through multiple networks, but the destination address remains the key reference for routing decisions.

Devices typically need an IPv4 address plus supporting information (such as a default gateway) to send packets to the outside network. In many home and business setups, these details are assigned automatically by a local network service.

IPv4 components: address types and the “32-bit” limitation

Because IPv4 uses 32-bit addresses, the total number of distinct addresses is limited. Over time, demand for public IPv4 addresses grew faster than that supply.

To cope with this shortage, networks often use address translation, commonly NAT (Network Address Translation). NAT allows many devices on a private local network to share a smaller number of public IPv4 addresses when reaching the broader Internet.

IPv4 also includes special address ranges with different intended uses (for example, addresses reserved for private networks or other purposes). These ranges affect how packets are routed and whether they are reachable from the public Internet.

Differences and limits to keep in mind

The biggest practical limitation of IPv4 is exhaustion of publicly routable addresses. That is why IPv4 is frequently found alongside address-sharing approaches (such as NAT) and, in newer environments, alongside newer IP versions.

Another important limit is that behavior can differ depending on whether a packet needs to traverse a translation boundary (as with NAT). This can affect how services are reached from the outside and how some application protocols negotiate connections.

Finally, compatibility depends on the network path and configuration. Some networks may still operate primarily with IPv4, while others support both IPv4 and newer IP versions. If an application behaves unexpectedly, the cause is often related to address reachability, routing rules, or translation behavior rather than “IPv4” itself.

Practical checks you can do

You can validate your own IPv4 setup using built-in network tools on your device:

Confirm your device’s IPv4 address and whether it’s private-range or public-range
Check your default gateway (what router your device uses for outside traffic)
Test reachability to common destinations and observe whether failures are local (routing/DNS) or path-related

If you’re diagnosing connectivity, focus on the path between your device and the destination: local addressing, gateway routing, and whether any translation is occurring along the way.