IP Knowledge — A Complete Guide to IP Addresses & Routing

1. The Evolution & Architecture of Internet Protocol Addressing

Formulated in the late 1970s and standardized in 1981 under RFC 791, the Internet Protocol was designed to interconnect disparate computer networks into a unified, packet-switched internetwork. Today, billions of smartphones, cloud servers, and industrial IoT sensors exchange petabytes of information every second governed by these fundamental rules.

2. Deep-Dive Mechanism Analysis: IP Packet Header Anatomy

When an application transmits data over a socket, the operating system network stack encapsulates the payload in an IP packet. Below is a detailed technical examination of how routers process key header fields:

• Time to Live (TTL): An 8-bit integer initialized by the sending host (typically to 64, 128, or 255). Every intermediate router decrements this counter by 1 before forwarding the packet. If the counter reaches zero, the packet is discarded, and an ICMP Type 11 (Time Exceeded) datagram is returned to the sender. This simple mechanism prevents routing loops from circulating forever and consuming backbone bandwidth.
• Protocol Field: An 8-bit identifier that instructs the receiving host operating system which transport protocol module must process the enclosed payload. Standard protocol numbers include 1 for ICMP, 6 for TCP, 17 for UDP, and 41 for IPv6 encapsulation.
• Identification, Flags & Fragment Offset: When a packet exceeds the MTU of an egress physical interface (such as a 1500-byte Ethernet frame transiting an optical link restricted to 1420 bytes), the router divides the payload. The Don't Fragment (DF) flag dictates whether fragmentation is permitted. If DF is set and the packet is oversized, the router drops the packet and emits an ICMP Type 3 Code 4 (Fragmentation Needed) error—the foundational mechanism behind Path MTU Discovery (PMTUD).
• Source & Destination Addresses: Each 32 bits (4 octets) long, representing the logical sender and recipient interfaces.

3. CIDR, Subnet Masks, and Address Calculations

Prior to 1993, IPv4 operated under rigid "Classful" network boundaries (Class A, B, and C), leading to massive address waste. The introduction of Classless Inter-Domain Routing (CIDR) under RFC 1519 decoupled subnetting from byte boundaries, allowing variable-length subnet masks (VLSM).

4. Decision Tree: IP Troubleshooting & Subnet Diagnostics

[Connection & IP Strategy Root Decision Node]
  │
  ├── 1. Primary Objective
  │     ├── A. Need to Inspect / Verify Current Connection
  │     │     ├── ① Check Public IPv4/IPv6 Address ──> Use What Is My IP (Home /)
  │     │     ├── ② Audit DNS / WebRTC / IPv6 Leaks ──> Run IP Tests (/ip-tests/)
  │     │     └── ③ Inspect Remote Server or Sender ──> Use IP Lookup (/ip-lookup/)
  │     │
  │     ├── B. Need to Mask or Rotate Outbound IP
  │     │     ├── ① Temporary Local Reset ──> Router Restart or DHCP Renew (Free)
  │     │     ├── ② High-Anonymity Browsing ──> Tor Browser (Free, Slower)
  │     │     └── ③ High-Speed Persistent Tunnel ──> Commercial Proxy / VPN
  │     │
  │     └── C. Developer & Scraping Requirements
  │           ├── ① High Concurrency / Web Scraping ──> Residential Rotating Proxies
  │           └── ② Low-Latency Dedicated Tunnel ──> Datacenter / Private VLESS Exit
  │
  ├── 2. Protocol Selection
  │     ├── ① Modern Anti-Censorship ──> VLESS + Reality / Trojan
  │     ├── ② Universal Cross-Platform Tooling ──> SOCKS5 / HTTP
  │     └── ③ Extreme High-Jitter Networks ──> Hysteria2 (UDP-based)
  │
  └── 3. Action Step
        ├── Commercial Proxy Plans ──> Check /proxy-plans/ for Verified Pricing
        └── Network Recovery Guide ──> Check /fixes/ for Connection Diagnostics

5. Deep-Dive Comparison: 8 Network Addressing & Routing Protocols

6. Related Network Diagnostics & Knowledge Hubs