Why Two Devices Share One Public IP Address

Why Two Devices Share One Public IP Address

TL;DR / Summary: Every device in your home shares one public address because a router performs network address translation. That is normal, it is why the internet works at all on IPv4, and it explains why a website cannot see your laptop directly.

One address, many devices

The provider assigns a single public address to your connection. Inside the home, each device has a private address from a range reserved for local use.

The router rewrites outgoing packets so they appear to come from the public address, and tracks which reply belongs to which device.

That tracking table is the whole mechanism. Without it, replies would arrive with nowhere to go.

Private addresses and why they repeat

Ranges such as 192.168.x.x are reserved for private networks and are not routed on the public internet. Millions of homes use the same private ranges without conflict, because the router separates them.

That is why two devices on different networks can both be 192.168.1.10 without any problem. The public address is the distinguishing factor.

What each layer does

  • Public address — identifies your connection to the internet
  • Private address — identifies a device inside your network
  • Port number — identifies the conversation inside the device

Three identifiers, three scopes. Confusing them is the source of most home networking questions.

Why websites cannot see your device

A website logs the public address and the port the router chose. It has no visibility of the private address behind it.

That is a privacy benefit and a functional limitation. It is also why port forwarding exists: it tells the router to send incoming traffic on a specific port to a specific device.

NAT is the reason your home network works and the reason your server does not, at the same time.

Two devices behind the same router are indistinguishable to an external server except by port, which is why shared addresses complicate rate limiting and ban systems.

When the shared address causes problems

Online games, video calls, and remote access occasionally fail because both peers are behind translation layers. The usual fix is a relay or a direct connection over a different route.

Rate limits and security blocks can affect everyone behind one address, which is a problem in shared housing and public Wi-Fi.

Some sites treat an address shared by hundreds of users as suspicious. That is a limitation of their design, not something you can configure away.

Checking what you actually have

Compare the address a lookup site reports with the address your router’s status page shows. If they match, you have a normal single-layer setup.

If they differ, you are behind carrier-grade NAT, which is common on mobile and some fibre connections. Port forwarding will not work in that case, whatever the router settings say.

Check whether the address changes when you reboot. A stable address is easier to work with, and some providers offer one on request.

IPv6 changes the picture

With IPv6, each device can have its own public address and translation is not required. Many networks run both, which is why a lookup may return two different results.

If a site behaves differently depending on the address family, check which one your device prefers. That single difference explains a surprising number of inconsistent results.

For a quick check of the address your device presents, the IP inquiry tool shows the public address and family, which is the starting point for any of these comparisons. Then look at the router page to see the other side.

Ports and how conversations stay separate

When two devices open connections to the same server, the router rewrites the source port so replies can be distinguished. The server sees two different ports at one address.

That is why a website can serve both devices without confusion. Each connection is identified by the combination of address and port.

It is also why port forwarding has to name a device. Incoming traffic has no conversation to match, so the router needs an explicit rule.

Translation works because ports give every conversation a name.

When ports are exhausted, new connections fail. This is rare at home and common on large shared networks, and it presents as intermittent timeouts.

Understanding the table explains a whole class of “internet is broken but only for one app” complaints.

Why VPNs change the address everyone sees

A VPN replaces the first hop of every connection. Your traffic leaves through the provider’s server, so websites see the provider’s address rather than your home one.

Inside the home, nothing changes: devices keep their private addresses and the router still translates. Only the public address moves.

That is why a VPN can make a regional service work and a local one fail, with no change to the router at all.

A VPN relocates your public address. It does not change your local network.

Split tunnelling sends some traffic through the VPN and some around it, which is why two devices can show different addresses on the same network.

If results are inconsistent, check the tunnel status first. It explains more surprises than any router setting.

Why game consoles sometimes report a strict NAT

Consoles check whether incoming connections can reach them. Behind translation with no forwarding rule, the answer is no, and the console reports a strict type.

Forwarding the console’s ports to its private address fixes it, provided the connection is not behind carrier-grade NAT.

Strict NAT is a description of reachability, not a fault.

If forwarding does not help, check whether the provider shares addresses. A shared address cannot be forwarded at all.

Similar Posts