192.168.1.1 is the private IPv4 address many home routers use as their default gateway, and it is also where the router's admin panel lives. To log in, connect to the router's Wi-Fi or plug in a cable, type http://192.168.1.1 into the browser's address bar (not the search box), and enter the admin username and password printed on the router's label.
If the page doesn't open, the most likely reason is that your router uses a different address, such as 192.168.0.1. Your computer already knows the right one: run ipconfig on Windows and use whatever appears as Default Gateway. The rest of this page covers the login itself, what to check when it fails, and what to change once you're in.
Logging in, step by step
- Join the router's Wi-Fi network or plug in an Ethernet cable. Use a cable if you plan to change Wi-Fi settings, so you don't get cut off halfway through the change.
- Open any browser. Edge, Chrome, Firefox and Safari all work.
- Type
http://192.168.1.1 into the address bar and press Enter. Typed into a search box, it just gives you search results. - If you see a certificate warning, accept it. Some routers use a self-signed HTTPS certificate, and the warning is expected on your own router.
- Enter the admin credentials from the label, or the ones you chose during setup. This is the admin password, which is usually not the same as the Wi-Fi password.
- If you're still on a default password from the label or the table further down, change it now.
Most brands also give you a friendly hostname that points at the router while you're connected to it: routerlogin.net (Netgear), tplinkwifi.net (TP-Link), myrouter.local (Linksys), router.asus.com (ASUS) and dlinkrouter.local (D-Link). Most also have a mobile app that does the same job.
One thing to know before troubleshooting: the address only works from inside your own network. You can't open your home router's 192.168.1.1 from the office, and that's by design. Remote administration should stay off unless you have a specific need and know how to secure it.
When 192.168.1.1 won't open
Most failures come down to one of three things: the router uses a different address, you aren't actually on its network, or the address was mistyped. Check them in that order before you start restarting hardware.
Your router uses a different address
Don't guess. Ask your device for its default gateway, and use that.
On Windows 10 or 11, open Command Prompt or Windows Terminal and run ipconfig. Look for Default Gateway under your active Wi-Fi or Ethernet adapter. In PowerShell you can pull out just the address:
Get-NetRoute -DestinationPrefix "0.0.0.0/0" | Select-Object -ExpandProperty NextHop
Without a terminal, go to Settings > Network & internet, select Wi-Fi or Ethernet, open your connection's properties and read the IPv4 details. If the command line is new to you, our guide to basic Command Prompt commands walks through ipconfig and the commands around it.
On macOS:
route -n get default | grep gateway
# or
netstat -nr | grep default
In the GUI, open System Settings > Wi-Fi, click Details next to your network, then TCP/IP. The gateway is the field labeled Router.
On Linux:
ip route show default
# default via 192.168.1.1 dev wlp2s0 proto dhcp ...
On Android, open Settings > Network & internet > Internet (or Wi-Fi), tap the gear or arrow next to your network, and look for Gateway or Router. Phone makers rename these menus, and some tuck the field under Advanced. On an iPhone or iPad, open Settings > Wi-Fi, tap the (i) next to your network and read the Router field.
Whatever comes back, whether 192.168.0.1, 10.0.0.1 or something else, that is your login address.
You aren't on the router's network
A phone on mobile data, a laptop on a neighbour's Wi-Fi, or any device with a VPN connected can't reach your router's panel. Disconnect the VPN and try again.
Two less obvious cases catch people too. If your adapter has a manually set IP in a different subnet, it can't talk to the router; set it back to obtain an address automatically (DHCP), then run ipconfig /release and ipconfig /renew. And if an ISP modem-router sits in front of your own router, you may be logging in to the wrong box. Your PC's gateway is always the device it is directly connected to.
The address was mistyped
A surprising number of people type 192.168.l.1, with a lowercase letter L where the digit 1 should be. In many fonts the two look almost identical, but the result isn't an IP address, so the browser treats it as a search term or hostname and fails. The usual variants:
- 192.168.l.1 or 192.168.1.l: letter "l" instead of the digit "1". Should be 192.168.1.1.
- 192.168.o.1: letter "o" instead of the digit "0". Should be 192.168.0.1.
- www.192.168.1.1: the "www." turns it into a hostname. Use http://192.168.1.1.
- 192.168.1.1.com: now it's an internet domain.
- 192.168.11 or 192.168.1: an octet is missing.
An IPv4 address always has exactly four numbers from 0 to 255, separated by dots. If yours contains letters, it's a typo.
The router answers, but the page still fails
Run ping 192.168.1.1 (or your real gateway address). Replies mean the router is reachable and the problem is the browser. "Request timed out" or "Destination host unreachable" means the problem is the network or the address, so go back to the sections above.
For browser problems, try another browser or a private window. Old cached redirects, HTTPS-only mode and extensions can all break router pages, so try http:// and https:// explicitly.
Nothing works
Unplug the router for about 30 seconds, plug it back in, and give it a couple of minutes to boot fully. If that fails, a factory reset is the last resort: with the router powered on, hold the recessed reset button with a paperclip, typically for around 10 seconds (check your model's manual), until the lights change. Everything goes back to the label defaults, including your Wi-Fi name and password.
Default usernames and passwords by brand
Check the sticker first. Newer routers increasingly ship with a unique password printed on the label or make you create one during setup, and rules such as the UK's product security regime, in force since April 2024, ban universal default passwords on new consumer devices. The table lists only defaults that vendors document publicly.
Brand | Default address | Username | Password |
|---|
Netgear | routerlogin.net or 192.168.1.1 | admin | password (very old models: 1234). Newer models make you set one during setup. |
Linksys | myrouter.local or 192.168.1.1 | (often blank or admin) | admin |
TP-Link | tplinkwifi.net, 192.168.0.1 or 192.168.1.1 | admin (older models) | admin on older models. Newer models ask you to create one on first login. |
ASUS | router.asus.com, 192.168.50.1 or 192.168.1.1 | admin | admin on some models and firmware. Newer models make you set one. |
D-Link | dlinkrouter.local or 192.168.0.1 | admin | (blank) |
ISP-supplied routers play by different rules. They usually carry a unique admin password on the label, and some ISPs lock parts of the panel or move management into their own app.
If you changed the password and forgot it, there is no backdoor. You need the factory reset described above, which wipes every other setting along with it.
What 192.168.1.1 actually is
Every device on a home network gets a private IP address from the router, and the router needs an address on that network too. Manufacturers pick a predictable one so you can find it, and 192.168.1.1 and 192.168.0.1 are the most common choices.
When your laptop wants to reach anything outside the home network, it sends the traffic to this address, which is why it's called the default gateway:
Laptop 192.168.1.23
↓
Router (default gateway) 192.168.1.1
↓ NAT translates to your public IP
ISP network
↓
Internet
The router also runs a small web server on that same address. That web server is the admin panel where you change Wi-Fi settings, passwords, DHCP, port forwarding and firmware.
Websites never see 192.168.1.1. They see the public IP address your ISP assigns to your router, which uses Network Address Translation (NAT) to share that one public address among all your private devices.
The 192.168 range
The 192.168 prefix isn't specific to routers. It is one of three private IPv4 blocks reserved by RFC 1918 for internal networks. Anyone can use these addresses inside a private network, and routers on the public internet won't forward them. That's how the same 192.168.1.1 can exist in millions of homes at once without a clash: each one points to a different router, and none of them is visible from outside.
Block | CIDR | Address range | Typical use |
|---|
10.x.x.x | 10.0.0.0/8 | 10.0.0.0 to 10.255.255.255 | Large companies, cloud VPCs, some ISP routers |
172.16.x.x to 172.31.x.x | 172.16.0.0/12 | 172.16.0.0 to 172.31.255.255 | Corporate networks, Docker default bridge networks |
192.168.x.x | 192.168.0.0/16 | 192.168.0.0 to 192.168.255.255 | Home and small office routers |
The whole 192.168.0.0/16 block holds 65,536 addresses. A home router normally uses one /24 slice of it, such as 192.168.1.0/24, which gives 254 usable host addresses (192.168.1.1 to 192.168.1.254). In that subnet, 192.168.1.0 identifies the network and 192.168.1.255 is the broadcast address, so neither is assigned to a device.
192.168.0.1 and 192.168.1.1 are simply the first usable addresses in two different /24 subnets. Neither is better; it comes down to the manufacturer and the ISP's firmware. 192.168.1.1 is common on Linksys, Netgear, many ISP-supplied routers and some TP-Link and ASUS models. 192.168.0.1 shows up on TP-Link, D-Link and many cable routers. Many newer ASUS models use 192.168.50.1, and 192.168.100.1 is usually the status page of a cable modem, not your Wi-Fi router.
For developers: checking whether an IP is private
If your services log client addresses, apply rate limits or accept webhooks, you'll often need to know whether an incoming IP is private. Since .NET 8, System.Net.IPNetwork makes that a one-liner:
using System.Net;
IPNetwork[] privateV4 =
[
IPNetwork.Parse("10.0.0.0/8"),
IPNetwork.Parse("172.16.0.0/12"),
IPNetwork.Parse("192.168.0.0/16"),
];
bool IsPrivate(IPAddress ip) => privateV4.Any(n => n.Contains(ip));
Console.WriteLine(IsPrivate(IPAddress.Parse("192.168.1.1"))); // True
Console.WriteLine(IsPrivate(IPAddress.Parse("8.8.8.8"))); // False
Changing your Wi-Fi name and password
Menu labels differ by brand, but the flow is the same everywhere:
- Log in to the admin panel at your gateway address.
- Open the section called Wireless, Wi-Fi, WLAN or Wireless Settings.
- Change the Network Name (SSID). Leave out your name, address and router model.
- Set security to WPA3-Personal, or WPA2/WPA3 mixed mode if you have older devices. Fall back to WPA2 with AES only for a device that can't handle WPA3, and never use WEP or WPA/TKIP.
- Enter a new password (also called a passphrase, pre-shared key or PSK). Four or five random words make a phrase that is strong and still easy to type.
- Repeat for each band (2.4 GHz, 5 GHz, 6 GHz) unless your router uses one combined network.
- Click Save or Apply. Every device disconnects and has to rejoin with the new password.
Changing the Wi-Fi password leaves the admin password untouched. They're separate settings, and you should change both.
Five minutes of hardening while you're logged in
Being in the admin panel is the right moment to fix the settings attackers count on. Start with the admin password: make it long and unique, and change the admin username too if the router lets you. Then find Firmware Update (often under Administration or System), install anything pending, and turn on automatic updates if they're offered. If the vendor no longer ships firmware for your model, its known vulnerabilities will never be fixed, and it's time to replace it.
After that, work through the switches that should usually be off:
- Remote management, meaning admin access from the internet (WAN), unless you truly need it.
- WPS. The PIN method in particular has a long history of brute-force weaknesses.
- UPnP, if nothing depends on it. It lets devices open ports automatically, which is convenient for game consoles but risky with poorly secured smart devices.
Finally, put visitors and smart-home gadgets on a guest network so they can't see your laptops and NAS, and look at the DHCP client list or attached-devices page. Anything you don't recognize is worth investigating.
Questions people still ask
Why does 192.168.1.1 send me to a different page or an app?
Many modern routers redirect the admin address to a branded hostname or tell you to use the vendor's mobile app. Some mesh systems do almost everything in the app and offer only a limited web panel. That is normal, not an error.
Can someone hack my router through 192.168.1.1?
Only someone already on your network can reach that address, unless remote management is on. The real risks are weak admin passwords, outdated firmware and remote access left enabled. Fix those and the address itself is not a vulnerability.
Can I change my router's address from 192.168.1.1?
Yes. Look for LAN or LAN Setup in the panel. The usual reason is a conflict with a second router or a VPN that uses the same subnet. After saving, reconnect and log in at the new address.
What about 192.168.1.254?
It's an equally valid gateway address in the same subnet, and some ISPs configure their routers at .254 instead of .1. Your device's Default Gateway setting tells you which one your network uses.
For a shorter overview of what you can configure once you're in, see Understanding 192.168.1.1: Your Key to Router Configuration.
Join the conversation! Your thoughts help the community grow.