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.
Buena señal Wi-Fi pero poca velocidad: qué comprobar
Diagnostica poca velocidad pese a buen RSSI revisando airtime, reintentos, ancho de canal, interferencias, cliente y backhaul.
01
RSSI es solo una parte de la capacidad
Un cliente a -50 dBm puede ir lento si el airtime está saturado, hay muchos reintentos, el AP comparte mal un canal ancho o el cliente negocia un PHY conservador. Señal fuerte responde “¿oigo al AP?”, no “¿con qué eficiencia intercambiamos tramas?”.
02
Mira reintentos, airtime y utilización de canal
Una tasa alta de reintentos apunta a colisiones, interferencia, nodos ocultos o modulación inestable. Mucha utilización con poco throughput suele indicar medio ocupado y no necesariamente backhaul lento. Compara estos contadores en la hora real de carga.
03
Valida capacidad del cliente y ancho negociado
Un AP moderno no puede obligar a un cliente antiguo o ahorrador de energía a usar más streams, mejor modulación o más ancho. Revisa radio del cliente, banda, ancho, MCS/NSS y driver antes de culpar al AP.
04
No olvides backhaul y shaping aguas arriba
Un enlace RF perfecto puede terminar en un puerto Ethernet de 100 Mbps, un mesh congestionado, una VLAN limitada o un gateway saturado. Mide throughput dentro de la LAN además de Internet para localizar el cuello.
05
Separa tasa PHY de throughput de aplicación
La tasa PHY negociada incluye codificación, contención y overhead; el throughput de aplicación siempre será menor. Compara magnitudes equivalentes y no uses la tasa anunciada como objetivo directo de speed-test.
06
Comprueba nodos ocultos e interferencia adyacente
Dos clientes que no se oyen entre sí pueden colisionar repetidamente en el AP. La interferencia de canal adyacente es distinta de la contención co-canal y puede ser especialmente dañina con planes parcialmente solapados.
07
Prueba un cliente cerca de un AP antes de ajustar toda la red
Una línea base controlada elimina roaming, distancia y celdas vecinas. Si esa prueba ya es mala, corrige AP/backhaul; si es buena, amplía el test hacia fuera.
EX
Ejemplo trabajado
- Coloca un cliente capaz cerca del AP y mide throughput LAN.
- Registra RSSI, PHY/MCS, utilización y reintentos al mismo tiempo.
- Repite bajo carga y compara latencia con reposo.
- Mueve el mismo cliente a la zona problemática e identifica qué métrica cambia primero.
✓
Checklist operativo
- Comprueba utilización y reintentos.
- Confirma banda, ancho, MCS y streams del cliente.
- Verifica velocidad del backhaul Ethernet o mesh.
- Compara latencia en reposo y bajo carga.
- Repite tras cada cambio aislado.
Herramientas para ponerlo en práctica
Estándares y referencias
🕐 History