Most home devices have an address used inside the local network and communicate with the wider internet through one or more addresses routed by the ISP. The two roles are easy to confuse because both are called “IP addresses.”

Private IPv4 space

The commonly used private ranges are 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. They are intentionally reusable on separate private networks and are not globally routed on the public internet.

Public IP

A public address is routable outside your local network. In IPv4, the router often translates traffic for many private devices through a public connection. In IPv6, addressing and routing work differently and devices can have globally scoped IPv6 addresses while a firewall still controls unsolicited traffic.

Why 192.168.1.1 cannot identify your house

Millions of unrelated networks can use the same private address at the same time. That is why an IP page should never imply that a common private gateway uniquely identifies a router model, owner, or physical location.

Use What Is My IP for the internet-facing address and the router-IP guide for your local gateway.

RFC 1918 private IPv4

10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16 are reusable private ranges. Millions of homes can use 192.168.1.1 simultaneously because the address is not globally routed.

Public and CGNAT

Your router can have a public IPv4, a provider-private/CGNAT address, IPv6, or combinations. The address a website sees can differ from the router WAN value under CGNAT/VPN.

Privacy

A public IP can identify an ISP/block and approximate region but does not reliably identify a person or street address.

Build a mental model, not a list of acronyms

Ask three questions: what address does the device have, what is its next hop, and which service translates names or applies policy? From there, concepts such as DHCP, DNS, NAT, Wi-Fi bands and mesh become connected parts of one path instead of isolated definitions.

Try it on your own network

Read your client IP, subnet/prefix, gateway and DNS values; then compare them with the router’s LAN and WAN status. This harmless observation exercise turns the theory into something you can recognize when troubleshooting later.

A simple lab you can perform without changing your network

Open the connection details on a computer or phone and record four values: local IP address, subnet/prefix, default gateway/router and DNS server. Then open the router status page and compare its LAN address with the client gateway. Finally compare the router WAN address with the public address reported by an external IP service. This reveals the boundary between the local LAN and upstream internet.

Ask what changes when you roam or switch networks

Move from Wi-Fi to mobile data or from one Wi-Fi network to another. The local address, gateway and DNS can all change. This demonstrates why 192.168.1.1 is not “your account” or a globally unique router—it is only meaningful inside the network that routes to it.

Relate names to addresses

Visit a site by hostname and remember that DNS resolved the name before the connection. A DNS failure and an IP-routing failure can look identical in a browser, yet require different fixes. Learning to separate those layers is one of the most valuable networking skills.

Relate Wi-Fi to routing

Wi-Fi is primarily the local radio link. A strong signal can coexist with failed DHCP, broken DNS or an ISP outage. Conversely, slow Wi-Fi can be a local radio problem even when the internet connection is healthy. Treat signal quality and internet reachability as separate observations.

Use standards and primary documentation

When exact behavior matters, prefer RFCs/standards and current vendor/provider documentation. Tutorials are useful for explanation, but model-specific defaults and security behavior can change with hardware revision and firmware.

Addressing evidence to collect

Write the client IP/prefix, default gateway, DHCP server, lease state and router LAN/WAN addresses. Compare networks mathematically instead of matching the first three octets by eye. Overlapping private ranges become especially important with VPNs, second routers and virtual networks.

Do not confuse local and public identity

Private addresses are reusable and scoped to the LAN. NAT/CGNAT can make several devices or even several customers share public addressing. Treat public-IP lookups as network metadata, not proof of an individual person or exact location.

Questions you should be able to answer after this guide

  • Which device is the default gateway on your current network?
  • Which values are local/private and which are internet-facing?
  • Which component supplies addressing, name resolution and Wi-Fi access?
  • Which observation would distinguish a LAN problem from an ISP/DNS/application problem?

If those answers are clear, the concept is doing useful work rather than remaining vocabulary.

Keep learning from topology

Compare a simple single-router home with a mesh system, an ISP gateway plus personal router, and a VLAN/guest-network design. The same protocols are present, but ownership of routing, DHCP, firewalling and Wi-Fi changes. That comparison explains many real-world “why is this address different?” questions.