SubnetLab & Networking Infrastructure
Comprehensive interactive guide covering fundamental IP addressing, binary operations, CIDR, VLSM, VLANs, routing protocols, packet inspection, wireless networks, and network security.
Mastering Subnets
From binary bitwise operations and CIDR calculations to VLSM, VLAN isolation, cloud VPC design, and firewall rules — master IP networking through interactive visualisations and real-time drills.
1. What is a Subnet?
A Subnet (Subnetwork) is a logical subdivision of an IP network. By partitioning a large network into smaller, isolated sub-networks, organization network administrators minimize broadcast noise, enhance security isolation, and optimize Layer 3 routing efficiency across local and cloud environments.
Performance & Traffic Control
Subnetting constrains Layer 2 broadcast domains. Without subnets, broadcast frames (ARP, DHCP) flood every host on the switch, causing broadcast storms and high network latency.
Enhanced Security Isolation
Enforces Zero-Trust boundary controls between host groups. Isolates sensitive infrastructure (Database, Payment Gateways, Admin) from public-facing web servers and Guest Wi-Fi.
Logical Addressing & Scale
Enables structured IP Address Management (IPAM). Facilitates route summarization, simplified troubleshooting, and scalable allocation across physical buildings or cloud Availability Zones.
Network Topology Example: 192.168.1.0/24 Subnet Partitioning
A single Class C block divided into 3 distinct functional subnets with a central Layer 3 Gateway Router.
Management & Admin
Staff Workstations
IoT & Guest Wi-Fi
2. IP Addresses & Binary
Every IPv4 address is a 32-bit binary number represented in 4 decimal octets separated by dots. Understanding bit values, positional binary weights ($128, 64, 32, 16, 8, 4, 2, 1$), and bitwise operations is fundamental to networking.
Live 4-Octet Decimal to Binary Converter
Enter values from 0 to 255 for each octet to visualize their 8-bit binary representation in real time.
IPv4 Address Anatomy: Network ID vs Host ID
Every IP address is divided into two logical sections by its subnet mask: the Network Portion (Prefix) which identifies the specific network, and the Host Portion (Suffix) which identifies the unique device interface on that network.
RFC 1918 Private IP Address Ranges
RFC 1918 designates three IP address ranges reserved exclusively for private internal networks. These IPs are non-routable on the public internet.
| Class | CIDR Block | IP Address Range | Total Addresses | Typical Application |
|---|---|---|---|---|
| Class A | 10.0.0.0 / 8 | 10.0.0.0 — 10.255.255.255 | 16,777,216 | Enterprise corporate networks, cloud VPCs |
| Class B | 172.16.0.0 / 12 | 172.16.0.0 — 172.31.255.255 | 1,048,576 | Medium corporate LANs, Docker internal bridges |
| Class C | 192.168.0.0 / 16 | 192.168.0.0 — 192.168.255.255 | 65,536 | Home routers, SOHO local networks, Wi-Fi hotspots |
Classful vs CIDR Addressing
Historical Classful routing forced rigid network boundaries, leading to rapid IP address exhaustion. CIDR (Classless Inter-Domain Routing) introduced variable-length prefix masks.
| Feature | Legacy Classful (RFC 791) | Modern CIDR (RFC 1519) |
|---|---|---|
| Mask Allocation | Fixed octet boundaries (/8, /16, /24) | Arbitrary bit boundaries (/1 to /32) |
| Routing Protocol Support | RIPv1, IGRP (No subnet mask sent in updates) | OSPF, BGP4, RIPv2, IS-IS (Subnet mask explicitly sent) |
| IP Utilization Efficiency | Very Poor (Extreme address wastage) | High (Optimal subnet sizing via VLSM) |
| Route Table Aggregation | Impossible (Unaggregated full routing tables) | Supernetting & BGP Prefix Aggregation enabled |
Loopback Address Space
Reserved for host-internal network stack testing (127.0.0.1 / localhost). Traffic sent to loopback never hits physical network interfaces or switch ports.
APIPA (Link-Local)
Automatic Private IP Addressing (RFC 3927). Self-assigned by operating systems when a DHCP server fails to respond. Non-routable across routers.
Bitwise AND Operation: Calculating Network Address
When a router evaluates an incoming packet, it performs a bitwise AND operation between the Destination IP Address and the Subnet Mask to determine the target Network Address.
3. CIDR & Subnet Masks — Interactive
CIDR (Classless Inter-Domain Routing) specifies how many leading bits in an IP address represent the network prefix. Adjust the slider or click any bit box below to interactively observe how changing prefix length affects subnet mask, bit allocation, total addresses, and usable host count.
Subnet Mask Bit Allocator
Selected Prefix: /24 (24 Network Bits, 8 Host Bits)
Usable Hosts Calculation Formula: $2^h - 2$
To calculate the number of hosts that can be assigned to devices on a IPv4 subnet, use the formula Usable Hosts = 2^h - 2, where h = 32 - CIDR is the number of remaining host bits.
4. VLSM — Variable Length Subnet Masking
Variable Length Subnet Masking (VLSM) allows network engineers to subdivide an IP address space into non-uniform subnets tailored to exact host requirements. Instead of assigning a fixed mask (like `/24`) everywhere, VLSM prevents IP address exhaustion by assigning larger masks (e.g., `/26`, `/27`, `/30`) where fewer hosts reside.
Point-to-Point Router Links
Provides exactly 4 total IP addresses ($2^2$), yielding 2 usable hosts. Ideal for point-to-point links between two core routers, eliminating address wastage.
Branch & Small Departments
Provides 32 total IP addresses ($2^5$), yielding 30 usable hosts. Perfect for small department teams, remote office locations, or server racks.
Standard Building / LAN
Provides 256 total IP addresses ($2^8$), yielding 254 usable hosts. Standard default allocation size for corporate office floors and DHCP user pools.
Worked VLSM Example: Subnetting a 192.168.1.0/24 Block
Requirement: Allocate subnets for Engineering (50 hosts), Sales (25 hosts), Executive (10 hosts), and 2 Router Links.
| Department | Needed Hosts | Allocated CIDR | Subnet Mask | Network Address | Usable Host Range | Broadcast Address |
|---|---|---|---|---|---|---|
| Engineering | 50 hosts | /26 (64 IPs) | 255.255.255.192 | 192.168.1.0 | 192.168.1.1 — 192.168.1.62 | 192.168.1.63 |
| Sales | 25 hosts | /27 (32 IPs) | 255.255.255.224 | 192.168.1.64 | 192.168.1.65 — 192.168.1.94 | 192.168.1.95 |
| Executive | 10 hosts | /28 (16 IPs) | 255.255.255.240 | 192.168.1.96 | 192.168.1.97 — 192.168.1.110 | 192.168.1.111 |
| Router Link 1 | 2 hosts | /30 (4 IPs) | 255.255.255.252 | 192.168.1.112 | 192.168.1.113 — 192.168.1.114 | 192.168.1.115 |
| Router Link 2 | 2 hosts | /30 (4 IPs) | 255.255.255.252 | 192.168.1.116 | 192.168.1.117 — 192.168.1.118 | 192.168.1.119 |
| Unassigned Pool | Future expansion | 136 IPs free | Various | 192.168.1.120 | 192.168.1.120 — 192.168.1.255 | 192.168.1.255 |
192.168.1.0/24 (256 Total IPs) ├── 192.168.1.0/26 [Engineering: 50 hosts required, 62 usable (.1-.62)] ├── 192.168.1.64/27 [Sales: 25 hosts required, 30 usable (.65-.94)] ├── 192.168.1.96/28 [Executive: 10 hosts required, 14 usable (.97-.110)] ├── 192.168.1.112/30 [Router Link 1: 2 hosts required, 2 usable (.113-.114)] ├── 192.168.1.116/30 [Router Link 2: 2 hosts required, 2 usable (.117-.118)] └── 192.168.1.120/24 [Reserved Future Allocation Pool: 136 IPs remaining]
/31 Subnet Prefixes on Point-to-Point Links
Under standard IPv4 rules, a /30 subnet uses 4 addresses to supply only 2 usable host IPs (a 50% loss due to dedicated network and broadcast IPs). RFC 3021 eliminates this waste by allowing /31 prefix masks on point-to-point links.
5. VLANs & Subnets — How They Connect
While both VLANs (Virtual LANs) and Subnets isolate network traffic, they operate at different layers of the OSI model. Understanding how Layer 2 physical switch isolation pairs with Layer 3 IP addressing is essential for modern enterprise network design.
VLAN (Virtual Local Area Network)
Partitioning at the physical switch level. Inserts a 4-byte 802.1Q tag into Ethernet frame headers to divide a single switch into multiple virtual broadcast domains.
IP Subnet (Subnetwork)
Logical IP address grouping defined by subnet masks (e.g., 255.255.255.0). Determines whether a packet stays local or must be routed through a gateway.
Industry Standard: 1:1 Mapping & Inter-VLAN Routing
Best practice dictates mapping exactly one IP Subnet to one VLAN. Communication between VLANs requires a Layer 3 Router or L3 Switch.
Access Ports (End Devices)
Switch ports configured as Access Ports belong to a single native VLAN. They send and receive standard untagged Ethernet frames directly to workstations, printers, and IP phones.
Trunk Ports (IEEE 802.1Q Inter-Switch Links)
Switch ports configured as Trunk Ports multiplex traffic from multiple VLANs over a single physical link by appending a 4-byte 802.1Q VLAN ID tag to each Ethernet frame header.
6. IPv6 — The Next Generation
IPv6 replaces IPv4's 32-bit address space with a massive 128-bit address space ($3.4 \times 10^38$ total addresses). Designed to eliminate NAT workarounds, IPv6 provides end-to-end global connectivity, built-in IPsec security, stateless auto-configuration (SLAAC), and simplified router headers.
IPv6 Address Anatomy: 8 Hextets (128 Bits)
Written as 8 groups of 4 hexadecimal digits (called hextets), separated by colons. Each hextet represents 16 bits ($8 \times 16 = 128$ bits).
Zero Compression Rules
To make long IPv6 addresses human-readable, RFC 5952 establishes two mandatory compression rules.
In any hextet, leading zeros can be dropped. For example, 0db8 becomes db8, and 0000 becomes 0.
A single contiguous sequence of all-zero hextets can be replaced with ::.Critical Constraint: :: can only be used ONCE per address to prevent ambiguity when parsing.
IPv4 vs IPv6 Feature Matrix
Architectural comparison between legacy IPv4 protocols and modern IPv6 standards.
| Feature | IPv4 Standard | IPv6 Standard |
|---|---|---|
| Address Size | 32 Bits (4 Bytes) | 128 Bits (16 Bytes) |
| Total Address Count | ~4.3 Billion ($4.3 \times 10^9$) | ~340 Undecillion ($3.4 \times 10^38$) |
| Format Notation | Dotted Decimal (e.g. 192.168.1.1) | Hexadecimal Colons (e.g. 2001:db8::1) |
| Standard Subnet Mask | Variable Prefixes (/8 to /32) | Standard /64 Interface Prefix |
| Address Auto-Configuration | Stateful DHCP required | Stateless SLAAC & Stateful DHCPv6 |
| NAT Requirement | Mandatory (address space exhaustion) | Obsolete (Every host receives public IP) |
The Universal IPv6 /64 Subnet Prefix
Unlike IPv4 where subnets vary in size, the standard subnet size in IPv6 is almost universally /64. This leaves 64 bits for the Interface ID, allowing SLAAC (Stateless Address Autoconfiguration) to automatically generate unique host addresses.
7. Public vs Private IPs & NAT
IP addresses are split into globally routable Public IPs and localized Private IPs. Because IPv4 addresses are scarce, Network Address Translation (NAT) allows hundreds of devices on a private LAN to share a single public IP address when communicating over the internet.
Internet-Facing Infrastructure
Globally unique addresses assigned by ICANN/IANA through Regional Internet Registries (ARIN, RIPE, APNIC) and ISPs. Directly accessible over the public internet.
Internal LAN & Cloud VPCs
Reserved for internal use inside homes, offices, and cloud VPC networks. ISP routers automatically drop private IP packets attempting to cross the public internet.
Interactive NAT / PAT (Port Address Translation) Flow
Step-by-step walkthrough showing how a NAT Gateway translates private sockets to public sockets.
Outbound Request Sent by Private Host
Client (192.168.1.50) sends a packet to Web Server (93.184.216.34:80) via ephemeral port 51234.
8. Subnet Calculator
Enter an IPv4 address and select a CIDR prefix length to calculate network boundaries, broadcast addresses, usable host ranges, and subnet masks in real time.
Common Subnet Quick Reference
| CIDR | Subnet Mask | Usable Hosts | Typical Use |
|---|---|---|---|
| /16 | 255.255.0.0 | 65,534 | Large Enterprise / Cloud VPC |
| /24 | 255.255.255.0 | 254 | Standard Local Subnet (LAN / Office) |
| /25 | 255.255.255.128 | 126 | Medium Department (100+ devices) |
| /26 | 255.255.255.192 | 62 | Small Department / Server Rack |
| /27 | 255.255.255.224 | 30 | Branch Office / Small Workgroup |
| /28 | 255.255.255.240 | 14 | Management Network / DMZ Subnet |
| /30 | 255.255.255.252 | 2 | Point-to-Point Router Link |
9. Creating Subnets on Your Local Network
Building custom subnets on a local area network requires methodical planning and accurate configuration across your gateway router, managed switches, and endpoint operating systems. Follow this 4-step workflow to partition and verify your subnets.
Step 1: Plan Address Space & CIDR Blocks
Select a private RFC 1918 base network (e.g. 192.168.0.0/16) and divide it into subnets based on required host capacity and isolation goals.
.0 (Network), .1 (Default Gateway), and .255 (Broadcast).Step 2: Configure Router/Switch Gateways
Configure 802.1Q sub-interfaces on your router (Router-on-a-Stick) or SVIs on a Layer 3 switch to act as default gateways.
! Step 2: Configure Router Sub-Interfaces (Router-on-a-Stick) interface GigabitEthernet0/0.10 description LAN_Subnet_Staff encapsulation dot1Q 10 ip address 192.168.10.1 255.255.255.0 no shutdown ! interface GigabitEthernet0/0.20 description LAN_Subnet_Guest encapsulation dot1Q 20 ip address 192.168.20.1 255.255.255.0 no shutdown
Step 3: Assign IP Addresses to Host Interfaces
Configure static IP address parameters, netmasks, and default gateways directly on host machines via OS CLI tools.
# Assign Static IP & Netmask on Windows via Netsh netsh interface ip set address name="Ethernet" static 192.168.10.50 255.255.255.0 192.168.10.1 # Configure Primary DNS Server netsh interface ip set dns name="Ethernet" static 1.1.1.1
Step 4: Verify & Test Inter-Subnet Routing
Confirm local gateway reachability, test cross-subnet packet forwarding, and inspect hop pathways using standard diagnostic utilities.
# 1. Verify Gateway Reachability ping 192.168.10.1 # 2. Test Inter-Subnet Routing to Guest Subnet ping 192.168.20.50 # 3. Trace Route Path across Gateway (Windows / Linux) tracert 192.168.20.50 # Windows traceroute 192.168.20.50 # Linux / macOS
10. Supernetting & CIDR Aggregation
Supernetting (also called CIDR Route Aggregation or Route Summarization) is the process of combining multiple contiguous smaller networks into a single, shorter-prefix network route. This dramatically reduces core routing table sizes and conserves memory on enterprise network backbones.
❌ Before Aggregation (4 Individual Routes)
Bloated Routing TableRouters must store, query, and advertise four separate routing table entries for adjacent subnets:
✅ After Aggregation (1 Supernet Route)
75% Table ReductionAll 4 subnets are consolidated into a single summary prefix with a shorter network mask:
192.168.0.0 to 192.168.3.255 (Total 1,024 IP addresses in 1 route entry).11. Subnets in the Cloud
Cloud hyperscalers (AWS, Azure, GCP) use Software-Defined Networking (SDN) to deliver virtual private clouds. While cloud subnets share traditional CIDR math, cloud vendors enforce vendor-specific IP reservations, availability zone scopes, and routing rules.
AWS VPC (Virtual Private Cloud)
Cloud SDN Subnet ArchitectureSubnets are strictly bound to a single Availability Zone (AZ).
5 Reserved IPs per subnet (.0 network, .1 VPC router, .2 AWS DNS, .3 reserved, .255 broadcast).
# AWS VPC & Subnet Terraform Example
resource "aws_vpc" "main" {
cidr_block = "10.0.0.0/16"
}
resource "aws_subnet" "public_az1" {
vpc_id = aws_vpc.main.id
cidr_block = "10.0.1.0/24"
availability_zone = "us-east-1a"
}📋 Cloud Subnetting Architecture Checklist & Tips
Plan for Future Scale & Non-overlapping Address Space
Always select large VPC CIDR blocks (/16) even when starting small. Never overlap VPC ranges with on-premise IP networks (10.x.x.x or 172.16.x.x) to enable seamless VPN/DirectConnect hybrid routing.
Enforce Strict Public vs. Private Subnet Separation
Place internet-facing load balancers in Public Subnets (attached to Internet Gateways) and application/database workloads in Private Subnets (routed via NAT Gateways for outbound access only).
Account for Cloud IP Reservations in Sizing Calculations
Remember AWS and Azure reserve 5 IP addresses per subnet (.0, .1, .2, .3, .255). A small /29 subnet provides only 3 usable host IPs instead of 6.
Deploy Multi-AZ Redundancy Across Availability Zones
Provision identical subnets across at least 2 or 3 Availability Zones (e.g. us-east-1a, us-east-1b) to ensure multi-AZ fault tolerance for enterprise workloads.
Isolate High-Security Subnets with Network ACLs (NACLs)
Combine Cloud Security Groups (stateful) with Network ACLs (stateless at the subnet boundary) to enforce explicit packet filtering between database and web subnets.
12. Firewall Rules Between Subnets
Subnetting divides physical networks into isolated broadcast domains, but routers forward traffic between subnets by default. Firewalls & Access Control Lists (ACLs) enforce Zero-Trust boundaries by inspecting and filtering packet headers at subnet gateways.
Default-DENY (Block)
Enforces Zero-Trust isolation. Inter-subnet traffic is implicitly or explicitly dropped unless an explicit permit rule allows it.
Granular PERMIT (Allow)
Allows specific protocol, source CIDR, destination CIDR, and port combinations (e.g. Web Subnet to DB Subnet on TCP 5432).
Stateful Audit & LOG
Captures dropped connection attempts, port scans, and unauthorized inter-subnet packets to SIEM monitoring tools for incident analysis.
Cisco IOS Inter-Subnet Access Control List (ACL 100)
Extended ACL LogicExtended ACLs filter based on source/destination IPs and TCP/UDP ports. Apply inbound on the router sub-interface closest to the source:
! Cisco Extended Access Control List (ACL 100) ! 1. Allow Web Subnet (VLAN 10) to access Database Subnet (VLAN 20) on PostgreSQL port 5432 access-list 100 remark --- Permit Web to DB Postgres --- access-list 100 permit tcp 192.168.10.0 0.0.0.255 192.168.20.0 0.0.0.255 eq 5432 ! 2. Allow Web Subnet (VLAN 10) to access Shared HTTPS Services (VLAN 30) access-list 100 remark --- Permit Web to Shared HTTPS --- access-list 100 permit tcp 192.168.10.0 0.0.0.255 192.168.30.0 0.0.0.255 eq 443 ! 3. Explicitly DENY all remaining inter-subnet traffic & log violation attempts access-list 100 remark --- Deny & Log all other cross-subnet packets --- access-list 100 deny ip 192.168.10.0 0.0.0.255 192.168.20.0 0.0.0.255 log ! 4. Apply ACL inbound on VLAN 10 Interface interface GigabitEthernet0/0.10 ip access-group 100 in
🛡️ Home & Small Network Firewall Rule Best Practices
Isolate Guest Wi-Fi Subnet Completely
Enable 'Guest Network Isolation' on your Wi-Fi router so guests (e.g. 192.168.2.0/24) cannot scan or connect to private NAS drives, PCs, or printers on 192.168.1.0/24.
Segregate Smart Home IoT Devices into a Dedicated VLAN
Place smart TVs, cameras, smart plugs, and voice assistants on an isolated IoT subnet (e.g. 192.168.50.0/24). Block inbound requests from the IoT subnet to your main LAN.
Disable UPnP Across Inter-Subnet Boundaries
Universal Plug and Play (UPnP) should be strictly disabled between subnets to prevent malicious IoT software from dynamically requesting open router port forwards.
Utilize Stateful Firewall Engines (pfSense / OPNsense / UniFi)
Deploy stateful firewall rules that automatically permit return traffic for outbound requests initiated by trusted LAN hosts without opening static inbound ports.
13. Troubleshooting Subnet Issues
Subnetting issues can lead to subtle network failures, including host isolation, asymmetric routing, IP conflicts, and cross-subnet packet drops. Master these 6 diagnostic scenarios and follow the 6-step troubleshooting workflow.
6 Common Subnet Misconfigurations & Solutions
1. Misconfigured Subnet Mask (Off-by-One CIDR)
Mask MismatchHost A (192.168.1.50/24) cannot reach Host B (192.168.1.200/25). Host B incorrectly treats Host A as external and sends packets to Gateway.
Verify netmask uniformity across all hosts in the subnet block.
# Windows: Inspect IPv4 Subnet Mask ipconfig /all # Linux: Verify assigned IP & Prefix length ip -4 addr show dev eth0
🩺 6-Step Subnet Diagnostic Workflow
ipconfig /all | ip addrVerify Local IP Address & Subnet Mask
Ensure host has a valid IP address (not 0.0.0.0 or APIPA 169.254.x.x) and correct netmask matching network plan.
ping 127.0.0.1Test Local Loopback & Interface
Ping 127.0.0.1 and local host IP to verify local TCP/IP protocol stack and NIC driver functionality.
ping 192.168.10.1Ping Default Gateway IP
Test ICMP reachability to local subnet router interface (e.g. 192.168.10.1) to confirm Layer 2 switch connectivity.
tracert 192.168.20.50Trace Route Path to Target Destination
Execute traceroute to locate exact router hop where inter-subnet packet forwarding fails or times out.
nslookup domain.com | nc -zv IP PORTTest DNS & Targeted TCP/UDP Ports
Verify whether issue is pure IP layer routing or higher-layer DNS resolution / firewall port blocking.
show vlan brief | show access-listsAudit Switch VLANs & Firewall ACL Rules
Check switchport VLAN assignments, 802.1Q trunk tags, stateful firewall rules, and router ACL drop counters.
14. Practice Problems
Master subnetting with real-world scenarios and certification-style drill questions. Test your calculations for network boundaries, host ranges, broadcast addresses, and VLSM allocations, then toggle answers to verify your steps.
Problem 1: Basic Subnetting
You are given the network address 172.16.5.0/24. Calculate the Network ID, Subnet Mask, First Usable Host IP, Last Usable Host IP, Broadcast Address, and Total Usable Hosts.
Problem 2: Subnet Division
Divide the network 10.1.1.0/24 into 4 equal subnets. Determine the new CIDR prefix length, Subnet Mask, Block Size, and list each created subnet with its Network ID, Usable Range, and Broadcast Address.
Problem 3: Find the Network
An engineer discovers a workstation configured with IP address 192.168.10.150/27. Determine the Network ID, Subnet Mask, First & Last Usable Host IPs, and Broadcast Address for the subnet block it belongs to. Is 192.168.10.150 a valid host address?
Problem 4: VLSM Challenge
Given the single base network block 192.168.1.0/24, design a Variable Length Subnet Masking (VLSM) allocation for three subnets: Finance (25 hosts needed), Marketing (12 hosts needed), and WAN Link (2 hosts needed). Order from largest to smallest requirement to avoid address overlap.
Problem 5: Real-World Scenario
A database server is assigned IP 10.0.5.100/28. A system administrator attempts to ping a default gateway at 10.0.5.113. Will this ping succeed directly on the local Layer 2 broadcast domain without passing through a router? Determine the exact subnet boundary for 10.0.5.100/28.
15. Subnetting Cheat Sheet
Quick-reference hub containing essential subnet formulas, comprehensive CIDR prefix lookup tables (/8 through /32), and mental math shortcuts for rapid network calculations in exams and production deployments.
📐Core Subnetting Formulas
Total IP Addresses
Calculates total raw IP addresses in block including network & broadcast.
Usable Host Count
Subtracts 2 for Network ID (first address) and Broadcast ID (last address).
Block Size (Magic Number)
Determines the exact step size between adjacent network boundaries.
Wildcard Mask (Inverse)
Used in Cisco Access Control Lists (ACLs) and OSPF network commands.
Network Address
Performs bitwise AND matching between IP address and subnet mask.
Broadcast Address
Last address in the subnet block where all host bits equal binary 1.
First Usable Host
First assignable IP address for network interfaces/endpoints.
Last Usable Host
Final assignable IP address before the broadcast boundary.
Subnets Created
Calculates total equal subnets created when extending network prefix.
📊Prefix Quick Reference Table (/8 to /32)
Complete CIDR lookup listing netmasks, host counts, magic numbers, and practical RFC use-cases.
RFC 3021 enables 2 usable IP addresses on point-to-point links with zero overhead (no reserved network or broadcast addresses), doubling IPv4 address efficiency on WAN links compared to traditional /30.
A /32 prefix represents a single host route (255.255.255.255). Used for router loopback interfaces (Router IDs in OSPF/BGP) and explicit single-IP host firewall rules.
| CIDR | Subnet Mask | Total IPs | Usable Hosts | Block Size (Increment) | Primary RFC / Production Use Case |
|---|---|---|---|---|---|
/8Class A | 255.0.0.0 | 16,777,216 | 16,777,214 | 256 (Octet 1) | Class A Default / Large Global Core Networks |
/9 | 255.128.0.0 | 8,388,608 | 8,388,606 | 128 (Octet 2) | Telco Backbones & Regional Supernets |
/10 | 255.192.0.0 | 4,194,304 | 4,194,302 | 64 (Octet 2) | Carrier-Grade NAT (CGNAT 100.64.0.0/10) |
/11 | 255.224.0.0 | 2,097,152 | 2,097,150 | 32 (Octet 2) | Large Enterprise Data Centers |
/12 | 255.240.0.0 | 1,048,576 | 1,048,574 | 16 (Octet 2) | Cloud VPC Private Allocations (RFC 1918 172.16.0.0/12) |
/13 | 255.248.0.0 | 524,288 | 524,286 | 8 (Octet 2) | Multi-Region Cloud Supernets |
/14 | 255.252.0.0 | 262,144 | 262,142 | 4 (Octet 2) | Large Service Provider Blocks |
/15 | 255.254.0.0 | 131,072 | 131,070 | 2 (Octet 2) | Regional Metro Networks |
/16Class B | 255.255.0.0 | 65,536 | 65,534 | 1 (Octet 2) / 256 (Octet 3) | Class B Default / Standard Cloud VPC (192.168.0.0/16, 10.0.0.0/16) |
/17 | 255.255.128.0 | 32,768 | 32,766 | 128 (Octet 3) | University & Large Campus LANs |
/18 | 255.255.192.0 | 16,384 | 16,382 | 64 (Octet 3) | Enterprise Office Hubs |
/19 | 255.255.224.0 | 8,192 | 8,190 | 32 (Octet 3) | Regional Corporate Buildings |
/20 | 255.255.240.0 | 4,096 | 4,094 | 16 (Octet 3) | Cloud Availability Zone (AZ) Subnets |
/21 | 255.255.248.0 | 2,048 | 2,046 | 8 (Octet 3) | Large Office Campus Subnets |
/22 | 255.255.252.0 | 1,024 | 1,022 | 4 (Octet 3) | Kubernetes Node / Pod CIDR Blocks |
/23 | 255.255.254.0 | 512 | 510 | 2 (Octet 3) | Medium Branch Office Networks |
/24Class C | 255.255.255.0 | 256 | 254 | 1 (Octet 3) / 256 (Octet 4) | Class C Default / Standard Office & Home LAN |
/25 | 255.255.255.128 | 128 | 126 | 128 (Octet 4) | Half /24 Subnet / Office Department |
/26 | 255.255.255.192 | 64 | 62 | 64 (Octet 4) | Standard Corporate Department Subnet |
/27Popular | 255.255.255.224 | 32 | 30 | 32 (Octet 4) | Small Team Subnet / Wireless Segment |
/28 | 255.255.255.240 | 16 | 14 | 16 (Octet 4) | Server Rack / Database Cluster |
/29 | 255.255.255.248 | 8 | 6 | 8 (Octet 4) | Router Cluster / HSRP / VRRP Virtual VIPs |
/30Legacy P2P | 255.255.255.252 | 4 | 2 | 4 (Octet 4) | Traditional Point-to-Point Router Link (2 Usable / 2 Reserved) |
/31RFC 3021 | 255.255.255.254 | 2 | 2 | 2 (Octet 4) | Point-to-Point Link (RFC 3021 - 0 Network/Broadcast Overhead) |
/32Host Route | 255.255.255.255 | 1 | 1 | 1 (Octet 4) | Host Route / Loopback Interface / Firewall Rule |
🧠Mental Math Tricks Grid (4 Cards)
1. The Magic 256 Rule
Instant Subnet Increment Step
Subtract the non-255 subnet mask octet from 256 to calculate the exact block size (subnet increment) in seconds.
2. Finger-Counting Bit Borrowing
Double Subnets, Halve Host Capacity
Every bit borrowed doubles the created subnets (2^n) and halves host capacity per subnet. Count on fingers from 1 to 6 bits.
3. Octet Jump Shortcuts
Locate the 'Interesting Octet' Instantly
Quickly map CIDR prefixes to their active working octet without converting binary digits:
4. Quick Wildcard Mask Inversion
Subtract Subnet Mask from 255.255.255.255
Derive Cisco ACL wildcard masks instantly by subtracting each mask octet from 255.
16. Test Your Knowledge
Click an answer to check it. Your score is tracked at the bottom.
Q1 — How many usable hosts does a /26 subnet have?
Q2 — What is the broadcast address of 192.168.1.64/26?
Q3 — Which subnet mask matches /27?
Q4 — In VLSM, why should you allocate subnets from largest to smallest?
Q5 — What does NAT stand for?
Q6 — How many subnets do you get by borrowing 3 bits from a /24?
Q7 — Which address is NOT valid in 192.168.1.0/30?
Q8 — What is the primary purpose of a VLAN?
Your Score
Keep practicing! Review the sections above and try again.
21. Cloud-Native & Container Networking
Modern cloud-native systems rely on virtualized network namespaces (netns), virtual ethernet pairs (veth), overlay tunnels, and kernel-level packet manipulation. Discover how Kubernetes CNI plugins, Docker isolation modes, and Layer 4/7 load balancers route microservice traffic at scale.
1. Kubernetes Networking Architecture & CIDR Ranges
Kubernetes enforces a mandatory IP-per-Pod flat network model: every Pod gets its own routable IP address and can communicate with all other Pods across nodes without NAT.
Real IP addresses assigned directly to container network interfaces (eth0 inside Pod). Allocated dynamically by the CNI plugin when Pods start up. Pod IPs change every time a Pod is recreated or rescheduled.
🔌 CNI (Container Network Interface) Plugins Comparison
Cilium CNI (eBPF)
Project Maintainer: Isovalent / CNCFInjects bytecode programs directly into kernel hooks (tc, cgroups, XDP). Replaces iptables DNAT entirely with eBPF BPF_MAP lookup tables. Provides Hubble deep flow observability and transparent WireGuard encryption.
# Cilium L7 HTTP NetworkPolicy Example
apiVersion: "cilium.io/v2"
kind: CiliumNetworkPolicy
metadata:
name: secure-api-access
spec:
endpointSelector:
matchLabels:
app: payment-service
ingress:
- fromEndpoints:
- matchLabels:
app: checkout
toPorts:
- ports:
- port: "8080"
protocol: TCP
rules:
http:
- method: "POST"
path: "/v1/charge"2. Docker Networking Drivers & Modes
Docker uses container network drivers to manipulate Linux network namespaces, iptables NAT tables, and virtual interfaces. Select a mode below to analyze host binding, performance, and packet paths.
Bridge Mode (Default)
docker run --net=bridgeContainers connect to a virtual software bridge (docker0) via virtual ethernet (veth) pairs. Outbound traffic uses IP Masquerading (NAT). User-defined bridges enable automatic container name DNS lookup.
✓ Architectural Advantages
- •Isolated container network namespace
- •Automatic container DNS on custom bridges
- •Secure default for standalone single-host containers
⚠ Technical Limitations
- •Port forwarding NAT overhead
- •Cannot span across multiple physical hosts without custom routing
3. Layer 4 (L4) vs Layer 7 (L7) Load Balancing & Ingress
Load balancers operate at different OSI layers to distribute traffic across container replicas. Compare transport-level packet routing (L4) with application-level HTTP routing (L7).
🌐 L7 Ingress Controller Mechanics
- ✓Inspection Depth: Decrypts TLS certificates (HTTPS Termination), parses HTTP methods, URI paths (
/v1/users), Host headers (api.domain.com), and cookies. - ✓Advanced Traffic Controls: Supports Canary deployment traffic splits (90/10 weighted routing), rate-limiting, CORS injection, and Web Application Firewall (WAF) rule sets.
- ✓Direct Pod Bypass: Modern K8s Ingress Controllers (NGINX/Envoy) watch K8s Endpoints API directly and forward packets straight to target Pod IPs without ClusterIP NAT overhead.
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: production-ingress
annotations:
nginx.ingress.kubernetes.io/rewrite-target: /
nginx.ingress.kubernetes.io/ssl-redirect: "true"
spec:
ingressClassName: nginx
rules:
- host: api.company.com
http:
paths:
- path: /v1/users
pathType: Prefix
backend:
service:
name: user-service
port:
number: 8080
- path: /v1/orders
pathType: Prefix
backend:
service:
name: order-service
port:
number: 90904. Interactive K8s Service IP Routing Simulator
Test how incoming client packets travel through Kubernetes abstractions (ClusterIP, NodePort, LoadBalancer, Headless, and Ingress) using either legacy iptables or high-performance eBPF data paths!
22. Network Diagnostics & CLI Sandbox
Master essential network troubleshooting CLI utilities (ping, traceroute, mtr, iperf3, dig, nmap). Test commands interactively in the simulated bash terminal sandbox, execute instant command presets, and reference the diagnostic cheat sheet.
Instant Execution Presets (Click to Run):
Structured Troubleshooting Workflow Matrix
Layer 3 ICMP Ping Test
Verify IP layer connectivity and physical/link layer reachability.
Hop Path & Delay Pinpoint
Identify exact router hop or provider link dropping packets.
DNS Resolution Audit
Confirm whether issue is IP routing or domain name resolution failure.
Firewall & Port Check
Detect blocked TCP/UDP ports, stateful firewall drops, or down services.
Bandwidth & Throughput
Measure maximum transmission rate, TCP window size, and UDP packet loss.
Diagnostic Tools Command Cheat Sheet
Comprehensive reference of syntax, flags, OSI layers, and practical use-cases.
Sends ICMP Echo Request packets to verify end-to-end IP reachability, latency (RTT), and packet loss percentage.
ping [options] <destination_ip_or_hostname>Maps every intermediate router hop along the packet path by incrementing IP TTL field from 1 up to destination.
traceroute [options] <destination_host>Combines the functionality of ping and traceroute into a single continuous real-time network diagnostic tool.
mtr [options] <target_host>Measures maximum attainable TCP and UDP network bandwidth, packet jitter, and datagram loss between two hosts.
iperf3 -c <server_ip> [options] | iperf3 -sFlexible DNS lookup utility that queries Domain Name System servers directly and prints exact response records.
dig [@server] <domain> [type] [options]Industry-standard port scanner and network security auditor used for host discovery and service enumeration.
nmap [scan_type] [options] <target>17. Routing & Gateway Protocols
Routers are the backbone of IP communications. They build forwarding decisions by evaluating packet destination addresses against local Routing Tables. Explore how routers learn paths dynamically via IGP & EGP Protocols, maintain seamless default gateway uptime with HSRP/VRRP Redundancy, condense massive ISP tables using BGP Aggregation, and execute Longest Prefix Matching.
Static vs. Dynamic Routing Protocols
OSPF (Open Shortest Path First)
Medium to large enterprise networks requiring fast convergence and hierarchical area design (Backbone Area 0).
Key Technical Highlights
Administrative Distance (AD) Trust Hierarchy (Lower = Better)Believability Score (0 - 255)
Gateway Redundancy (HSRP & VRRP Virtual IP Failover)
Interactive Failover Controls
Protocol Event Console Log
BGP Route Summarization & Aggregation
Reducing Global Routing Table Bloat
The Internet routing table contains over 900,000 IPv4 prefixes. To protect router RAM and CPU, Autonomous Systems summarize contiguous subnets into a single prefix before advertising to ISP peers.
Bitwise Matching Breakdown (22 Common Bits)Green = Identical Network Bits
Interactive Routing Table Lookup Simulator (Longest Prefix Match)
Matched 6 route entries. Subnet mask /29 won because it has the highest number of contiguous matching network bits (Longest Prefix Match Rule).
Active Router Forwarding Information Base (FIB)
Total Entries: 8| Status | Protocol | Network CIDR | Next Hop IP | Interface | AD / Metric | Action |
|---|---|---|---|---|---|---|
| ★ SELECTED | EIGRP | 10.0.1.48/29 | 10.0.1.49 | Eth1.20 | 90 / 15 | |
| MATCHED (/27) | Static | 10.0.1.32/27 | 10.0.1.1 | Eth1.10 | 1 / 1 | |
| MATCHED (/24) | Connected | 10.0.1.0/24 | 10.0.1.1 | Eth1 | 0 / 0 | |
| MATCHED (/16) | OSPF | 10.0.0.0/16 | 10.255.1.1 | Eth0 | 110 / 10 | |
| MATCHED (/8) | OSPF | 10.0.0.0/8 | 10.255.0.1 | Eth0 | 110 / 20 | |
| NO MATCH | Connected | 192.168.1.0/24 | 192.168.1.1 | Eth2 | 0 / 0 | |
| NO MATCH | BGP | 172.16.0.0/12 | 172.16.0.1 | Eth3 | 20 / 100 | |
| MATCHED (/0) | Static | 0.0.0.0/0 | 203.0.113.1 | WAN0 | 1 / 1 |
Add Custom Route Entry to Table
19. DHCP & IP Address Management (IPAM)
Dynamic Host Configuration Protocol (DHCP) automates IPv4/IPv6 allocation across local networks. Explore the step-by-step DORA handshake, Layer 3 relay agent forwarding across subnets, core DHCP options, and enterprise IPAM pool sizing.
The 4-Step DORA Handshake
DHCP DISCOVER Summary
When an unconfigured device connects to a network, it has no IP address. It sends a Layer 3 UDP broadcast to 255.255.255.255 on port 67. Since the client has no IP yet, its source IP is 0.0.0.0 and UDP source port is 68.
Payload Parameters & Options
DHCP Relay Agent (ip helper-address)
GIADDR (Gateway IP Address) field to 192.168.10.1, and forwards a unicast packet across subnets directly to 10.0.0.100.! Cisco IOS DHCP Relay Agent Configuration ! 1. Enter Gateway Subnet Interface (VLAN 10) interface GigabitEthernet0/0.10 description LAN-VLAN10-GATEWAY ip address 192.168.10.1 255.255.255.0 ! 2. Configure Primary & Secondary DHCP Server Relays ! Helper-address converts L2/L3 Broadcasts into Unicast to target IP ip helper-address 10.0.0.100 ip helper-address 10.0.0.101 ! 3. (Optional) Fine-tune Relay Security & Option 82 Insertion ip dhcp relay information option ip dhcp relay information trust-all
Essential DHCP Options
Specifies the subnet mask of the client's subnet according to dotted decimal notation.
List of IP addresses for routers on the client's subnet. Must be listed in preference order.
List of DNS recursive name servers available to the client.
Specifies the name of the client host, often populated automatically into Dynamic DNS (DDNS).
Specifies the domain name that client should use when resolving unqualified hostnames.
Identifies TFTP boot server used for PXE network operating system deployment.
Specifies the executable filename location on the TFTP server to initiate PXE boot.
Injects specific static routing table entries directly into client operating systems.
Enterprise IPAM & Pool Exhaustion Calculator
WARNING: High pool usage. High churn during peak hours may trigger address depletion.
20. Packet Encapsulation & Analysis
Every interaction on the internet depends on Packet Encapsulation—the process where raw application data is wrapped layer-by-layer with Transport headers, IP headers, and Ethernet frames before physical transmission over the wire. Understanding header bit fields, stateful TCP handshakes, and PCAP analysis tools like Wireshark is essential for network engineering and security analysis.
1. Interactive OSI vs TCP/IP Layer Stack Inspector
Select any layer to inspect protocol mapping, PDU names, headers attached, and addressing units.
Transport Layer
Provides end-to-end process-to-process data delivery, flow control, error recovery, and multiplexing.
2. Frame, Packet & Segment Header Anatomy
RFC Bit/Byte layout visualizer for Ethernet II Frames (Layer 2), IPv4 Packets (Layer 3), and TCP Segments (Layer 4).
Data Offset (4b) + Flags (9b)
Data Offset defines header size in 32-bit words. Control Flags control session state (URG, ACK, PSH, RST, SYN, FIN).
3. TCP 3-Way Handshake & Connection Teardown
Step-by-step TCP sequence number arithmetic, flag bitmask inspection, and TCP socket state transitions.
Step Explanation: Client picks an Initial Sequence Number (ISN=1000), sets SYN=1 flag, and sends connection request to Server port 443.
4. Interactive Wireshark PCAP Packet Viewer Simulator
Inspect real network trace packets, expand nested protocol headers, and analyze byte hex dumps.
| No. | Time (s) | Source | Destination | Protocol | Length | Info |
|---|---|---|---|---|---|---|
| 1 | 0.000000 | 192.168.1.50 | 93.184.216.34 | TCP | 74 | 54321 → 80 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 SACK_PERM=1 |
| 2 | 0.024115 | 93.184.216.34 | 192.168.1.50 | TCP | 74 | 80 → 54321 [SYN, ACK] Seq=0 Ack=1 Win=29200 Len=0 MSS=1460 |
| 3 | 0.024210 | 192.168.1.50 | 93.184.216.34 | TCP | 66 | 54321 → 80 [ACK] Seq=1 Ack=1 Win=64240 Len=0 |
| 4 | 0.025102 | 192.168.1.50 | 93.184.216.34 | HTTP | 144 | GET /index.html HTTP/1.1 |
| 5 | 0.026401 | 192.168.1.50 | 1.1.1.1 | DNS | 83 | Standard query 0x1a2b A api.example.com |
| 6 | 0.038920 | 192.168.1.50 | 8.8.8.8 | ICMP | 98 | Echo (ping) request id=0x1234, seq=1, ttl=64 |
23. Wireless & WLAN Integration
Modern Enterprise Wireless LANs (WLANs) seamlessly bridge unguided RF radio signals to wired Ethernet infrastructures. This section explores SSID-to-VLAN mapping, Wireless LAN Controller (WLC) topologies, RF spectrum frequency bands (2.4GHz, 5GHz, 6GHz), Channel Bonding, and real-time Signal Propagation & Interference dynamics.
SSID-to-VLAN Mapping & WLC Topology
Live Frame Flow for SSID: Corp-Enterprise
CAPWAP Data Tunneling (UDP 5247)Centralized WLC (Split MAC Architecture)
CAPWAP TunnelAP handles real-time 802.11 beaconing and frame acknowledgments (Local MAC). All user data packets are encapsulated in CAPWAP tunnels (UDP 5247) and sent to the WLC. WLC performs centralized 802.1X authentication, L2 VLAN tagging, and firewall policy enforcement.
FlexConnect (Local Switching Architecture)
Branch & Remote APsDesigned for branch offices over WAN. Management and control traffic (CAPWAP Control UDP 5246) goes to the central WLC, but user payload traffic is switched locally onto the local switch VLANs. If WAN disconnects, branch APs remain operational locally.
Wi-Fi Frequency Bands & Technical Comparison
2.4 GHz Band (Legacy & IoT)
2.412 - 2.484 GHz (~83.5 MHz)- • Maximum signal range and wall penetration
- • Compatible with 100% of Wi-Fi hardware
- • Only 3 non-overlapping channels (Heavy congestion)
- • Severe Bluetooth & Microwave interference
| Specification / Metric | 2.4 GHz Band | 5 GHz Band | 6 GHz Band (Wi-Fi 6E/7) |
|---|---|---|---|
| Frequency Range | 2.412 - 2.484 GHz | 5.150 - 5.850 GHz | 5.925 - 7.125 GHz |
| Total Spectrum Pool | ~83.5 MHz | ~500 MHz | ~1,200 MHz (Massive) |
| 20MHz Non-Overlapping Ch. | 3 Channels (1, 6, 11) | Up to 25 Channels | Up to 59 Channels |
| Max Supported Channel Width | 20 MHz (40MHz unsafe) | 20 / 40 / 80 / 160 MHz | Up to 320 MHz (Wi-Fi 7) |
| Indoor Coverage Distance | ~35m (High penetration) | ~25m (Moderate penetration) | ~15m (Line-of-sight preferred) |
| Interference Sources | Microwaves, Bluetooth, Zigbee | DFS Weather Radars | Zero Legacy Devices (Clean) |
| Max Theoretical PHY Speed | 1.1 Gbps (Wi-Fi 6) | 9.6 Gbps (Wi-Fi 6) | 46.1 Gbps (Wi-Fi 7 MLO) |
2.4 GHz Channel Planner & 5/6 GHz Bonding
2.4 GHz Channel Overlap Calculator (Channels 1 to 11)20 MHz Width / 5 MHz Spacing
Channels are separated by at least 25 MHz (5 channel numbers). Zero spectral overlap. Optimal cellular AP deployment!
5 GHz & 6 GHz Channel Bonding Hierarchy
Combines contiguous 20MHz channels to multiply throughput at the expense of spectrum density and SNR.
Interactive Wi-Fi Signal & Spectrum Overlap Visualizer
1. Transmitter & Environment
2. AP Channels & Noise
3. Derived Signal Quality
Real-Time RF Spectrum Mask & Signal Shape
No Overlap18. Network Security & Access Control
Modern cloud and enterprise networks enforce defense-in-depth through multi-layered access control mechanisms. From Stateless Subnet NACLs and Stateful Instance Security Groups to Encapsulated Overlay Tunnels (VPN & VXLAN) and Network Address Translation (NAT), secure network architectures protect workloads at every hop.
1. Network ACLs vs. Security Groups
Comparing subnet-level stateless packet filters against hypervisor/ENI stateful firewalls.
| Architectural Feature | Network ACL (NACL) | Security Group (SG) |
|---|---|---|
| Operating Boundary | Subnet Boundary (VPC Router Level) | Instance / ENI Level (Hypervisor) |
| State Tracking | Stateless Return traffic MUST be explicitly allowed in Outbound rules. | Stateful Return traffic automatically allowed regardless of outbound rules. |
| Rule Actions Supported | ALLOW and DENY rules | ALLOW rules only (Implicit Default Deny) |
| Evaluation Order | Sequential by Rule Number (Lowest number evaluated first) | All rules evaluated simultaneously before decision |
| Ephemeral Return Ports | Must open ports 1024-65535 outbound for response traffic! | Automatically tracked by connection state table |
Return Traffic Flow Breakdown — NACL (Stateless)Step 1 of 3
External client sends HTTP request to web server on port 80 using client ephemeral port 52134.
VPN Tunnels
WireGuard — Modern Lightweight Crypto Tunnel
Designed as a fast, simple replacement for IPsec and OpenVPN. Operates in Linux kernel space with minimal overhead (~4,000 lines of code).
VXLAN Encapsulation
Virtual Extensible LAN (VXLAN) encapsulates Layer 2 Ethernet frames inside Layer 4 UDP packets. Used in data center spine-leaf topologies and Kubernetes CNI overlays (Flannel/Calico) to expand past the 4,096 VLAN limit up to 16.7 Million VNI segments.
Contains the 24-bit VXLAN Network Identifier (VNI) providing up to 16,777,216 isolated virtual Layer 2 subnets over a shared L3 fabric.
3. Network Address Translation (NAT) Variants
Understanding SNAT, DNAT, and PAT (NAPT) packet header transformations at boundary gateways.
PAT — Port Address Translation
Maps thousands of internal private host IP addresses onto a single shared public IP address by assigning unique public source ports for each session.
Both source IP and source port are translated to prevent socket collisions on public internet responses.
4. Interactive Security Rule Inspector
Test arbitrary packet parameters (Source IP, Destination Port, Protocol) against custom firewall ACLs.
Testing packet: TCP packet to port 80 from 203.0.113.50.
Matched explicitly enabled Rule #100 (Allow inbound HTTP from internet). Evaluation halted (First Match Wins).
Active NACL Rule ConfigurationClick rule checkbox to enable/disable
| Active | Rule # | Protocol | Port Range | Source CIDR | Action | Description |
|---|---|---|---|---|---|---|
| #100 | TCP | 80 | 0.0.0.0/0 | ALLOW | Allow inbound HTTP from internet | |
| #110 | TCP | 443 | 0.0.0.0/0 | ALLOW | Allow inbound HTTPS from internet | |
| #200 | TCP | 22 | 192.168.1.0/24 | ALLOW | Allow SSH only from Admin Subnet | |
| #210 | TCP | 22 | 0.0.0.0/0 | DENY | Deny SSH from everywhere else | |
| #300 | TCP | 3306 | 10.0.1.0/24 | ALLOW | Allow MySQL from Web Subnet | |
| #999 | ALL | ALL | 0.0.0.0/0 | DENY | Default Deny All Inbound Traffic |