Blog · Home network
Same Wi‑Fi: one public IP for everyone?
Usually yes. Your router gets one public IP from the ISP and shares it via NAT. Phones and PCs on that Wi‑Fi will match on What Is My IP Address IP unless one uses a VPN or different network.
Private addresses still differ
Inside the LAN each device gets its own DHCP lease (for example 192.168.1.10 vs 192.168.1.11). Those private IPs are not what websites see; they only see the shared WAN address after NAT.
When the public IP differs on the same SSID
If one laptop runs a VPN and another does not, their checkers show different exits. Guest networks or VLANs with separate routing are rare in homes but can differ in corporate setups.
Mobile data breaks the pattern
Switching a phone to LTE gives a carrier address, not your home broadband IP. Compare in mobile data vs Wi‑Fi.
People also ask
Ethernet vs Wi‑Fi same IP? Usually yes on the same LAN—the router still NATs one WAN address for all LAN clients.
Smart home hubs? IoT devices share the same public face too unless they use a separate cellular modem.
Why does my TV show a different IP in its menu? That menu is almost certainly the TV’s private IP, not the WAN address.
Extended guide: one WAN, many sessions
Think of your router as a receptionist with one public phone number. Outbound calls share that number; return calls get routed to the right desk using port and session tables. That is why every device on Wi‑Fi can browse simultaneously without needing its own global IPv4 in a typical NAT setup.
Games and peer-to-peer apps sometimes need extra help (UPnP, manual forwards, or IPv6) because unsolicited inbound packets do not know which LAN host to reach without explicit mapping.
If one device uses a VPN, it breaks the “same public IP” pattern for that device because its traffic exits elsewhere. Everyone else on the LAN still shares the ISP address.
Understanding this model prevents false bug reports like “my phone and laptop differ on the IP site” when one runs a VPN client.
Edge cases: guest networks, VLANs, and policy-based routing
Enterprise Wi‑Fi sometimes maps “same SSID” to different VLANs behind the scenes. Guests might egress through a separate NAT with a different public IP than employees—even though the network name looks identical on the sticker. If two laptops on the “same Wi‑Fi” show different checkers, ask whether one is on guest isolation or a split tunnel.
Mesh routers occasionally steer clients between bands or satellites in ways that briefly change the path seen by upstream logging. The public IP usually stays the same on consumer gear, but corporate controllers can push different exit policies per VLAN. Always capture which SSID and which security profile you used when sending diagnostics.
Parental controls and filtering DNS can change which sites load without changing your IP. If support asks for IP only, still mention filters—otherwise they may chase the wrong hypothesis when a domain is blocked upstream.
IPv6 can add a second visible address family while IPv4 stays shared. Two devices might both show the same IPv4 if the ISP uses a small NAT pool, yet each has unique IPv6 temporary addresses. Clarify which family a game or service keys off when troubleshooting voice chat or strict NAT warnings.
Public hotspots that force VPN usage (schools, some airports) can make every client appear as the hotspot’s aggregator first, then the VPN exit second. Read the checker after each hop: local Wi‑Fi, then after VPN, to avoid mixing layers in one paste.
Teaching the “one WAN” model in one minute
Draw a box labeled “router” with one line out to “internet.” Inside the box, draw phones and laptops with different private numbers. Explain that websites only see the outside line until something (VPN, different WAN) changes the exit. That picture prevents most household confusion.
Kids on gaming consoles asking “why is my IP the same as my sister’s?” now have a clear answer: shared building address, different room numbers.
If a smart device app shows an IP in its settings, verify whether it is LAN-only before comparing to our checker—many IoT UIs never show WAN at all.
Summary checklist
Test two devices back-to-back on the same SSID with VPNs disabled. If results match, your mental model is right. If not, look for per-device VPN, guest network isolation, or wired vs wireless policy routing.
Teach roommates this checklist before spending hours on “IP mismatch” bugs that are actually expected.
Related guides
- NAT and your public IP — how sharing works.
- Public vs private IP — two layers.
- What IP a VPN shows — per-device exceptions.