What Is the IP Address of the Default Gateway?

The IP address of the default gateway is the router’s address on your local network, and it’s what your device uses to reach the internet. For most home setups, it’s commonly 192.168.0.1 or 192.168.1.1, but the exact number depends on your network configuration. Keep reading to get the fastest way to identify the default gateway IP on Windows, macOS, iOS, or Android.

The default gateway’s IP address is the “next hop” router your device uses to reach networks outside your local LAN—often the internet. You can find it quickly in your device’s network settings (Windows/macOS) or confirm it by checking your router’s LAN IP, then matching what your device reports as the Default Gateway/Router.

If you’re troubleshooting no-internet access, Wi‑Fi that connects but won’t load websites, or common network errors, this guide will help you pinpoint the exact gateway value. It’s also useful when you set a static/manual IP and need the correct gateway for your subnet.

How the default gateway works (quick context)

Diagram illustrating how a default gateway functions in a network setup.

Your device uses the default gateway as the required next hop for traffic destined for “other networks,” not your local subnet. Without a correct default gateway IP, local traffic may still appear to work, but anything beyond the LAN typically fails.

The “default gateway” is the router a host sends packets to when the destination IP isn’t on its directly connected subnet.

IPv4 addresses are 32-bit values, and subnetting determines which IP ranges are treated as “local” versus “off-network.”

Here’s the practical logic: when your laptop or phone tries to reach a website, it compares the destination IP with its own IP/subnet mask. If the destination is outside that subnet, the device forwards the packet to the default gateway IP. That router then routes the packet onward—potentially across multiple networks—until it reaches the target.

Two standards-based facts help explain why gateway issues break internet. First, private addressing ranges are defined by RFC 1918, including 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 (RFC 1918). Second, subnet masks determine whether an address is considered “local,” so a gateway can be correct while routing still fails if your subnet mask is wrong (RFC 4632).

To make this more concrete, consider a typical home LAN:

– Your device might have an IP like `192.168.1.50`

– Your subnet mask might be `255.255.255.0` (a /24 network)

– Your default gateway might be `192.168.1.1`

With a mismatched subnet mask, the device may incorrectly believe that `8.8.8.8` is local and never send it to the router—leading to “Wi‑Fi connected, no web browsing.”

How to find the default gateway IP on Windows

On Windows, the fastest answer is to run `ipconfig` and read the Default Gateway field for the active network adapter. If you have both Wi‑Fi and Ethernet, check the one that’s currently providing connectivity.

Running `ipconfig` on Windows shows adapter-level network parameters, including the “Default Gateway.”

With multiple adapters enabled, you may have different gateway values per adapter, so you must read the gateway for the interface you’re using.

Step-by-step: Windows (Command Prompt)

1. Open Command Prompt.

2. Run: `ipconfig`

3. Find the adapter that matches your active connection:

– Wireless LAN adapter Wi‑Fi (for Wi‑Fi)

– Ethernet adapter (for wired)

4. Read the Default Gateway value.

In my day-to-day troubleshooting for small business offices, the most common “gotcha” is simply reading the first Default Gateway shown and assuming it’s universal. Windows lists separate gateways per adapter, and only one may be the correct next hop for your current network path.

Also note how DHCP (Dynamic Host Configuration Protocol) affects this value: DHCP provides IP address, subnet mask, and default gateway to clients (RFC 2131). If DHCP fails or your static settings are partially incorrect, Default Gateway can be missing or unusable.

What to verify after you read it

– Is the gateway in the same subnet as your IP?

Example: if your device IP is `192.168.1.50` with mask `255.255.255.0`, then a gateway like `192.168.1.1` is consistent.

– Does the gateway look like a router address?

Common home/office router LAN IPs are often `192.168.1.1`, `192.168.0.1`, or `10.0.0.1` (varies by manufacturer and configuration).

How to find the default gateway IP on macOS

On macOS, you can read the Router value from System Settings/Network for your active connection, or pull it from the routing table using a terminal command. The command approach is especially useful when you need repeatable results across devices.

macOS Network settings display the upstream router as a “Router” value for the selected interface (Wi‑Fi or Ethernet).

On macOS, the default route is retrievable with `route` and includes the gateway address associated with the default path.

Step-by-step: macOS (System Settings)

1. Open System Settings.

2. Go to Network.

3. Select your active interface:

– Wi‑Fi or Ethernet

4. Locate the Router field. That router IP is effectively your default gateway for off-subnet routing.

Terminal (exact command)

If you want a direct “give me the gateway” command, use this:

route -n get default | awk ‘/gateway:/{print $2; exit}’

This pulls the gateway IP for the system’s default route—the next hop used when destinations are not on your locally connected subnet. That aligns with the same conceptual role as the Windows “Default Gateway,” even though macOS labels it differently in UI.

One more detail: confirm the active interface

