192.168.0.1

The two-subnet split

192.168.0.0/16 holds 256 possible /24 subnets. Consumer vendors settled on the first two, and then split roughly down the middle over which to ship. There is no technical difference between them and no advantage to either. It is a manufacturing convention that stuck, which is why both 192.168.0.1 and 192.168.1.1 rank among the most searched numeric strings on the web.

The split matters in one practical situation, covered below: chaining two routers that both default to the same subnet.

Hardware that ships with it

Vendor	Notes
D-Link	Standard across the DIR line; some models also answer at dlinkrouter.local
TP-Link	Most Archer routers; also tplinkwifi.net. Their range extenders and some older models use 192.168.1.1
Netgear cable modems and gateways	Several CM and C-series units, unlike Netgear’s routers
Motorola and Arris cable modems	The status page on many DOCSIS units
Ubee, Sagemcom, Hitron	ISP-supplied gateways in various markets
Belkin, Tenda, older Linksys	Model-dependent

Firmware revisions change this, and an ISP that reflashes a unit sets whatever it likes. The table narrows the guess; your gateway command settles it.

Getting in

1. Join the network the router serves, over Wi-Fi or a LAN cable.
2. Enter http://192.168.0.1 in the address bar. Type the http:// part. Browsers upgrade bare hostnames to HTTPS, and most routers answer only on port 80 locally.
3. Sign in with the credentials on the router’s label. Look at the underside, the rear panel, or a card that slides out of the base. Recent units print a unique password per device rather than a shared model default.
4. Set a new password immediately, then check for a firmware update.

Sign in only to hardware you own or manage. Connecting to a network does not grant permission to administer the equipment on it, and unauthorised access to a computer system is a criminal matter under laws such as the Computer Misuse Act and the Computer Fraud and Abuse Act.

Confirm the address before typing it

Your operating system already knows where the router is. It calls it the default gateway.

ipconfig                          Windows: Default Gateway
route -n get default              macOS: gateway
ip route show default             Linux: the address after "via"

iOS puts it in Settings, Wi-Fi, (i), as the Router row. Android lists it as Gateway in the Wi-Fi network details. The router IP guide has the rest, including ChromeOS and PowerShell.

If the answer is something else, follow it: 192.168.1.1, 10.0.0.1, or 192.168.1.254.

When two routers collide

Adding a second router behind the first is where the 0 versus 1 split becomes a real problem. If both default to 192.168.0.0/24, the downstream unit receives a WAN address in the same subnet it serves on the LAN side, and its routing table cannot resolve the ambiguity. Symptoms are a router that seems configured correctly while nothing behind it reaches the internet.

Two fixes:

• Change the downstream router’s LAN subnet, for example to 192.168.50.0/24 with the router at 192.168.50.1, and move its DHCP pool to match.
• Better for most homes, put the downstream unit in access point or bridge mode so there is one router, one subnet, and one NAT.

The same clash appears with corporate VPNs. Many use 192.168.0.0/24 internally, and a home network on the identical subnet will break split-tunnel routing. Moving your LAN to an unusual subnet removes the collision for good.

When the page refuses to open

Wrong address. Run the gateway command. This accounts for most failures.

HTTPS upgrade. Type the full http://192.168.0.1. A private window bypasses a cached HSTS entry.

VPN active. A full-tunnel client can route LAN destinations into the tunnel. Disconnect and retry.

Guest network. Guest SSIDs isolate clients and block management access on purpose.

Your own address is 169.254.x.x. DHCP failed and the device self-assigned a link-local address as RFC 3927 specifies. You are associated but not on the network. Renew the lease, then power-cycle the router.

Bridge mode. A modem in bridge mode has no admin page to serve. Administer the router behind it.

Address in use elsewhere. A statically configured printer or NAS holding 192.168.0.1 will answer instead of the router, showing an unexpected page rather than a login form.

What this address is not

It is not visible on the internet. Routers on the public network drop traffic addressed to RFC 1918 ranges, so a request to 192.168.0.1 never leaves the building. It is also not your public address: that one belongs to your router’s WAN side and is assigned by your ISP. See it on whatsmyip.fyi, with ISP, ASN, and approximate location in the full report.

Looking 192.168.0.1 up in /ip-lookup returns no owner, because private space has no registrant. The public vs private guide explains the boundary in full.