Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


A default gateway is the next-hop router a device normally uses when no more specific route matches a destination. At home, that is often the router's local address. It is not automatically your public IP address, DNS server, or the website you are opening. Understanding the route matters more than memorizing a common address such as 192.168.1.1.[1][2]
Key Takeaways:
- The destination address determines which route is considered.
- A more specific route can take priority over a default route.
- Wi-Fi, Ethernet, IPv4, IPv6, and VPN interfaces can have different routes.
- Finding a gateway address is an observation; changing it can break connectivity.
A device compares the destination with its routing information. If the destination is on a directly connected network, the device can normally deliver through that local interface. For another network, it needs a next hop that can forward the packet. A default route covers destinations for which no narrower match is available.[1][2]
The gateway is that next hop, not the final destination. A browser still requests the website's address; it does not replace the website with the router's address. The router can forward onward through other routers before the packet reaches the destination.
Consider an illustrative laptop on 192.168.10.0/24 with address 192.168.10.24 and gateway 192.168.10.1. A request to another directly connected address in that subnet follows the local route. A request to an unrelated internet address may use the default gateway. These example addresses describe a model, not values to copy into your own settings.
Use the subnet-mask explanation to understand how the device distinguishes the local network. For the wider VPN model, read the complete VPN guide.
| Term | Question it answers | Common confusion |
|---|---|---|
| Destination address | Where is this packet intended to go? | Assuming every request targets the router |
| Default gateway | Which next hop handles otherwise unmatched destinations? | Treating it as the public address |
| DNS resolver | Which address belongs to this hostname? | Assuming it chooses every network route |
| Router | Which device forwards between networks? | Assuming it has only one address |
| Public source IP | Which address does a remote service observe? | Assuming it equals the local gateway |
A home router may also provide DNS forwarding and Wi-Fi, which makes these roles look like one setting. They remain separate responsibilities. Changing the DNS resolver does not necessarily change the next-hop router, and changing a VPN exit does not necessarily change the router's local address.
Routing uses a destination prefix rather than simply asking whether a default gateway is listed. In the ordinary IPv4 forwarding model, the more specific matching prefix wins. Other selection rules, including metrics and policy, resolve the applicable alternatives within the system's configuration.[2]
A default IPv4 route is represented by 0.0.0.0/0. Its zero-length prefix matches every IPv4 destination, so it is useful precisely when there is no preferred narrower route. A specific route to a work network can coexist with it.
The diagram shows a routing decision, not a measured network. A local destination follows the connected route; an unmatched destination follows an applicable default. A VPN can add its own interface and routes, changing which path applies without turning the home router into the VPN server.
A settings screen often presents a convenient summary. It may omit a VPN route, a policy rule, or another active interface. Seeing a gateway in Wi-Fi details proves that configuration exists; it does not establish that every application's traffic uses it.
If Ethernet and Wi-Fi are both connected, record both interfaces. If a work tunnel is active, record its state as well. Do not remove routes just to make the display look simpler. On managed devices, ask IT which configuration is expected before attempting a repair.
For example, a specific company-network route can send private business destinations into a tunnel while the normal default handles unrelated browsing. A full-tunnel policy can instead direct broader traffic through the tunnel. The configuration and actual destination decide the outcome.
Start with a read-only view and identify the active connection. The following table is an entry point, not a replacement for the full router-address guide, which gives platform-specific navigation and explains common address variations.
| Platform | Read-only place to start | What to record |
|---|---|---|
| Windows | Run ipconfig; inspect the connected adapter | Adapter name, local address, Default Gateway |
| Mac | Open the active network's TCP/IP details | Connection name and Router value |
| iPhone or iPad | Open the connected Wi-Fi network's information | Network name and Router value |
| Android | Open the connected network's details; labels vary | Active network and any Gateway or Router value |
Microsoft documents ipconfig as a way to display address configuration. Read the relevant adapter instead of copying the first gateway-looking line: disconnected, virtual, and VPN adapters can also appear.[3]
Android manufacturers and releases differ, and some settings views do not expose the same field. If it is absent, consult the device's documentation or network administrator. Do not install an unknown scanner solely to obtain an address.
Finding the address does not authorize logging into a router, changing its password, or altering a shared network. At a hotel, school, or workplace, the administrator owns those tasks. A router's web interface may also be disabled or available only through another approved management method.
If your goal is simply to report a connection failure, the address and active-interface name are usually enough starting context. Redact unrelated network details before posting diagnostic output publicly.
IPv6 has its own routes. Its default route is ::/0, and default routers can be learned through Router Advertisements. The next-hop router may use a link-local address, where the interface or zone is important to distinguish the local link.[4]
Consequently, an IPv4 gateway does not describe an IPv6 request. A device may have working IPv6 connectivity while IPv4 fails, or the reverse. The website's resolved addresses and the selected connection influence which family is used.
Do not replace a link-local IPv6 gateway with the router's public address because it “looks more complete.” A displayed interface suffix can be meaningful rather than cosmetic. Ask for the expected configuration if the route appears unfamiliar.
Networks can advertise more than one router or have deliberate failover. The presence of several entries is not a diagnosis of malware or misconfiguration. Compare the active interface and system policy with the administrator's intended design.
The useful troubleshooting question is whether the route for the failing destination is valid and reachable. It is more precise than asking whether the device has exactly one gateway value.
A VPN gateway is a tunnel endpoint or forwarding component in the VPN design. It differs from the home router's local next hop even when both are called a gateway. The VPN-client explanation describes the software that establishes the tunnel and applies its configuration.
For AethoVPN, enabling global mode sends all applications' traffic through encrypted VPN forwarding; this describes the product's traffic mode, not a claim that the app gives arbitrary access to devices on your home LAN. Distinguish that tunnel policy from the local router address shown in network settings.
Router features also have separate purposes. UPnP and automatic port mapping concern requests a local application makes to a router; knowing the default gateway does not mean those requests are enabled or appropriate.
A ping response can be one observation, but no response does not alone prove that a gateway is down: systems may filter that diagnostic traffic. Likewise, reaching the router does not prove that its upstream internet connection or DNS resolver works.
At home it often is the router's local address. Other networks and tunnel designs can use different next hops, so inspect the active configuration.
No. A local next-hop address and the source address seen by an internet service have different roles and can be entirely different values.
Yes, a router can perform both roles. That shared value does not make name resolution and packet forwarding the same operation.
Multiple interfaces, IPv4 and IPv6, or deliberate network policy can produce several entries. Determine which route applies to the destination before changing anything.
No. A tunnel can change logical routing while the device still needs its underlying network connection to reach the VPN endpoint.
No. Copying an address from another network can break connectivity. Use the network's supported configuration or ask its administrator for the correct value.
No. Diagnostic packets may be filtered, and a ping checks only one behavior. Combine the result with interface, route, and other connection observations.
Sources:
Sources checked 5 October 2026.
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.