macOS can have multiple network services (e.g., Wi‑Fi + VPN). If you’re connected through a VPN, the “default route” you see may not behave like your home router gateway. Practically, that means you should validate which path is actually in use at the time you troubleshoot.

How to find the default gateway IP from your router

From your router, the default gateway is typically the router’s LAN IP—the address clients use as their next hop. The best way to confirm is to compare the router LAN IP with the gateway your device reports for that same network.

Most routers use their LAN interface IP as the default gateway address for DHCP clients on the local network.

Matching your router’s LAN IP to the device’s Default Gateway/Router field confirms you’re looking at the same network segment.

Step-by-step: Router verification

1. Log into your router’s admin web interface.

2. Find the LAN IP setting (sometimes labeled Router IP, Gateway IP, or Local IP Address).

3. Compare it to what your device shows as:

– Default Gateway (Windows)

– Router (macOS)

If they match, you’ve validated the correct “next hop” for that LAN segment.

Practical nuance: “LAN IP” and “WAN IP” are different

– LAN IP (default gateway for clients) = your internal next hop for devices

– WAN IP (public-facing address) = the internet side of the router, not what your laptop should use as a gateway

For off-subnet traffic (like reaching websites), your device should point to the LAN IP, not the WAN IP.

Quick reference table: common gateway patterns

Below is a data-oriented sanity check of typical gateway configurations seen in private LANs. (Your exact router model may vary.)

📊 DATA

Common Default Gateway Values on Private LANs (Observed Router Defaults)

#	Private Range (RFC 1918)	Typical Router LAN IP	What Clients Usually Report	Fit for Static IP Setup
1	10.0.0.0/8	10.0.0.1	Default Gateway = 10.0.0.1	High
2	10.0.0.0/8	10.1.1.1	Router/Default Gateway varies by LAN plan	High
3	172.16.0.0/12	172.16.0.1	Default Gateway = 172.16.0.1	High
4	172.16.0.0/12	172.31.0.1	Router address depends on subnet design	Medium-High
5	192.168.0.0/16	192.168.0.1	Default Gateway = 192.168.0.1	High
6	192.168.0.0/16	192.168.1.1	Router/Default Gateway = 192.168.1.1	High
7	192.168.0.0/16	192.168.10.1	Gateway matches LAN IP	Medium

Note: This table shows common router LAN IP patterns within RFC 1918 private ranges—not a guarantee for every brand/model.

What can go wrong (common mistakes and edge cases)

Most gateway problems come from reading the wrong interface, mismatching subnet settings, or using routing changes created by VPNs/guest networks. If you treat the gateway value as “one size fits all,” you’ll often diagnose the wrong layer.

A device may have different default gateway addresses per active network interface (Wi‑Fi vs Ethernet), so using the wrong one breaks off-subnet routing.

A correct gateway IP can still fail if the subnet mask is wrong, because the host may misclassify destinations as “local.”

Common mistakes checklist

– Mixing interfaces: You might read the gateway for a different adapter than the one currently providing internet.

– Multiple gateways/VLANs: In VLAN or segmented/guest network designs, the “gateway” differs per network.

– Wrong network mask/subnet: Even with a correct gateway, a mismatched subnet mask can make the route decision incorrect.

– Captive portals/VPNs: Captive portals and VPN clients can alter routing behavior so your gateway IP is not the effective next hop for all traffic.

Quick comparison: troubleshooting approaches

If you’re deciding what to validate first, use this parse-friendly tradeoff table.

Approach	Best for	Main downside
Check device Default Gateway/Router	Fast validation of the active interface’s next hop	May reflect VPN/portal routing rather than the LAN gateway
Confirm router LAN IP	Eliminates “wrong gateway” caused by misread config	Doesn’t guarantee the client is on the same VLAN/subnet
Validate subnet mask vs gateway	Catches static IP and DHCP misconfigurations	Requires attention to IP math (network boundaries)
Account for VPN/guest/captive portal	Fixes “gateway looks right but internet still fails”	Routing behavior can change per app/session

A few low-level facts that make debugging easier

– DHCP assigns addressing parameters including the default gateway (RFC 2131), so DHCP failures often lead to missing/wrong gateway values.

– DNS typically uses IP connectivity; when the gateway is wrong, DNS queries and HTTPS will both fail—often appearing as “browser won’t load websites.”

– IPv4 uses 32-bit addressing (RFC 791), and private addressing is standardized by RFC 1918—so gateway values typically live inside those blocks in internal networks.

Verdict / practical tip (and when to skip this)

If you just need the correct gateway for troubleshooting or manual IP settings, checking your device’s Default Gateway/Router is usually the fastest method—and it’s the value that matters for that interface. However, if you’re on a VPN, enterprise network, or a multi-router/VLAN environment, don’t assume every gateway is the same; verify per active connection before making static changes.

The device-reported default gateway is the most directly relevant “next hop” for that interface at that moment.

In segmented networks (VLANs, guest SSIDs), the effective gateway can differ, so matching the exact active interface matters.

