What is a default gateway, and how do you find yours?

A device can talk directly only to addresses on its own network: the laptop at 192.168.1.20 can reach the printer at 192.168.1.40 without help. Anything else, from a web server to a game console in another country, is somewhere it cannot see. Rather than keep a map of the whole internet, the device keeps a single fallback rule: send everything unknown to the default gateway and let it work out the rest.

The gateway is a router with at least two sides. Its LAN side has an address on your network, 192.168.1.1 in the diagram, which is the address your devices know it by. Its WAN side has the address your internet provider assigned, which is what the rest of the world sees. The router forwards packets between the two and, through network address translation, rewrites the source address so replies find their way back to the right device.

The word default matters. A device may hold more specific routes (a VPN client adds some; an office PC may have a route to a second subnet), and those win when they match. The default route is the catch-all that applies when nothing more specific does. In the routing table it appears as destination 0.0.0.0 with mask 0.0.0.0 in Windows' route print, and as default in ip route on Linux and netstat -nr on macOS.

The three values appear together in every network settings screen and are easy to confuse. Each answers a different question.

The subnet mask and the gateway work as a pair. The mask tells the device that 192.168.1.0 through 192.168.1.255 are local; the gateway must be inside that range, or the device has no way to reach it. A gateway of 192.168.2.1 with a /24 mask on 192.168.1.20 is a configuration error, and the symptom is a connection that looks fine but cannot load anything. The subnet calculator shows the exact range any mask covers.

Your gateway is not the same as your IP address, though on a home router the gateway and the DNS server are often the same address because the router handles both jobs. And your gateway is not your public IP: that belongs to the router's WAN side and comes from your provider.

Windows 11

1. Open Settings, then Network & internet.
2. Open Advanced network settings, then Hardware and connection properties.
3. Find your active adapter (Wi-Fi or Ethernet) and read the Default gateway line.

The Wi-Fi properties page under Settings shows your IPv4 address and DNS servers but not the gateway, which is why this route goes through Advanced network settings. Faster: open Terminal or Command Prompt, type ipconfig and press Enter; the Default Gateway line under your adapter is the answer. In PowerShell, Get-NetIPConfiguration lists it as IPv4DefaultGateway.

macOS (Sequoia and Tahoe)

1. Open System Settings, then Wi-Fi (or Network, then Ethernet for a wired connection).
2. Click Details… next to the connected network.
3. Open the TCP/IP tab. The gateway is the Router field.

In Terminal, netstat -nr | grep default prints the same address.

iPhone and iPad

1. Open Settings, then Wi-Fi.
2. Tap the ⓘ next to the network you are connected to.
3. Scroll to IPV4 ADDRESS. The gateway is the Router line.

Android

1. Open Settings, then Network & internet, then Internet.
2. Tap the gear next to the connected network.
3. Scroll to Network details; the gateway is the Gateway line.

Samsung phones put it under Settings, Connections, Wi-Fi, the gear next to the network, then View more; the Manage router button on that screen opens the gateway's address in your browser.

Linux

Run ip route. The first line reads something like default via 192.168.1.1 dev wlan0; the address after via is the gateway.

Whatever the device, the gateway is the address to type into a browser to reach the router's admin page. The guide to finding your router's IP address covers brand defaults and login problems.

A device without a gateway can still talk to its own network, so file sharing and printing keep working while every website times out. The settings screen shows the gateway field blank, or the address is there but unreachable. The common causes:

• DHCP failed. The device never received an address from the router and fell back to a 169.254.x.x link-local address, which comes with no gateway at all. Rebooting the router and reconnecting usually fixes it; the 169.254 guide covers the rest.
• A static address was typed in by hand and the gateway field was left empty or filled with the wrong subnet. Switch the connection back to automatic (DHCP) or correct the value.
• Two routers on one network. A mesh satellite or a second router in router mode hands out its own gateway, and devices behind it reach the internet through a double translation layer. Put the second box in access point or bridge mode.
• The router is up but its uplink is down. The gateway responds to ping, yet nothing beyond it does. That is a provider or modem problem, not a gateway problem.

On Windows, the troubleshooter message The default gateway is not available almost always means a Wi-Fi driver or power-saving issue on the laptop rather than a router fault; updating the adapter driver and turning off its power-management option clears most cases.

Two addresses describe your connection, and websites only ever see one of them. The gateway (192.168.1.1) is private: millions of homes use the identical address, and it means nothing outside your walls. The public address on the router's WAN side is the one the internet uses to reach you, and it is what the homepage shows. The local IP page explains how to read your device's own private address and why browsers no longer reveal it to websites.

One useful check: log in to the router and compare its WAN address with the public address shown on the homepage. If they differ, or the WAN address starts with 100.64 through 100.127, your provider has put another router of its own in front of yours. That is carrier-grade NAT, and it explains why port forwarding on your gateway does nothing.