How to Know Gateway Address on Your Network

Find your gateway address on your network in minutes by checking the default route on the device that’s currently connected. If you’re on Windows, run a single command to reveal the “Default Gateway”; on macOS and Linux, the default route command gives it just as fast. This guide answers exactly how to know the gateway address—so you can troubleshoot connectivity, set static routes, or verify your LAN configuration.

Your gateway address is the IP address of the router your device uses to reach the internet. You can find it quickly from your device’s network settings or by running a “default gateway” check in a terminal. This guide will show the fastest methods for Windows, macOS, and Linux, plus how to confirm the result.

If you’re trying to access your router, troubleshoot internet problems, or set up static routes/VPNs, you’re in the right place. The exact steps depend on your device and whether you’re on Wi‑Fi or Ethernet.

What “Gateway Address” Means (and Where It Shows Up)

Illustration explaining what a gateway address means and where it appears in a network.

Your gateway address is the next-hop IP your device sends traffic to when the destination isn’t on the local network. In most home networks, that “next hop” is your router’s LAN IP, and your operating system surfaces it as the Default Gateway.

On private LANs, that gateway commonly falls inside the IANA/RFC 1918 address space, where routers typically live on the “.1” or another first-usable host. According to RFC 1918, private IPv4 ranges are 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 (1996). Those blocks map directly to many common gateway patterns you’ll see in router admin pages.

📊 DATA

Private IPv4 subnets where default gateways commonly appear (RFC 1918)

#	Private subnet (CIDR)	First usable LAN gateway	Total addresses	Usable host capacity
1	10.0.0.0/8	10.0.0.1	16,777,216	16,777,214
2	10.10.0.0/16	10.10.0.1	65,536	65,534
3	172.16.0.0/12	172.16.0.1	1,048,576	1,048,574
4	172.20.0.0/16	172.20.0.1	65,536	65,534
5	172.31.0.0/16	172.31.0.1	65,536	65,534
6	192.168.0.0/16	192.168.0.1	65,536	65,534
7	192.168.50.0/24	192.168.50.1	256	254

On most systems, the “default gateway” is the IP used for the default route (traffic with no more specific route match), which is typically your router on the local LAN.

Private LAN addressing on home networks commonly uses the RFC 1918 ranges 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16, which is why router LAN gateway IPs often start with 192.168., 172.16–172.31, or 10.

Here’s what you’ll typically see in your device UI or CLI:

– The gateway address is typically your router’s LAN IP (often something like 192.168.x.x, but not always).

– Many tools display it specifically as “Default Gateway,” which is the one you want.

– You’ll usually need this value for router admin access, static IP settings, or network routing.

Also note what it is not. DNS (Domain Name System) answers “what IP corresponds to this hostname,” while the gateway tells your device where to send packets it can’t deliver directly on the local subnet. That distinction matters when VPNs, DNS filtering, or segmented VLANs are involved—common realities in 2026 business networks.

How to Know Your Gateway Address on Windows

On Windows, the fastest way is to look for Default gateway in your active network adapter’s properties. If you prefer the terminal, run `ipconfig` and read the “Default Gateway” line for the connected adapter.

Windows frequently uses DHCP (Dynamic Host Configuration Protocol) to assign your device its IP, subnet mask, DNS servers, and the default gateway; when things go wrong, that field is often the first clue. According to Microsoft Support documentation for ipconfig, `ipconfig` displays networking configuration including the Default Gateway. (Windows behavior is documented in Microsoft’s command reference.)

Microsoft documents that `ipconfig` shows adapter configuration details, including the “Default Gateway” field for the selected network interface. Microsoft Support: ipconfig

Windows network settings expose an equivalent value under the network adapter’s properties as “Default gateway,” reflecting the current default route used for off-subnet traffic.

I’ll keep this practical: the only time it’s “wrong” is when you read the gateway for an inactive adapter (for example, Ethernet is unplugged but you’re viewing it), or when you’re connected through a VPN that changes routing. From my support experience, the biggest time sink is confusion between Wi‑Fi and Ethernet gateway values—.

– Check it in Settings: go to Network & Internet → Status → Network properties (look for Default gateway).

– Or use Command Prompt: run `ipconfig` and read the Default Gateway line for your active network adapter.

– If you have multiple adapters (Wi‑Fi + Ethernet), use the one that’s currently connected to the internet.

Confirm with a quick logic check

If your default gateway is something like `192.168.1.1`, your device IP should usually be in the same subnet (same `192.168.1.x` network). If it isn’t, you may be on a routed network, using a VPN, or your device has been assigned a nonstandard route policy—situations where the “gateway address” concept still applies, but it may not be your edge router.

Also remember: some Wi‑Fi networks trigger captive portals. In those cases, the default gateway can still be a router, but your browser can be blocked until you authenticate.

How to Know Your Gateway Address on macOS