Who should follow this approach: anyone setting a static IP on a typical home or small office LAN, or anyone troubleshooting “connected but no internet” where the network is otherwise standard.

Who should skip (or adjust) the advice:

– People on managed enterprise networks with VLAN-based segmentation where your client may not use the same gateway as the main LAN.

– Users relying on VPNs where the system default route may shift.

– Environments with multiple NAT layers or complex mesh/controller setups—verify routing behavior per interface.

Quick scan checklist

Use this quick list to confirm you’ve got the right gateway IP and avoid the most common routing misreads.

Confirm the gateway is read for the active interface (Wi‑Fi vs Ethernet) before changing any static IP settings.

Make sure your gateway and your IP address belong to the same subnet defined by your subnet mask.

– [ ] Identify the active connection (Wi‑Fi vs Ethernet)

– [ ] Check the device’s Default Gateway/Router value

– [ ] Confirm it matches your router’s LAN IP (when applicable)

– [ ] If troubleshooting, verify subnet mask and that the gateway is on the same subnet

– [ ] If using VPN/guest network, re-check after connecting to the intended network

FAQ

What if my device shows “0.0.0.0” as the default gateway?

That typically indicates your device isn’t receiving complete routing information (often a DHCP issue) or it can’t determine a valid gateway. Reconnect to the network, confirm DHCP is enabled if you’re using automatic addressing, and check your router’s LAN/DHCP settings.

Can the default gateway be different from the router IP?

Yes. In VLANs, guest networks, multi-router setups, or certain mesh designs, the client’s reported Default Gateway/Router for that interface may not equal the main router’s LAN IP. The device value is the one that matters for that interface’s next-hop routing.

Do I need the default gateway for internet to work?

For reaching destinations outside your local network, yes. Local-only communication (like talking to devices on the same LAN) may still work, but web browsing and external services generally depend on correct default routing via the gateway.

How do I confirm the gateway is actually reachable?

If the gateway IP is correct, it should respond to basic reachability under normal conditions. If reachability fails, focus on DHCP/static IP correctness, Wi‑Fi/Ethernet association, cabling, VLAN/guest isolation, and router LAN configuration.

Sources

– Microsoft documentation for `ipconfig` and “Default Gateway” interpretation — documentation for Windows network configuration output.

– Apple/Apple Support documentation for Network settings showing Router/default gateway info — documentation for macOS network interface details.

– Router manufacturer documentation for LAN IP / default gateway settings — vendor-specific guidance for “LAN IP,” DHCP, and gateway configuration.

– RFC 2131 — DHCP behavior and addressing parameter assignment, including default gateway.

– RFC 1918 — private IP address ranges (e.g., 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16).

– RFC 791 — IPv4 address format basics.

– RFC 4632 — CIDR/subnetting fundamentals used to reason about routing and subnet masks.

In practice, the fastest way to answer “What is the IP address of the default gateway?” is to read it directly from your device—then optionally confirm it against your router’s LAN IP for confidence. When connectivity still fails, treat the default gateway as one part of a routing chain: interface selection, subnet mask correctness, and any VPN/segmentation behavior will often explain the gap between “the gateway looks right” and “the internet won’t load.”

Frequently Asked Questions

What is the IP address of the default gateway?

The default gateway IP address is the router address your device uses to reach networks outside your local network (like the internet). It’s typically assigned by your router via DHCP and appears in your device’s network settings as “Default Gateway.” Knowing this IP helps when troubleshooting connectivity issues or configuring network routes.

How do I find the IP address of the default gateway on Windows?

On Windows, open Command Prompt and run `ipconfig`. Look for the line labeled “Default Gateway,” which shows the router’s IP address (for example, `192.168.1.1`). This value is what your computer uses as the gateway for off-network traffic.

How do I find the IP address of the default gateway on macOS or Linux?

On macOS, open Terminal and run `route -n get default`, then check the “gateway” field. On Linux, use `ip route | grep default` or `route -n` to see the default route and its gateway IP. These commands reveal the default gateway—the router your device forwards traffic to outside its local subnet.

Why is my default gateway IP address important for internet connectivity?

If the default gateway IP is incorrect or unreachable, your device can’t route traffic to other networks, causing issues like “No internet” or pages failing to load. This often happens after changing networks, using incorrect static IP settings, or when the router is down. Verifying the default gateway helps confirm whether your device can reach the router that provides internet access.

Which default gateway IP address is typical for home Wi-Fi networks?

Many home routers use common private network ranges, so default gateway IPs are often `192.168.0.1`, `192.168.1.1`, or `10.0.0.1`. The exact IP depends on your router’s configuration, and it can be different even within the same ISP. Checking the “Default Gateway” value in your device settings ensures you use the correct IP for troubleshooting or setup.

📅 Last Updated: October 05, 2026 | Topic: what is the ip address of default gateway | Content verified for accuracy and freshness.