Networking and Web Tools: Subnetting, Bandwidth, and Encoding Explained
Learn IP subnetting with CIDR notation, bandwidth and transfer time calculations, password strength per NIST SP 800-63B, and Base64 encoding for web development.

Your company is setting up a new office with 50 employees. You need to subnet the 10.0.0.0/24 network into departments. Engineering needs 20 hosts, Sales needs 15, HR needs 10, and IT needs 5. What subnet masks do you use? How many addresses does each department get?
If you assign /27 (30 usable hosts) to Engineering, /27 to Sales, /28 (14 usable) to HR, and /29 (6 usable) to IT, you have used four subnets and still have room for more. But getting there requires understanding CIDR notation, binary subnetting, and host calculation. This guide covers the math behind networking and web tools that IT professionals use daily.
IP Subnetting and CIDR
What Is CIDR?
CIDR (Classless Inter-Domain Routing) notation expresses a subnet by appending the prefix length to the IP address. For example, 192.168.1.0/24 means the first 24 bits are the network portion and the remaining 8 bits are for hosts.
Subnet Mask to CIDR Conversion
| Subnet Mask | CIDR | Usable Hosts | Binary (last octet) |
|---|---|---|---|
| 255.255.255.0 | /24 | 254 | 00000000 |
| 255.255.255.128 | /25 | 126 | 10000000 |
| 255.255.255.192 | /26 | 62 | 11000000 |
| 255.255.255.224 | /27 | 30 | 11100000 |
| 255.255.255.240 | /28 | 14 | 11110000 |
| 255.255.255.248 | /29 | 6 | 11111000 |
| 255.255.255.252 | /30 | 2 | 11111100 |
Host Calculation Formula
Usable Hosts = 2^(32 - CIDR) - 2
The minus 2 accounts for the network address (all host bits 0) and broadcast address (all host bits 1).
Example: Subnetting 10.0.0.0/24
You have 10.0.0.0/24 (256 total addresses, 254 usable). You need 4 subnets.
Divide by 4: each subnet gets 64 addresses (/26, 62 usable).
| Subnet | Network | Usable Range | Broadcast |
|---|---|---|---|
| 1 | 10.0.0.0/26 | 10.0.0.1 to 10.0.0.62 | 10.0.0.63 |
| 2 | 10.0.0.64/26 | 10.0.0.65 to 10.0.0.126 | 10.0.0.127 |
| 3 | 10.0.0.128/26 | 10.0.0.129 to 10.0.0.190 | 10.0.0.191 |
| 4 | 10.0.0.192/26 | 10.0.0.193 to 10.0.0.254 | 10.0.0.255 |
Variable Length Subnet Masking (VLSM)
When departments need different sizes, use VLSM. Start with the largest subnet and work down.
For our office example (Engineering 20, Sales 15, HR 10, IT 5):
| Department | Hosts Needed | CIDR | Usable Hosts | Network |
|---|---|---|---|---|
| Engineering | 20 | /27 | 30 | 10.0.0.0/27 |
| Sales | 15 | /27 | 30 | 10.0.0.32/27 |
| HR | 10 | /28 | 14 | 10.0.0.64/28 |
| IT | 5 | /29 | 6 | 10.0.0.80/29 |
Remaining space: 10.0.0.88/29 through 10.0.0.255 is available for future use.
Cloud Provider Reserved IPs
Cloud providers reserve IP addresses in each subnet. Always account for these when planning:
| Provider | Reserved IPs per Subnet |
|---|---|
| AWS | 5 (network, broadcast, DNS, gateway, future use) |
| Azure | 5 (network, broadcast, 2 Azure, 1 future) |
| GCP | 4 (network, broadcast, 2 Google) |
| OCI | 3 (network, broadcast, 1 Oracle) |
A /28 in AWS gives 11 usable hosts, not the textbook 14.
Use our IP Subnet Calculator to calculate network addresses, broadcast addresses, usable host ranges, and CIDR conversions.
Bandwidth and Transfer Time
The Mbps vs MB/s Confusion
Network speeds are measured in bits per second (Mbps). File sizes are measured in bytes (MB). One byte equals 8 bits. The conversion trips up many people.
Transfer Time = File Size (in bits) / Network Speed (in bits per second)
Example: Downloading a 10 GB File
File size: 10 GB = 10 x 1,073,741,824 bytes = 10,737,418,240 bytes = 85,899,345,920 bits Network speed: 100 Mbps = 100,000,000 bits per second
Transfer time: 85,899,345,920 / 100,000,000 = 859 seconds = 14.3 minutes
But this assumes 100% efficiency. Real-world TCP throughput is typically 70% to 90% of theoretical maximum due to protocol overhead, packet loss, and latency. At 80% efficiency:
Actual transfer time: 859 / 0.80 = 1,074 seconds = 17.9 minutes
Quick Conversion Table
| File Size | At 10 Mbps | At 100 Mbps | At 1 Gbps |
|---|---|---|---|
| 1 MB | 0.8 sec | 0.08 sec | 0.008 sec |
| 100 MB | 80 sec | 8 sec | 0.8 sec |
| 1 GB | 819 sec (13.7 min) | 82 sec (1.4 min) | 8.2 sec |
| 10 GB | 8,192 sec (2.3 hr) | 819 sec (13.7 min) | 82 sec (1.4 min) |
| 100 GB | 81,920 sec (22.8 hr) | 8,192 sec (2.3 hr) | 819 sec (13.7 min) |
Bandwidth-Delay Product
For high-latency links (satellite, intercontinental), the bandwidth-delay product (BDP) determines how much data can be "in flight" at once. TCP window size must be at least as large as the BDP for optimal throughput.
BDP = Bandwidth (bits/sec) x Round-Trip Time (sec)
Example: 100 Mbps link with 200 ms RTT: BDP = 100,000,000 x 0.2 = 20,000,000 bits = 2.5 MB
The TCP window must be at least 2.5 MB to fill the pipe. Default TCP windows are often too small for high-latency, high-bandwidth links.
Use our Bandwidth Calculator to calculate transfer times and convert between Mbps and MB/s.
Password Strength and Security
NIST SP 800-63B Guidelines (2026)
The National Institute of Standards and Technology published SP 800-63B as the authoritative guide on password security. Key recommendations updated for 2026:
- Minimum length: 8 characters (user-chosen) or 6 characters (system-generated)
- Maximum length: At least 64 characters must be supported
- Composition rules: Eliminate mandatory complexity rules (no forced special characters, numbers, or mixed case). Length is more important than complexity.
- Password history: Check new passwords against a list of known compromised passwords (using services like HaveIBeenPwned)
- Password rotation: Do not require periodic changes unless compromise is suspected. Forced rotation leads to weaker passwords.
- Paste allowed: Allow paste in password fields to facilitate password manager use
- Rate limiting: Limit authentication attempts and use time-increasing delays
Entropy Calculation
Password entropy measures randomness in bits:
Entropy = log2(charset^length) = length x log2(charset)
| Character Set | Size | Entropy per Character |
|---|---|---|
| Lowercase letters | 26 | 4.7 bits |
| Lowercase + uppercase | 52 | 5.7 bits |
| Alphanumeric | 62 | 5.95 bits |
| Alphanumeric + common symbols | 95 | 6.5 bits |
Example: Password Strength
An 8-character alphanumeric password: 8 x 5.95 = 47.6 bits of entropy. A 16-character alphanumeric password: 16 x 5.95 = 95.2 bits of entropy.
Each additional character roughly doubles the cracking time. A 12-character password is 16 times harder to crack than an 8-character one.
Cracking Time Estimates (2026 Hardware)
| Entropy | GPU Cracking Time (8 x RTX 4090) |
|---|---|
| 40 bits | Seconds |
| 50 bits | Minutes |
| 60 bits | Hours |
| 70 bits | Days |
| 80 bits | Months |
| 90 bits | Years |
| 100 bits | Centuries |
| 128 bits | Heat death of the universe |
A 12-character alphanumeric password (71.4 bits) takes days to crack with consumer hardware. A 16-character password (95.2 bits) takes centuries. Length matters more than complexity.
Use our Password Generator to create strong random passwords, and our Password Strength Calculator to estimate entropy and cracking time.
Base64 and URL Encoding
Base64 Encoding
Base64 encodes binary data as ASCII text. It is used in email attachments, data URIs, and API authentication. Every 3 bytes of binary data become 4 Base64 characters.
Example: The text "Hello" in Base64:
- H = 72, e = 101, l = 108, l = 108, o = 111
- Binary: 01001000 01100101 01101100 01101100 01101111
- Group into 6-bit chunks: 010010 000110 010101 101100 011011 000110 1111(00)
- Base64: SGVsbG8=
The "=" padding indicates the original data was not a multiple of 3 bytes.
URL Encoding
URL encoding (percent encoding) replaces unsafe ASCII characters with % followed by two hex digits. Spaces become %20, ampersands become %26, and equals signs become %3D.
Example: "hello world&foo=bar" encodes to "hello%20world%26foo%3Dbar"
Use our Base64 Encoder/Decoder to encode or decode Base64 data, and our URL Encoder for URL encoding.
Real-World Scenarios
Scenario 1: Office Network Design
You are setting up a 4-department office using 10.0.0.0/24.
Engineering (20 hosts): 10.0.0.0/27 (30 usable) Sales (15 hosts): 10.0.0.32/27 (30 usable) HR (10 hosts): 10.0.0.64/28 (14 usable) IT (5 hosts): 10.0.0.80/29 (6 usable) Guest WiFi: 10.0.0.88/29 (6 usable) Future expansion: 10.0.0.96/27 through 10.0.0.255 available
This VLSM plan efficiently allocates addresses with minimal waste and room for growth.
Scenario 2: Cloud Migration Bandwidth Planning
You are migrating 500 GB of data to AWS. Your upload speed is 50 Mbps.
Theoretical time: 500 x 8,589,934,592 / 50,000,000 = 85,899 seconds = 23.9 hours At 80% efficiency: 23.9 / 0.80 = 29.9 hours
Plan for approximately 30 hours. Use AWS Direct Connect or a physical appliance (Snowball) if the timeline is too long.
Scenario 3: Password Policy Update
Your company currently requires 8-character passwords with mandatory uppercase, lowercase, numbers, and special characters, changed every 90 days. Per NIST SP 800-63B, you should:
- Increase minimum to 12 characters
- Remove mandatory composition rules
- Remove 90-day rotation requirement
- Check new passwords against compromised password lists
- Allow paste for password managers
- Support up to 64 characters
A 12-character password without forced complexity has 71.4 bits of entropy and is easier to remember than an 8-character password with forced complexity (47.6 bits).
Common Mistakes
1. Confusing bits and bytes. Network speeds are in bits (Mbps). File sizes are in bytes (MB). Always convert to the same unit before calculating transfer time. 100 Mbps is 12.5 MB/s, not 100 MB/s.
2. Not accounting for reserved IPs in cloud subnets. AWS reserves 5 IPs per subnet. A /28 in AWS gives 11 usable hosts, not 14. Always check your cloud provider's reserved IP documentation.
3. Using mandatory complexity instead of length. NIST SP 800-63B explicitly recommends against forced composition rules. A 16-character lowercase password (74.7 bits) is stronger than an 8-character complex password (52 bits).
4. Forgetting protocol overhead in bandwidth calculations. TCP/IP headers, encryption overhead, and packet loss reduce real-world throughput to 70% to 90% of theoretical maximum. Always add a 20% buffer.
5. Not planning for growth in subnetting. A department that needs 14 hosts today may need 30 in two years. Always size subnets with at least 50% headroom. A /28 for 10 hosts leaves no room for growth. Use /27 instead.
External Research and Resources
- IETF RFC 1918: Private IP Address Allocation defines the private IP address ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) used in virtually all private networks.
- NIST SP 800-63B: Digital Identity Guidelines is the authoritative source for password policy recommendations, updated to emphasize length over complexity and eliminate forced rotation.
- IETF RFC 4648: Base64 Encoding defines the Base64 encoding standard used in email, web, and API data transfer.
People Also Ask
How do I calculate usable hosts in a subnet?
Usable hosts = 2^(32 - CIDR) - 2. The minus 2 accounts for the network address and broadcast address. For a /24: 2^8 - 2 = 254 usable hosts. For a /28: 2^4 - 2 = 14 usable hosts. In cloud environments, subtract provider-reserved IPs (5 for AWS, 5 for Azure, 4 for GCP). Use our IP Subnet Calculator for instant results.
How long does it take to transfer a file?
Transfer time = File size in bits / Network speed in bits per second. A 10 GB file at 100 Mbps: 10 x 8,589,934,592 / 100,000,000 = 859 seconds = 14.3 minutes. Account for 20% protocol overhead: approximately 17.9 minutes. Use our Bandwidth Calculator for instant results.
What makes a strong password in 2026?
Per NIST SP 800-63B, password strength comes from length, not complexity. Use at least 12 characters. A 12-character alphanumeric password has 71.4 bits of entropy and takes days to crack with consumer GPUs. A 16-character password takes centuries. Use a password manager and enable multi-factor authentication. Use our Password Generator to create strong passwords.
What is Base64 encoding used for?
Base64 encodes binary data as ASCII text so it can be transmitted over text-only channels like email or embedded in JSON APIs. Every 3 bytes of binary data become 4 Base64 characters. It is used in email attachments, data URIs in HTML, API authentication tokens, and JWT tokens. Use our Base64 Calculator to encode or decode.
Related Calculators
- IP Subnet Calculator - Calculate subnets, CIDR, and host ranges
- Bandwidth Calculator - Calculate transfer times and convert Mbps to MB/s
- Password Generator - Generate strong random passwords
- Password Strength Calculator - Estimate password entropy and cracking time
- Base64 Calculator - Encode and decode Base64 data
- URL Encoder - Encode and decode URLs
- Binary Calculator - Binary arithmetic and conversions
- Hex Calculator - Hexadecimal calculations
- Number Converter - Convert between number systems
Related Articles

Weather Calculators: Wind Chill, Heat Index, and Dew Point Explained
Learn how the NWS calculates wind chill, heat index, and dew point. Updated with 2026 NOAA formulas, NWS heat tools, and temperature conversion guidance.

Sleep Math: How Sleep Cycles Work and When to Go to Bed
Stop counting hours and start counting cycles. Learn the 90-minute sleep cycle formula, optimal bedtimes by wake time, and how age changes your sleep needs.

Road Trip Budget: How to Calculate Fuel Costs and Gas Mileage
Plan your road trip budget with precision. Learn how to calculate MPG, fuel costs, and tire size effects on speedometer accuracy. Updated with 2026 EPA and AAA data.