Direct answer
An IPv4 /p prefix leaves 32 − p host bits, so the block contains 2^(32−p) addresses. Apply the prefix mask to an address to find the network and add block size minus one for the final address. Traditional subnet examples subtract network and broadcast addresses for prefixes through /30, but /31 and /32 handling depends on use and standards; never subtract two blindly.
What this calculation tells you
IP addressing uses the relationship “total addresses = 2^(32 − prefix length)”. The useful output is not merely a headline number: it keeps the inputs, units and calculation basis visible so the result can be checked and compared without changing the underlying question.
The two worked situations cover 192.168.10.42/24 and divide /24 into four equal children. Together with the “Common IPv4 prefix capacities” comparison, they show how the method behaves in materially different circumstances and where a real-world rule or measurement still has to come from outside the calculator.
Where it is used
192.168.10.42/24
Address is 192.168.10.42 with prefix length 24. Traditional host range is 192.168.10.1–192.168.10.254, or 254 addresses under that convention.
divide /24 into four equal children
A /24 block must be divided into at least four equal subnets. The /24 provides four equal /26 children.
Common IPv4 prefix capacities
The total column follows pure address arithmetic; the usable column adds an operational convention.
When this guide helps
- You need to reproduce 192.168.10.42/24 from explicit inputs rather than a rough estimate.
- You want to test divide /24 into four equal children without carrying an assumption over silently from the first case.
- You need to reconcile the ip addressing result with “total addresses = 2^(32 − prefix length)” before using it.
Calculate ip addressing with ipv4 block capacity
Write the address as 32 bits and set the first p mask bits to one. Bitwise AND of the address and mask produces the network. The block spans that network through network + total − 1.
RFC 4632 documents CIDR prefix notation and address aggregation. CIDR arithmetic describes blocks; assignment, routing, reserved ranges, security zones and organizational policy remain separate.[1]
Validate the ip addressing result before using it
The network address must be divisible by block size in the 32-bit integer representation. The inclusive range count—last minus first plus one—must equal 2^(32−p).
Convert the mask back to binary and verify it contains one contiguous run of prefix ones followed by zeros. A noncontiguous dotted mask is not represented by ordinary CIDR notation.
Mistakes that produce a convincing but wrong answer
Typical errors include reading /24 as 24 host bits, subtracting two from /31 or /32 without considering context, starting the range at the entered host instead of the network, and crossing an octet boundary incorrectly.
A large numerical block does not mean every address is available to a workload. Provider reservations, protocol uses and local allocation plans must be applied separately.
What the calculation cannot decide
This calculator performs IPv4 block arithmetic only. It does not validate ownership, public reachability, DHCP configuration, firewall policy or route authorization.
Use current network architecture and applicable standards before deployment; example usable-host conventions are labels, not universal assignment policy.[1]
Worked case: 192.168.10.42/24
Address is 192.168.10.42 with prefix length 24.
Host bits = 8, so total = 2^8 = 256. Mask is 255.255.255.0; network is 192.168.10.0 and final address is 192.168.10.255.
Traditional host range is 192.168.10.1–192.168.10.254, or 254 addresses under that convention.
The entered .42 identifies a host inside the block; it is not the block start.[1]
Reproduce this worked caseOpen IPv4 Subnet Calculator
Worked case: divide /24 into four equal children
A /24 block must be divided into at least four equal subnets.
Four needs two added prefix bits, producing /26. Each /26 contains 2^(32−26) = 64 addresses.
The /24 provides four equal /26 children.
Real allocation may need uneven VLSM blocks; equal subdivision is only this scenario.[1]
Reproduce this worked caseOpen IPv4 Subnet Calculator
Compare scenarios without changing the question
The “Common IPv4 prefix capacities” comparison changes a declared driver while retaining the ipv4 block capacity basis. Read the rows with the stated inputs and units so the difference can be attributed to the changed condition instead of to an unnoticed denominator or convention change.
The total column follows pure address arithmetic; the usable column adds an operational convention.
| Prefix | Host bits | Total addresses | Traditional usable-host example |
|---|---|---|---|
| /24 | 8 | 256 | 254 |
| /26 | 6 | 64 | 62 |
| /30 | 2 | 4 | 2 |
| /31 | 1 | 2 | context-dependent, not automatically 0 |
Prepare a reliable input record for IPv4 Subnet Calculator
Before opening the IPv4 Subnet Calculator, create a compact input ledger. For every value, record its quantity, unit, period or reference date, where it came from, and whether it is measured, quoted, estimated or deliberately chosen. The governing relationship is “total addresses = 2^(32 − prefix length)”, so each symbol and number must belong to that same basis. This preparation prevents a polished calculator output from concealing mixed units, duplicate costs, incompatible periods or an assumption that was mistaken for an observation.
Copy the source value at its available precision and postpone rounding until the displayed result needs it. If an input is uncertain, do not replace it with a silent average: enter a named base case and preserve a defensible low and high case for later comparison. Give each scenario a short label so screenshots, exported notes and later recalculations can be matched to the correct assumptions without relying on memory. The IPv4 Subnet Calculator uses the values supplied to it; it does not retrieve a missing price, measurement, policy, route, tariff, scientific constant or professional decision unless the calculator explicitly says that it does.
Test how the ip addressing result changes
Reproduce “Worked case: 192.168.10.42/24” first and check every intermediate step against the written calculation. Then replace the example with your own input ledger without changing the equation or unit convention. Next reproduce “Worked case: divide /24 into four equal children” as a genuinely different use case. Working through both cases matters because a formula that appears obvious in one direction can expose a denominator, rounding, calendar, sign or allocation error when the scenario changes.
Use the IPv4 Subnet Calculator comparison table as a sensitivity test, not as decoration. Keep the calculation question fixed, change one material driver, and write the resulting difference in both absolute and relative terms when both are meaningful. If several inputs are uncertain, change them one at a time before combining them into a stress case. That sequence shows which assumption drives the answer and avoids attributing a multi-input change to the wrong cause.
Reconcile the ip addressing answer independently
A calculator result should survive a reverse or component check. Rebuild the answer from the displayed intermediate values, substitute the result back into “total addresses = 2^(32 − prefix length)”, and confirm that totals, shares, ranges or endpoints return to the entered record apart from final display rounding. Where the result involves whole packages, dates, route segments, rubric weights or billing tiers, reconcile the continuous calculation before applying the real-world rounding or boundary rule.
Keep the limitation beside the number rather than in a forgotten note. In this guide, the central boundary is: This calculator performs IPv4 block arithmetic only. It does not validate ownership, public reachability, DHCP configuration, firewall policy or route authorization. A result can be numerically correct while remaining unsuitable for a decision because the source data is stale, the model omits a material condition, or the required legal, safety, clinical, engineering, academic or provider rule was never entered. Record that unresolved condition explicitly instead of treating extra decimal places as confidence.
Save and update a reproducible ip addressing scenario
Save the calculation date, the IPv4 Subnet Calculator name, equation, complete input ledger, intermediate outputs, final result and rounding convention together. Also retain the reviewed reference “IETF — RFC 4632 Classless Inter-domain Routing” and the source or document used for every real-world input. This creates a small audit trail that another reader can reproduce without guessing which price, measurement, time zone, grading policy, physical model or operating condition supported the headline answer.[1]
Recalculate when a material input or governing rule changes; editing the old headline alone breaks the audit trail. Use IPv4 Address Count Calculator and VLSM Subnet Planner for the adjacent questions they are designed to answer, while keeping the IPv4 Subnet Calculator as the canonical workflow for this article. Separate calculator records make changes easier to trace and prevent one oversized worksheet from mixing calculations with different denominators, time bases or decision boundaries.
A practical audit checklist
- Prefix is 0–32
- Network aligned to block
- Inclusive range count checked
- Usable convention named
- Routing and reservations reviewed separately
Practical questions
Frequently asked questions
Does /24 mean 24 usable addresses?
No. It means 24 network-prefix bits, leaving eight address bits and 256 total addresses.
Why not always subtract two?
Network uses such as point-to-point /31 links and single-address /32 routes require different interpretation.
Does the calculator assign the subnet?
No. It only computes address-block arithmetic.
Further reading
Authoritative sources
Use these primary and professional resources to check definitions, conventions, or requirements that may extend beyond this guide.