user@netcalc ~/calc $
ipv4_calculator
Calculate network, broadcast, mask, hosts, class and binary for any IPv4 address
ip:
mask:
✓ stdout — ipv4_calculator
Enter runs the calculation · Shift+Enter inserts a new line
user@netcalc ~/calc $
ipv6_calculator
Calculate network info for IPv6 addresses in CIDR notation
ipv6:
pfx:
✓ stdout — ipv6_calculator
user@netcalc ~/calc $
vlsm_calculator
Variable Length Subnet Mask — assigns optimal blocks for each network segment
net:
pfx:
// Subnets required
name:
hosts:
name:
hosts:
name:
hosts:
✓ stdout — vlsm_calculator
| # | Name | Hosts Req | Hosts Avail | Prefix | Network | First Host | Last Host | Broadcast | Mask |
|---|
user@netcalc ~/calc $
usable_ip_range
Shows the exact usable host range for a given network
ip:
mask:
✓ stdout — usable_ip_range
user@netcalc ~/calc $
binary_ip_calc
Convert IP addresses to binary and vice versa, with per-octet visualization
dec:
bin:
✓ stdout — binary_ip_calc
user@netcalc ~/network $
cidr_converter
Convert between CIDR, decimal mask and wildcard. Includes full /1–/32 reference table.
in:
✓ stdout — cidr_converter
📋 CIDR Reference Table
| CIDR | Subnet Mask | Wildcard | Hosts | /24 subnets | Block |
|---|
user@netcalc ~/network $
wildcard_mask_calc
Calculate the wildcard (inverse) mask for Cisco ACLs, OSPF and firewall rules
mask:
✓ stdout — wildcard_mask_calc
user@netcalc ~/network $
supernet_calculator
Find the minimum supernet containing all specified networks (route summarization)
nets:
✓ stdout — supernet_calculator
user@netcalc ~/network $
subnet_splitter
Split a network into equal subnets by specifying a new prefix
net:
mask:
new:
✓ stdout — subnet_splitter
| # | Network | First Host | Last Host | Broadcast | Hosts | Mask |
|---|
user@netcalc ~/network $
range_to_cidr
Convert an IP range (start–end) to the minimum set of CIDR blocks
start:
end:
✓ stdout — range_to_cidr
| # | CIDR Block | Network | Broadcast | Hosts |
|---|
user@netcalc ~/network $
ip_to_integer
Convert IPv4/IPv6 addresses to integer and vice versa
ip:
int:
✓ stdout — ip_to_integer
user@netcalc ~/network $
ipv6_normalize
Expand and compress IPv6 addresses — normalize any valid format
ipv6:
✓ stdout — ipv6_normalize
user@netcalc ~/network $
hex_ip_converter
Convert between hexadecimal and IP address — useful for Windows route tables and Cisco logs
ip:
0x:
✓ stdout — hex_ip_converter
user@netcalc ~/network $
vlan_calculator
802.1Q VLAN info: tag encoding, PCP, DEI, VID, range and compatibility
vlan:
pcp:
dei:
✓ stdout — vlan_calculator
user@netcalc ~/dns $
reverse_dns_generator
Generate the PTR in-addr.arpa zone for an IPv4 network
net:
pfx:
dom:
✓ stdout — reverse_dns_generator
user@netcalc ~/dns $
ipv6_ptr_generator
Generate the PTR ip6.arpa record for an IPv6 address
ipv6:
host:
✓ stdout — ipv6_ptr_generator
user@netcalc ~/dns $
ip_geolocation
Locate a public IP or resolve a domain and geolocate its public address
Domains are resolved through DNS first; geolocation is based on the resulting public IP.
geo:
✓ stdout — ip_geolocation
user@netcalc ~/dns $
ip_address_planner
Interactive IP address space planner — click cells to edit, export to CSV
📋 IP Address Plan
| # | Name | Network | Mask/CIDR | Gateway | VLAN | Location | Notes |
|---|
user@netcalc ~/legal $
Privacy
Data stored in your browser
Theme, language, promotion dismissal and calculation history are stored in localStorage on this device.
Calculations
Calculations are sent through this site's same-origin Worker proxy to the private calculation service.
Performance metrics
LCP, CLS and INP may be stored as aggregate performance measurements by tool and language. Calculation inputs and persistent user identifiers are not included.
GeoIP
Only GeoIP lookups are processed by an external provider. The requested IP address is sent for that lookup.
Issue reports via Telegram
A report link opens the public Telegram bot and includes only the current page slug in the bot start parameter. Calculator inputs and report text are not sent by this website. Text you choose to send inside Telegram is handled by Telegram and the bot.
Cookies and advertising
Advertising is controlled by the production configuration. When Google AdSense is enabled, consent is handled through a certified CMP before personalized advertising is used where required.
Delete local data
Use the button below to clear calculation history. To remove every local preference, clear this site's data in your browser settings.
This page provides operational information; it is not a legal-compliance certification.
How to choose Wi-Fi channels in 2.4, 5 and 6 GHz
Compare channel width, overlap, DFS and PSC considerations when planning modern Wi-Fi networks.
01
2.4 GHz is mainly an overlap problem
The 2.4 GHz band offers few practical non-overlapping 20 MHz choices. Wider channels consume a large part of the band and can increase contention, so dense deployments usually benefit from conservative channel width and coordinated reuse.
02
5 GHz adds spectrum and DFS decisions
5 GHz provides many more channels, but some are subject to Dynamic Frequency Selection depending on regulatory domain. DFS can improve spectrum reuse while also introducing channel changes when radar is detected.
03
6 GHz changes the planning model again
6 GHz offers much more clean spectrum for modern clients and introduces Preferred Scanning Channels to help discovery. Availability, allowed power and channel width still depend on country rules and device capability.
04
Measure the environment, do not only pick numbers
A channel plan should be validated with actual utilization, interference and client capabilities. The “best” channel on paper can perform worse than a busier-looking channel if neighboring APs cooperate better or interference is non-Wi-Fi.
05
Channel width is a capacity-versus-reuse decision
Moving from 20 to 40, 80 or 160 MHz can raise peak PHY rates but consumes more spectrum and reduces the number of independent cells. In dense environments a narrower channel can deliver more total network capacity because more APs can reuse spectrum without overlapping.
06
Regulatory domain and transmit power belong in the plan
A channel that exists in a standards table may not be legal or equivalent everywhere. DFS requirements, indoor-only rules, AFC availability and maximum EIRP depend on country and device class. Configure the correct regulatory domain before treating a channel plan as valid.
07
Validate roaming and airtime, not just RSSI
Good coverage is not only strong signal. Check channel utilization, retry rate, client distribution, minimum basic rates and roaming behavior. A network with very high RSSI can still perform poorly if clients remain attached too long or airtime is dominated by slow stations.
EX
Worked example
- For 2.4 GHz, begin with 20 MHz cells and a coordinated reuse pattern rather than automatic wide channels.
- For 5 GHz, map non-DFS and DFS groups and decide whether radar-triggered channel moves are acceptable for each AP role.
- For 6 GHz, verify client support and use PSC-aware planning so discovery remains efficient.
- After deployment, compare the paper plan with utilization, retries and roaming traces during real busy periods.
✓
Operational checklist
- Set the correct regulatory domain first.
- Prefer narrower channels in dense deployments unless measurements justify width.
- Measure airtime, retries and neighboring APs on site.
- Revisit the plan after client mix or AP density changes.
Tools to apply it
Standards and references
🕐 History