Local IP vs public IP: the difference that matters
Your local IP (also called a private or LAN address) identifies your phone, laptop, or TV inside the network created by your router. Typical examples look like 192.168.1.42, 10.0.0.15, or 172.16.0.8. Your public IP is assigned by your ISP to the WAN side of the router and is shared by devices when they reach websites. Confusing the two is one of the most common home-networking mistakes — especially when setting up port forwarding, remote desktop, or camera access.
Routerpedia publishes separate tools for each: this page focuses on LAN addressing, while What is my IP? shows the address visible on the internet. Knowing both helps you follow setup guides accurately when a brand article says “enter the device IP” versus “find your WAN IP.”
Why you need your local IP
Printers, NAS boxes, Raspberry Pi servers, Home Assistant, and security NVRs are often reached by local IP in a browser. Port-forward rules on the router point an external port to a specific LAN IP and internal port — if DHCP later hands that device a new address, the forward breaks until you update it or reserve a DHCP lease. Mesh nodes and access points also appear in router device lists with local IPs for management.
When troubleshooting “can’t reach the admin page,” confirm you are on the same Wi‑Fi SSID (not guest isolation), ping the gateway, and check your own local IP is in the same subnet. Our Subnet Calculator explains whether two addresses share a network, which is essential if you intentionally run multiple LANs or VLANs.
How this browser detection works (and its limits)
Web pages are not allowed to read your LAN IP through a simple JavaScript property. This tool uses a widely known WebRTC ICE candidate approach: the browser gathers network candidates for a temporary peer connection, and private IPv4 addresses may appear in those candidates. We never send that address to Routerpedia for storage; it is displayed locally when found.
Detection can fail when WebRTC is disabled, when privacy extensions block candidate exposure, on some corporate-managed browsers, or when only IPv6 link-local addresses are visible. In those cases, use your operating system tools: ipconfig on Windows, System Settings → Network on macOS, or Wi‑Fi details on iOS/Android. You can also open the router’s attached-devices page using a gateway IP from our IP addresses library.
DHCP, reservations, and stable home labs
Most home devices receive local IPs automatically via DHCP from the router. Leases renew periodically; after a long power outage, devices may get different addresses. For anything you port-forward or bookmark, create a DHCP reservation keyed to the device MAC address, or configure a static IP inside the LAN range but outside the DHCP pool — follow your router brand’s guidance so you do not create IP conflicts.
Guest networks often use a different subnet and block access to LAN IPs on purpose. If detection shows an unexpected range, you may be on guest Wi‑Fi or a VPN that creates a virtual adapter. Disable the VPN temporarily when you need the true home LAN address. Check What is my proxy? if you suspect traffic is leaving through an intermediary.
Private IP ranges at a glance
RFC 1918 defines three IPv4 ranges reserved for private networks: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. Consumer routers most often ship with 192.168.1.0/24 or 192.168.0.0/24, but mesh kits sometimes default to 10.0.0.0/24. If your detected address starts with 10, 172.16–31, or 192.168, you are on a private LAN. Link-local 169.254.x.x means DHCP failed — fix cabling or restart the router before chasing other issues.
Use our Subnet Calculator to see whether two addresses share the same network. That matters when a laptop on guest Wi‑Fi cannot reach a printer on the main VLAN by design. VPN clients may inject another private range; your machine can hold multiple local IPs simultaneously across Wi‑Fi, Ethernet, and tunnel adapters.
Finding your gateway and router admin IP
The default gateway — almost always your router — is typically the lowest usable host in the LAN subnet, such as 192.168.1.1. Type that address into a browser to reach firmware settings. Routerpedia maintains a searchable list of common defaults in our IP addresses section when labels fade or brands reuse unusual gateways like 192.168.50.1.
Your local IP and the gateway must sit in the same subnet. If detection shows 192.168.1.50 but the admin page lives at 192.168.0.1, you may be double-NATed through an upstream modem-router still using the factory range. Fix by bridging the ISP box or aligning LAN IP settings before port forwarding. Cross-check your WAN address on What is my IP? when guides reference “router status page IP.”
Port forwarding and stable LAN addresses
Port-forward rules map an external port on your public IP to a specific local IP and internal port — for example, TCP 443 to 192.168.1.100. If DHCP reassigns that server tomorrow, the rule silently breaks. Create a DHCP reservation tied to the device MAC, or assign a static IP outside the dynamic pool but inside the calculated usable range.
Document local IPs for cameras, NAS units, and home automation hubs in a simple spreadsheet. After LAN subnet changes, update every reservation before testing from cellular data outside the home. If inbound connections never arrive despite correct local targeting, ask your ISP about CGNAT — shared public IPv4 blocks classic hosting even when local IPs are perfect.
Virtual machines, Docker, and multiple NICs
Laptops docked with Ethernet and Wi‑Fi active may show whichever interface WebRTC exposes first. Virtual machines and Docker networks add virtual adapters with their own private ranges. Hypervisors often NAT lab VMs through 192.168.x.x spaces separate from your physical router. If detection returns an unexpected address, disable unused adapters temporarily or check the hypervisor’s virtual switch settings.
When a containerized app needs LAN access, use bridged networking or publish ports explicitly rather than guessing addresses. Developers testing captive portals should compare UA strings via What Is My User Agent? on host and guest OS instances. Secure Wi‑Fi credentials from the WiFi Password Generator still matter on lab SSIDs — treat them like production keys if they bridge to your main subnet.
Safety notes
Sharing your local IP on the public internet is usually low risk because private addresses are not globally routable. Still, avoid posting full network maps with device names and open ports. Keep router admin passwords unique, and prefer HTTPS or vendor apps when available for management. For a full toolkit spanning Wi‑Fi passwords, QR sharing, DNS, and ISP identity, visit the Routerpedia tools hub.