Skip to content
TR EN
5 min read · · UK Bilişim Network Engineering Team

/22, /23 and /21 Subnet Masks: How Larger Networks Work

Why Go Beyond /24? Growing Network Requirements

A /24 network with the 255.255.255.0 mask offers 256 addresses, 254 of which can be assigned to devices. For a small office that is often enough. As the network grows, though, the number of devices in a single segment rises quickly: desktops, IP phones, printers, wireless clients, security cameras and IoT devices all have to share the same address pool.

At that point there are two options:

  • Split the network into VLANs and define each segment as its own /24
  • Widen the mask and use a larger address block

The second approach leads to "in-between" prefixes such as /21, /22 and /23. They are used both for large flat segments (guest Wi-Fi, labs, production networks) and for aggregating several /24s into a single route (route summarization). This article walks through the common logic of all three prefixes.

The /23 Subnet Mask: Combining Two /24 Blocks

/23 means 23 network bits and 9 host bits. Its key values:

  • Subnet mask: 255.255.254.0
  • Total addresses: 2⁹ = 512
  • Usable hosts: 512 − 2 = 510
  • Wildcard mask: 0.0.1.255

Example: let's calculate 172.16.2.0/23 step by step:

  1. The mask has 254 in the third octet; the block size is 256 − 254 = 2.
  2. The network address is 172.16.2.0 (the third octet is a multiple of 2).
  3. The network spans 512 addresses; the broadcast address is 172.16.3.255.
  4. Usable range: 172.16.2.1 – 172.16.3.254.

In binary it is clear: 254 = 11111110. The last bit of the third octet has moved to the host side and can be 0 or 1. So 172.16.2.0/24 and 172.16.3.0/24 merge into a single /23 network.

The /22 Subnet Mask in Detail: Host Count and Range

/22 is the most commonly used wide prefix in enterprise networks. The steps:

  1. Host bits: 32 − 22 = 10
  2. Total addresses: 2¹⁰ = 1024
  3. Usable hosts: 1024 − 2 = 1022
  4. Mask (binary): 11111111.11111111.11111100.00000000 → 255.255.252.0
  5. Wildcard mask: 0.0.3.255

A concrete example: 192.168.4.0/22

  • Block size: 256 − 252 = 4 (in the third octet)
  • Network address: 192.168.4.0
  • First usable address: 192.168.4.1
  • Last usable address: 192.168.7.254
  • Broadcast address: 192.168.7.255

This network covers four consecutive /24 blocks: 192.168.4.0/24, 192.168.5.0/24, 192.168.6.0/24 and 192.168.7.0/24.

The critical rule — alignment: the third octet of a /22 network must be a multiple of 4 (0, 4, 8, 12…). For example, "192.168.6.0/22" is not a valid network start: if you give that address to an interface, the device considers itself part of the 192.168.4.0/22 network, and in route or ACL definitions most routers return an "inconsistent address and mask" error. Either way, the network boundaries end up different from what you expected.

Bit Shifting with /21 and Larger Prefixes

All subnetting logic comes down to one rule: each time the prefix shrinks by 1, capacity doubles.

  • /24 → 254 usable hosts
  • /23 → 510
  • /22 → 1022
  • /21 → 2046 (mask 255.255.248.0)
  • /20 → 4094 (mask 255.255.240.0)

Example: 10.20.0.0/21 has a block size of 8 in the third octet (256 − 248 = 8):

  • Network address: 10.20.0.0
  • Usable range: 10.20.0.1 – 10.20.7.254
  • Broadcast address: 10.20.7.255

Alignment applies here too: the third octet of a /21 network must be a multiple of 8. In bit terms, /21 moves the last 3 bits of the third octet to the host side; 3 bits give 8 combinations, so 8 /24s merge into one block.

Enterprise Scenario: Choosing the Right Mask for a 500+ Device Office

