How to Find Your Subnet Mask on Any Device
Learn how to find your subnet mask on Windows, macOS, Linux, Android, iOS, and routers with quick commands and simple steps for every setup.
You're sitting in a network settings screen, the VPN client is waiting, and a router change in China can't wait until tomorrow. The IP address is visible, but the subnet mask is hiding behind one more menu, or worse, it looks different on your laptop than on your phone. That's usually the moment people start searching for how to find your subnet mask, because they don't need a lecture, they need the exact value that keeps the connection working.
Table of Contents
- Why You Might Need Your Subnet Mask Right Now
- What a Subnet Mask Actually Means
- Finding Your Subnet Mask on Windows 10 and 11
- Finding Your Subnet Mask on macOS, iOS, Android, and Linux
- Getting the Mask From Your Router and DHCP
- Troubleshooting Missing or Wrong Subnet Masks
- Quick Reference Table and Final Checklist
Why You Might Need Your Subnet Mask Right Now
A subnet mask usually matters when someone has a task that can't be solved by guessing. In mainland China, that often means setting a static IP for a home server, matching a VPN profile to the local network, or sorting out a router change on a small office LAN where the device list is already full of mismatched settings. It can also come up when a video call keeps dropping on corporate Wi-Fi, because the local network details are part of the path that decides whether a device talks cleanly to the rest of the subnet.
The first thing to get straight is that the mask is a property of the local interface, not the public internet side of the connection. That's why trying to “look it up from a public IP” usually leads to confusion, especially on guest Wi-Fi, mobile hotspots, or remote work setups where the visible address changes but the local network rules do not. The practical way to find it is on the device itself, or on the router that handed out the lease, which is why the standard Windows ipconfig workflow remains so widely documented for desktops, while macOS, iPhone, iPad, and Android each expose the same detail in their own network panels. The overview in the Blowfish Technology network upgrade guide is useful if the mask is only one part of a larger office network change.
For readers in China, the question is often not just “where is it”, but “which one should be trusted”. VPNs can show one mask on a virtual adapter, while the physical Wi-Fi adapter keeps another. IPv6 transition can also reshape what appears on screen, so the question becomes whether the task needs IPv4, IPv6, or both.
Practical rule: if the goal is to set a local address, look at the active LAN or Wi-Fi interface first. If the goal is to diagnose a failing connection, compare the device's value with the router's LAN or DHCP settings.
What a Subnet Mask Actually Means
A subnet mask is the line that separates two parts of an IPv4 address, the part that identifies the network and the part that identifies the device. It is a 32-bit binary value made of consecutive 1s, and the device uses it to decide whether another address is local or somewhere else. That decision comes from a bitwise AND between the IP address and the mask, while the broadcast address comes from combining the network address with the inverted mask. The same idea sits behind the way devices decide whether they belong on the same subnet, as described in the subnetting reference from Network Academy.
The format you'll usually see
On home and small office networks, the mask often appears in dotted-decimal form such as 255.255.255.0. That notation is common in routers, Windows adapter details, and many ISP setups in China. You may also see the slash form, such as /24, which means the same thing in shorter CIDR notation.
IPv6 uses a different label, usually a prefix length like /64, but the idea stays familiar. The network side is fixed, and the device side is left available for individual hosts, only the notation changes. In some Chinese network environments, IPv6 transition can make the interface output look different from one adapter to the next, so the value on screen may not look like the older IPv4 mask you expect.
A quick example that makes the math concrete
If a device has 192.168.1.50 with a mask of 255.255.255.0, the network is 192.168.1.0 and the broadcast address is 192.168.1.255. The usable host range runs from 192.168.1.1 through 192.168.1.254. A change from 255.255.255.0 to something else can break a static IP setup even when the IP itself looks fine.
The mask is less about decoration and more about boundaries. If the boundary is wrong, the device may still have an address, but it won't behave like it belongs on the network you expect.
A useful way to check your own network design is to compare that boundary with the rest of the setup. A good infrastructure guide for small businesses can help when the subnet mask is only one part of a larger router, DHCP, and device addressing plan.
If a router dashboard or VPN panel shows /24, /30, or /64, that is not a different kind of setting. It is the same boundary written another way. On guest Wi-Fi, a VPN adapter, or a remote work profile, the mask can look missing or different because you may be seeing the active virtual interface instead of the physical Wi-Fi or Ethernet connection.
Finding Your Subnet Mask on Windows 10 and 11
Windows is the quickest place to check because the operating system puts the active adapter details in plain view. The fastest route is still the same across language packs, which is why it shows up in so many guides: press Win + R, type cmd, press Enter, then run ipconfig or ipconfig /all. The subnet mask appears under the active adapter, right beside the IP details, and that makes the command useful even when the Settings app is harder to use.
Use Command Prompt first
Open Command Prompt, then look for the adapter that matches the connection in use, usually Wi-Fi or Ethernet. The value you want sits on the same block as the IP address, so there's no need to calculate anything by hand. On managed corporate machines, this is often easier than clicking through a locked-down interface.
A second Windows path exists for people who prefer the GUI. Open Settings, go to Network and Internet, then choose Wi-Fi or Ethernet, open the connection details, and check the IPv4 properties screen. The subnet mask may sit behind an edit dialog there, so the value is visible only after one extra click.
If the machine has several adapters, the first result isn't always the right one. VPN adapters, Hyper-V, and other virtual interfaces can show their own masks, so the active physical adapter is the one that usually matters for local network setup.
Older paths still matter
Some systems, especially older Windows builds or tightly managed office images, still route the information through Control Panel. The path runs through Network and Sharing Center and the connection details pane, where the mask appears with the rest of the adapter data. That's slower than ipconfig, but it still gets to the same place.
Windows editions sold in China may show Simplified Chinese labels in some dialogs, so the visual labels can differ from English screenshots. The layout still follows the same logic, which means the adapter name, IPv4 details, and subnet mask are the fields to watch.
The main rule on Windows is simple. Check the active adapter, not the most interesting one.
Finding Your Subnet Mask on macOS, iOS, Android, and Linux
Macs, phones, Android handsets, and Linux boxes all expose the same basic value, but each platform hides it in a different place. That matters in China because many people switch between a laptop at a coworking space, an iPhone on hotel Wi-Fi, and a Linux server sitting in a back room. The label may change, yet the local network boundary still exists.
macOS
On macOS, open System Settings, choose Network, select the active connection, then open Details or Advanced and check the TCP/IP tab. The subnet mask sits alongside the IP address in that screen, just as NordVPN's macOS walkthrough describes. Older System Preferences layouts use slightly different labels, but the destination is the same.
iPhone and iPad
On iPhone and iPad, open the connected Wi-Fi network's info screen and look for Subnet Mask under the address details. That's usually enough for a quick check, though carrier profiles and managed configurations can hide extra network information in China-based mobile setups. If the device is on Wi-Fi, the mask is tied to that local network, not to the cellular connection.
Android
Android commonly shows the value in Wi-Fi under the connected network's advanced or IP settings. Some Chinese ROMs tuck it under additional network detail panels, so the path can feel less direct than on stock Android. The key is to stay inside the connected network's settings rather than roaming through general internet menus.
Linux
Linux gives the most command choices. ip a or ip addr show usually prints the interface address and mask together, ifconfig still works where installed, and nmcli is useful for NetworkManager users. All three are local interface tools, which makes them better than trying to infer the value from a remote server or a public IP.
On Linux, the mask often appears as a slash prefix next to
inet. That's normal, and it means the interface is already telling the full story in CIDR form.
The same device may show one value on Wi-Fi and another inside a VPN. That doesn't mean the system is broken, only that the active interface has changed.
Getting the Mask From Your Router and DHCP
Sometimes the device screen is only half the answer. If the subnet mask field is blank, greyed out, or inconsistent, the router often has the authoritative setting because DHCP hands out the network details as part of the lease. That's why looking at the router can settle arguments between devices, especially on home broadband boxes and ISP-supplied units in China.
Where to look in the router interface
Sign in to the router admin page, usually through a local management address such as 192.168.0.1 or 192.168.1.1, then check the LAN settings or the DHCP client list. On many ZTE or Huawei firmwares used by Chinese ISPs, the menu labels may appear in Chinese, but the LAN and DHCP sections still perform the same job. The LAN page shows the configured subnet for the whole network, while the DHCP page shows what was leased to each connected device.
A useful habit is to compare the mask on the router with the mask on the device that's misbehaving. If they differ, the router is usually the better place to trust unless a VPN or special interface is in control. That comparison is especially helpful in guest Wi-Fi networks where the local rules are intentionally narrow.
Why DHCP matters
DHCP doesn't just hand out an IP address. It also tells the device what subnet it belongs to, which is why the router can be treated as the source of truth for local network settings. For a broader background on how that relationship works, the Throughwire DHCP and DNS guide is a useful companion once the mask itself is located.
IPv6 complicates the picture a little, because routers may display a prefix length instead of a dotted mask. That's still the same boundary idea, only written in slash notation. On Chinese networks where IPv6 is becoming more common, that interface output can look different from older IPv4-only guides even when the underlying job is the same.
Troubleshooting Missing or Wrong Subnet Masks
When the subnet mask is missing, the first question is whether the interface received a lease. On Windows and Linux, a blank or absent value usually points to a connection that never finished negotiating with the router, which can happen if the cable is loose, the Wi-Fi link dropped, or the router hasn't responded yet. Renewing the lease with ipconfig /renew or bringing the connection back up with nmcli connection up is the cleanest next step.
When the value looks wrong
A mask of 0.0.0.0 usually means the interface isn't carrying a normal local lease, or another system has taken control of it. Guest networks with AP isolation can create that kind of confusion, and VPN clients can do it too by replacing the local adapter details with their own virtual settings. A mask of 255.255.255.255 often points to a host-style setup rather than a normal LAN assignment, so it deserves a second look instead of a quick guess.
The We Fix PC Laptop diagnostics guide is helpful when the issue is broader than one setting, because missing masks often travel with driver issues, flaky adapters, or connectivity errors elsewhere in the stack. For a related failure mode, the Throughwire IP configuration failed note is worth comparing against the device's error message.
VPNs and IPv6 change what appears
VPN clients can create a virtual adapter with its own mask, which is why users in China sometimes see a different value the moment they connect. That virtual value may be a short point-to-point range, while the physical Wi-Fi or Ethernet adapter still belongs to the local LAN. If a static IP works before the VPN connects and fails afterward, the wrong interface is probably being edited.
IPv6-only or dual-stack transitions can be even more confusing. A device may show only a fe80:: link-local address and no normal IPv4 address at all because the upstream network is running IPv6-first. In that case, the router's WAN mode matters more than searching for a missing IPv4 mask.
If the device has no usable IPv4 details, don't force a static IPv4 setup onto an IPv6-only link. Check the router mode and the network type first.
The quickest fix path is usually simple. Confirm the interface is up, compare the router's LAN setting, disable the VPN if it's owning the adapter, and then refresh the lease.
Quick Reference Table and Final Checklist
| Mask | CIDR | Hosts | Typical Use |
|---|---|---|---|
| 255.255.255.0 | /24 | 254 | Home networks and small office LANs |
| 255.255.255.252 | /30 | 2 | Point-to-point links |
| 255.255.0.0 | /16 | 65,534 | Larger office LANs |
The quick check is simple. Confirm the interface is active, read the mask from the active adapter, and compare it with the router's DHCP or LAN settings if anything looks odd. If the task involves a VPN profile, make sure the VPN's virtual adapter isn't overriding the local LAN value. For router-side verification and logs, the Throughwire router logs guide is a practical follow-up when the mismatch doesn't make sense.
A small checklist keeps the next setup faster:
- Check the active interface: Wi-Fi, Ethernet, or VPN.
- Match the router's value: Use the LAN or DHCP page if the device looks wrong.
- Decide on IPv4 or IPv6: Use the format that matches the task.
- Recheck after reconnecting: Guest Wi-Fi and mobile hotspots can hand out different local settings.
Throughwire gives people working from mainland China a private network option that keeps connections stable without making them dig through extra configuration screens. If this topic came up because a VPN or router change is already on the table, visit Throughwire and see how its setup fits into the same kind of network workflow covered here.