Accessing the Internet: Changes in Host IP Addresses

When you type a URL into your browser and hit Enter, a complex journey begins. A data packet is generated on your local device and begins its trek across the vast expanse of the internet toward a remote server. A common misconception among beginners is that the Source IP address within that packet remains a constant, unchanging identifier throughout the entire transmission. In reality, as a packet traverses different network boundaries, its IP address is often rewritten.

Understanding how and why these addresses change is fundamental to mastering the principles of network communication.
The primary reason for IP address transformation lies in the exhaustion of IPv4 addresses. Because there are not enough unique IPv4 addresses for every device on Earth, the networking world relies on a distinction between Private IP addresses and Public IP addresses.

Most home and enterprise networks operate using private addresses, as defined by the RFC 1918 standard. These addresses are reserved for internal use and are strictly non-routable on the public internet. The three primary blocks are:

• 10.0.0.0/8
• 172.16.0.0/12
• 192.168.0.0/16

Because these addresses cannot travel across the open internet, a device with a private IP cannot communicate with a web server directly. To bridge this gap, a mechanism known as Network Address Translation (NAT) is employed.

The Mechanics of IP Transformation

To understand how addresses change, we must first distinguish between the roles of different networking devices. A critical technical nuance is that standard routers do not modify the Source or Destination IP addresses when forwarding packets. Instead, a standard router simply decrements the TTL (Time to Live) value by one and recalculates the header checksum to ensure the packet continues its journey.

The actual rewriting of the IP address is the exclusive responsibility of a NAT device (typically your home router acting as a gateway).

A Step-by-Step Packet Journey

Consider a typical scenario where a laptop on a home network accesses a website. The process unfolds as follows:

1. Packet Initiation: The host sends a packet. The Source IP is its private address (e.g., 192.168.1.100), and the Destination IP is the server's public address.
2. The NAT Gateway Intervention: The packet reaches the home router. The router recognizes that the packet is destined for the internet. It replaces the private Source IP with the Public IP assigned by the ISP (e.g., 203.0.113.5) and records this change in a translation table.
3. Internet Transit: As the packet moves through various intermediate routers across the internet, the Source and Destination IPs remain unchanged.
4. Server Reception: The target server receives the packet. From the server's perspective, the request originated from the router's public IP (203.0.113.5), not the laptop's private IP.
5. The Return Trip: The server sends a response back to the router's public IP.
6. De-encapsulation and Delivery: The router receives the response, consults its NAT table to find which internal device requested that specific data, restores the original private Destination IP, and delivers the packet to the host.

NAPT: Managing Multiple Devices via Ports

In modern networks, dozens of devices (phones, laptops, smart TVs) often share a single public IP address. To prevent data from being sent to the wrong device, NAT is usually implemented as NAPT (Network Address Port Translation). This involves mapping not just IP addresses, but also port numbers.

NAPT Transformation Example

Suppose a host at 192.168.1.100 uses local port 5000 to access a server at 198.51.100.20 on port 443. The NAT gateway's public IP is 203.0.113.5.

The NAT gateway maintains an internal Translation Table to keep track of these mappings:

This table is the "brain" of the gateway, ensuring that even when thousands of connections are happening simultaneously, the return traffic is routed to the correct local device.

Other Scenarios Where IP Addresses Change

While NAT is the most common cause of IP transformation, several other scenarios can change the IP address that a server sees:

• Dynamic Public IPs: Most residential broadband connections use DHCP or PPPoE to obtain an IP from the ISP. This means your public IP is not permanent; it may change every time you restart your modem or when the ISP reassigns addresses.
• Carrier-Grade NAT (CGN): Due to the extreme scarcity of IPv4, many ISPs implement NAT at their own core network level. In this case, your data undergoes double NAT—once at your home router and once at the ISP level. The destination server sees the ISP's massive gateway IP rather than your specific connection.
• Mobile Network Transitions: When a smartphone moves from a Wi-Fi network to a cellular (5G/LTE) network, or roams between different base stations, its external IP address changes. This transition is often why active connections (like a video call or a game) might momentarily drop.
• VPNs and Proxies: When using a VPN (Virtual Private Network) or a proxy server, your traffic is encapsulated and sent to a remote gateway. The destination server only sees the IP address of the VPN exit node, effectively masking your true public IP.

Summary

The IP address of a host is not a static "fingerprint" that remains constant during a session. Instead, it is a dynamic identifier that evolves as it crosses network boundaries. While standard routers act as simple traffic directors, NAT devices act as translators, allowing the vast majority of the world's devices to communicate using a limited pool of public addresses. Understanding where and how these changes occur is essential for anyone looking to troubleshoot connectivity, analyze server logs, or dive deeper into advanced networking technologies like port forwarding and intranet penetration.