Picture a three-floor office: 260 desktops, 80 IP phones, 35 printers, an average of 120 wireless clients and security cameras. That is more than 500 devices in total.

  • /23 (510 hosts): Looks "just enough" on paper. But once you account for static assignments for printers, cameras and access points and leave room to grow, the pool can run out within a year or two.
  • /22 (1022 hosts): Offers roughly twice the headroom. It is the safe choice for designs that need one large segment (guest Wi-Fi, production network, test lab).

An architecture note: a flat broadcast domain of 1,000 devices increases ARP and broadcast traffic. A healthier approach is to define per-floor /24 VLANs and advertise them on the router as a single /22 summary (route summarization guide), using /22 both as a segment size and as a summarization tool.

Quick Comparison Table: /21, /22, /23 and /24

CIDR Subnet Mask Total Addresses Usable Hosts Block Size (3rd octet)
/21 255.255.248.0 2048 2046 8
/22 255.255.252.0 1024 1022 4
/23 255.255.254.0 512 510 2
/24 255.255.255.0 256 254 1

Troubleshooting: How the Wrong Mask Breaks Connectivity

Mistakes with wide prefixes usually show up as "some IPs work, some don't":

  • Misaligned network definition: if you define 192.168.6.0/22, the real network is 192.168.4.0/22. DHCP hands out addresses from the wrong range, and IPs you did not expect appear to be "on the same network".
  • Mask too narrow on a device: if a server on a /22 network is configured with /24, it sends packets for addresses in the neighboring /24 blocks to the gateway instead of delivering them directly. If there is no gateway, or a filter in the way, the connection fails; even when it works, it adds an unnecessary hop.
  • Mask too wide on a device: in the opposite case, the device sends ARP requests directly for an IP that actually sits behind a router. With no reply, the connection times out. Some routers compensate with Proxy ARP, but that is not a lasting fix.
  • DHCP scope mismatch: if the network is a /22 but DHCP hands out only 254 addresses, the pool runs out early; if the scope extends past the network boundary, address conflicts follow.

Verifying Complex Subnet Ranges with the Calculator

The fastest way to avoid these mistakes is to check the arithmetic before you type the configuration. Enter, for example, 192.168.4.0/22 into the IPv4 subnet calculator and it lists the network address, broadcast address, the 1022-address usable range, the wildcard mask and the 32-bit binary layout on one screen. The "Subnet Splitting" tab shows how the /22 block splits into smaller prefixes (/23, /24, /25…) as a table. All calculations run client-side in your browser; no IP data is sent to a server.

If you want to check your range before you plan, use the subnet calculator: enter the CIDR value and see everything from the network and broadcast addresses to the host range in seconds.

Frequently Asked Questions (FAQ)

What is a /22 subnet mask, and how many hosts does it support? →

A /22 is a prefix where the first 22 bits are on the network side. The mask is 255.255.252.0; it provides 1024 total addresses, and 1022 of them can be assigned to devices.

How many /24 networks does a /22 equal? →

It equals four consecutive /24 blocks. For example, 192.168.4.0/22 covers the 192.168.4.0/24, 192.168.5.0/24, 192.168.6.0/24, and 192.168.7.0/24 networks.

Why isn't 192.168.6.0/22 a valid network address? →

The third octet of /22 blocks must be a multiple of 4. 6 does not meet this rule; the address 192.168.6.0 is actually an address inside the 192.168.4.0/22 network.

For a network with 500 devices, should I choose /23 or /22? →

/23 can theoretically handle 510 hosts, but it leaves no room for growth. If the device count is likely to increase, /22 with a capacity of 1022 hosts is the safer choice.

Should a large network like /22 be used as a single VLAN? →

Nearly 1000 devices on a single segment increase broadcast traffic. From an architecture standpoint, the preferred approach is to split the network into /24 VLANs and summarize with /22 on the routing side.

Network Engineering Toolset

All calculations execute client-side in your browser.

11 tools