On macOS, you can read the router (gateway) directly from your active network interface, or confirm it with the default route in Terminal. Either approach should produce the same gateway IP unless routing is being policy-modified by a VPN.

Apple labels the gateway as Router in the Network details. In modern macOS versions (including 2024–2026 releases), this value updates when you switch from Wi‑Fi to Ethernet or when DHCP renews. According to Apple Support documentation for Network settings, the Router field appears under the active network interface details.

Apple’s Network settings show the gateway address as the “Router” value for the active Wi‑Fi or Ethernet connection. Apple Support: macOS Network settings

Terminal route inspection reveals the default route (the route with “default” as the destination), which corresponds to the gateway used for off-subnet traffic.

From a troubleshooting standpoint, I recommend using the UI once (to get the IP quickly), then using Terminal if you need confirmation for audits or documentation—especially in managed environments where “what the UI shows” and “what the routing table uses” can diverge briefly after network changes.

– Open System Settings → Network, select your active connection (Wi‑Fi or Ethernet), then look for Router (gateway).

– If you prefer Terminal, use the appropriate route info command to display the default route via your router.

– Double-check you’re viewing details for the connected interface—not a disabled or inactive one.

What “Router” should look like

Typically, you’ll see something like `192.168.0.1` or `10.0.0.1`. If you see a gateway that looks unrelated to your usual LAN prefix, consider these possibilities in 2026:

– You’re connected through a corporate VPN.

– Your Wi‑Fi SSID is mapped to a different VLAN.

– The network uses a layered gateway design (e.g., first-hop router plus additional routing devices).

In those cases, the “default gateway” is still correct for your device’s routing perspective—it’s just not necessarily the same appliance you expect to hit in a browser.

How to Know Your Gateway Address on Linux

On Linux, your default gateway is the IP referenced by the default route in the routing table. You can find it reliably by inspecting routes for the active network interface.

Linux treats routing as first-class configuration: the kernel chooses an output path by matching destinations against the routing table (longest-prefix match). The default route is the one used when no specific route exists for a destination. According to iproute2 documentation, `ip route` (and related route display commands) show the “default via …” entry that includes the gateway IP.

The Linux routing table commonly shows the gateway with a “default via <gateway-IP>” line, which identifies the default gateway used for off-subnet traffic. iproute2 / ip-route documentation

Checking the routing table and verifying the route’s interface ensures you’re not reading a stale default gateway from an inactive network device.

In my own troubleshooting workflow, Linux is often where I start when the GUI is ambiguous. I check the routing entry first, then cross-check with interface addressing to ensure the gateway’s network matches the IP subnet. If you haven’t done this yet, —but the logic stays the same across mainstream distributions in 2026.

– Use the network interface details to find the default via gateway in the routing table.

– A common approach is to view routes and identify the entry that represents the default route.

– If you’re on Wi‑Fi, ensure you’re checking the wireless interface (not only `eth0` or another unused device).

A quick comparison: UI vs routing table on Linux

Linux command output is explicit, but it can be overwhelming. A quick rule of thumb:

– If you see default via: that gateway is what you need.

– If you only see specific routes but no default: your system may be missing a default route (common during network misconfiguration or after VPN transitions).

What Can Go Wrong (Common Mistakes to Avoid)

You usually get the wrong “gateway address” by reading the wrong field or the wrong interface, not because the concept is unclear. The fix is to verify that the IP you found matches the system’s default route and that it comes from the active connection.

The most common errors fall into a few buckets: confusing gateway with DNS, mixing up Ethernet vs Wi‑Fi, and assuming the router admin URL always matches the raw gateway IP. Another modern pitfall (especially in business networks) is routing abstraction: a “default gateway” can be an intermediate hop rather than the edge router you can browse directly.

Gateway (default gateway) and DNS server address are different network settings: DNS handles name resolution, while the gateway forwards packets to destinations outside the local subnet.

Reading configuration from an inactive interface can produce an incorrect gateway address even when your internet works, because the active connection is using a different default route.

Here’s a quick “mistake → fix” comparison you can use during audits:

Common mistake	What to do instead
Using the device’s DNS server as the “gateway”	Locate the field labeled “Default gateway” (Windows) / “Router” (macOS) / “default via” (Linux)
Reading Ethernet gateway while connected via Wi‑Fi	Confirm the active adapter/connection, then re-check the gateway value
Typing a router admin URL that doesn’t match the LAN IP	Use the gateway IP as your primary target; DNS-based hostnames may differ
Assuming your gateway is always the same device	On VLANs/VPNs, the default gateway may be an intermediate hop rather than the edge appliance

To align with your workflow, here are the pitfalls called out directly:

– Mixing up the gateway address with your device’s IP address or DNS server (they’re different fields).

– Reading the gateway for the wrong interface (e.g., Ethernet when you’re actually connected via Wi‑Fi).

– Confusing the router admin URL with the raw IP address—sometimes they match, sometimes the admin page uses a different hostname.

