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.
Diagnóstico de trunks VLAN: tagged, untagged y errores de VLAN nativa
Sigue la pertenencia VLAN extremo a extremo e identifica desajustes de PVID, VLAN nativa y listas permitidas que provocan conectividad parcial o intermitente.
01
Sigue una VLAN de extremo a extremo
Empieza por el puerto de acceso y continúa por cada trunk, bridge e interfaz virtual. Anota si cada salto espera la VLAN tagged o untagged. Un único desacuerdo puede aislar un servicio mientras otros siguen funcionando.
02
PVID y VLAN nativa clasifican entrada, no hacen magia
Una trama sin tag que entra por un puerto se asigna a una VLAN según sus reglas de ingreso. Esa misma VLAN puede salir por otro puerto con tag o sin él. Trata clasificación de entrada y etiquetado de salida como decisiones separadas.
03
Las listas allowed producen fallos parciales
Un trunk puede transportar gestión y voz correctamente y descartar una nueva VLAN de clientes porque falta en una lista permitida de un lado. Compara ambos extremos e intermedios aunque parte del trunk funcione.
04
Evita depender de VLAN nativa mal alineada
Los fabricantes nombran native, PVID, untagged e hybrid de forma distinta. Construye una matriz explícita de tagging por enlace y verifícala con aprendizaje MAC o captura en lugar de traducir comandos solo por nombre.
05
Usa aprendizaje MAC como tracer de capa 2
Una MAC origen debe aparecer en la VLAN esperada en cada switch del camino. Si desaparece o cambia de VLAN en un salto, has localizado el desajuste de tagging o PVID.
06
Recuerda que gestión y clientes pueden usar VLAN distintas
Poder gestionar ambos switches solo demuestra alcance IP en la VLAN de gestión. No demuestra que la VLAN de cliente esté presente en la allow-list del trunk.
07
Documenta trunks como una matriz
Para cada enlace anota VLAN permitidas y si cada una sale tagged o untagged. Esta descripción neutral traduce mejor entre MikroTik, Cisco, Huawei y smart switches que los nombres específicos del fabricante.
EX
Ejemplo trabajado
- Host A entra untagged en VLAN 40 en Switch 1.
- El uplink debe transportar VLAN 40 con la misma expectativa de tag en ambos switches.
- Switch 2 entrega VLAN 40 untagged al puerto de destino.
- Si la MAC desaparece en el trunk, compara VLAN allowed y PVID/native en ambos extremos.
✓
Checklist operativo
- Escribe la matriz VLAN/tagging de cada trunk.
- Compara listas allowed en ambos extremos.
- Verifica PVID/VLAN nativa para entrada untagged.
- Usa MAC learning o captura para demostrar el salto que falla.
Herramientas para ponerlo en práctica
Estándares y referencias
🕐 History