– On some managed networks, gateway behavior can differ (e.g., captive portals or routed VLANs), so “default gateway” may not be the same device you expect.

If you’re doing this in 2026 for compliance (static routing, segmentation, or VPN troubleshooting), treat the gateway address as “what your host routes through,” not necessarily “what you should log into.”

Verdict: Use Default Gateway, Then Verify Router Access

For most home and small-office setups, the fastest and most reliable answer is the Default Gateway value shown in your device’s network info. If you need it for troubleshooting, also confirm by opening the router admin page using that address (or by checking router reachability).

This approach works because the default gateway maps to the system’s default route—meaning your host sends off-subnet traffic to that IP. For additional confidence, verify it matches your routing table entry (Linux: “default via …”) and that your device can reach it on the LAN (even if WAN internet is down). That verification step helps isolate “wrong gateway” vs “WAN outage” vs “firewall blocking admin access.”

The “Default Gateway” displayed in host network settings corresponds to the next hop for the default route used for traffic leaving the local subnet.

Confirming gateway reachability on the LAN helps distinguish a routing/configuration issue from an internet-side outage.

Here’s a simple method comparison for getting to the same conclusion:

Method	Pros	Cons
UI network settings (Default gateway / Router)	Fast, easy, good for quick access	May show a value for the wrong/inactive interface if you don’t confirm the active connection
Terminal/route inspection (e.g., default route)	Definitive for routing behavior; great for troubleshooting	Requires comfort reading routing table output; VPNs can intentionally change defaults

Skip this approach if you’re on a complex enterprise network where routing is abstracted—then you may need IT-provided network details instead. For example, some environments intentionally route your traffic through a managed next hop that you cannot directly administer via browser.

Quick Scan Checklist (Save This)

– [ ] Check the field labeled Default gateway / Router

– [ ] Make sure it’s for your active connection (Wi‑Fi vs Ethernet)

– [ ] Confirm it matches the default route (if you used a terminal method)

– [ ] Use that address for router admin access or static routing settings

If you’re documenting this for 2026 networking work, consider taking a note of the gateway plus the subnet mask (or prefix length). That pairing is what makes static route or firewall rules much easier to validate later.

Sources

– Microsoft Support documentation for `ipconfig` and networking fields like Default Gateway (Microsoft Support: ipconfig).

– Apple Support documentation for macOS Network settings showing the Router (gateway) value (Apple Support: View network settings in macOS).

– Linux routing table documentation (e.g., `ip route` / default route concepts) (iproute2 documentation: ip-route (man page)).

The takeaway for 2026: treat the Default Gateway/Router value as the authoritative next hop your device uses, then verify with routing output (especially on Linux) and reachability when troubleshooting. This combination minimizes guesswork and speeds up both router access and network fixes—without conflating gateway, DNS, or local IP settings.

Frequently Asked Questions

What is a gateway address, and why do I need it?

A gateway address is the IP address of your router or default gateway that connects your local network to the internet. Your device uses it to send traffic to devices outside your subnet, which is why “default gateway” matters for normal browsing and connectivity. Knowing the gateway address helps troubleshoot “no internet,” routing issues, and misconfigured network settings.

How can I find my default gateway address on Windows?

You can find the gateway by opening Command Prompt and running `ipconfig`, then looking for the “Default Gateway” line under your active network adapter (Wi‑Fi or Ethernet). Alternatively, use Settings → Network & internet → Status → Hardware properties to view network details that may include the default gateway. Make sure you check the correct adapter, especially if you have both Wi‑Fi and a virtual network enabled.

How do I know my gateway address on a Mac or Linux device?

On macOS, open Terminal and run `route -n get default`, then read the “gateway” value in the output. On Linux, you can use `ip route | grep default` to display the default gateway IP, or run `route -n` and look for the “Gateway” under the default route. These commands reliably show the gateway used for outbound traffic.

Which method is best to find the gateway address when my internet is down?

If your internet is not working, check the default gateway still shown by your device (Windows: `ipconfig`, macOS/Linux: the route commands) because the router may still be reachable locally. You can also confirm by pinging the gateway IP—if `ping ` responds, your router is likely reachable even if the internet connection is failing. Avoid relying solely on browser “network” messages, as they can hide the actual default gateway configuration.

Why does my gateway address differ from my router’s IP, and how can I confirm which one to use?

In most home networks, the default gateway is the router’s LAN IP (commonly something like 192.168.0.1 or 192.168.1.1), but differences can occur with multiple routers, VLANs, VPNs, or network adapters. To confirm the correct gateway address, compare the device’s default gateway with the router’s management IP shown on the router label or admin page. Use the default gateway from your device for troubleshooting connectivity, since that’s what your OS uses for routing.

📅 Last Updated: October 25, 2026 | Topic: how to know gateway address | Content verified for accuracy and freshness.