Skip to content

Complete Computer Networking Study Guide

flowchart TD
A[Hub] --> B[Key Concepts]
A --> C[Core Principles]
A --> D[Practical Applications]
B --> E[Fundamental definitions]
C --> F[Design patterns]
D --> G[Real-world usage]

Computer networking is the backbone of modern computing. Every application that communicates over the internet — web browsers, mobile apps, APIs, databases, streaming services — relies on networking protocols and infrastructure. Understanding how networks work is essential for building reliable, secure, and performant systems.

This hub page maps every resource on this site. The learning path takes you from the foundational OSI model through IP addressing, transport protocols, application protocols, security, and network tools. Each section includes practical examples, packet captures, and troubleshooting techniques.


The OSI (Open Systems Interconnection) model and the TCP/IP model are the conceptual frameworks that organise networking protocols into layers. Understanding these models is the foundation for everything else in networking.

The OSI model divides networking into seven layers, each with specific responsibilities:

  1. Physical — raw bit transmission over physical media (cables, radio waves)
  2. Data Link — node-to-node delivery, MAC addresses, and Ethernet frames
  3. Network — end-to-end routing, IP addresses, and packet forwarding
  4. Transport — reliable (TCP) or unreliable (UDP) data delivery between processes
  5. Session — session management and dialog control
  6. Presentation — data formatting, encryption, and compression
  7. Application — network services to user applications (HTTP, DNS, SMTP)

The TCP/IP model simplifies this into four layers: Link, Internet, Transport, and Application. In practice, TCP/IP is the model used on the internet.

Encapsulation is the process of wrapping data with protocol headers as it moves down the layers. Each layer adds its own header (and sometimes trailer) to the data from the layer above. This is why a single HTTP request involves headers at every layer.


IP addressing is the mechanism that allows packets to be routed from source to destination across interconnected networks. IPv4 and IPv6 are the two versions of the Internet Protocol.

IPv4 addresses are 32-bit numbers written in dotted-decimal notation (e.g., 192.168.1.1). There are roughly 4.3 billion IPv4 addresses — not enough for every device on the internet, which is why NAT (Network Address Translation) and IPv6 exist.

Subnetting divides a network into smaller sub-networks. A subnet mask determines which portion of an IP address identifies the network and which identifies the host. CIDR notation (e.g., /24) specifies the prefix length — the number of network bits.

IPv6 addresses are 128-bit numbers written in hexadecimal with colons (e.g., 2001:0db8:85a3::8a2e:0370:7334). IPv6 eliminates the need for NAT and provides a virtually unlimited address space.

Private IP ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) are used within local networks and are not routable on the public internet. NAT translates between private and public addresses.


TCP (Transmission Control Protocol) and UDP (User Datagram Protocol) are the two primary transport layer protocols. They serve different purposes and make different trade-offs between reliability and performance.

TCP provides reliable, ordered, byte-stream delivery. It uses a three-way handshake (SYN, SYN-ACK, ACK) to establish connections, sequence numbers for ordering, acknowledgements for reliability, and flow control to prevent overwhelming the receiver.

UDP provides unreliable, connectionless, datagram delivery. It has no handshake, no ordering, and no retransmission. This makes it fast and lightweight — ideal for DNS queries, real-time video, gaming, and any application where speed matters more than perfect reliability.

TCP flow control uses a sliding window mechanism. The receiver advertises how much data it can buffer; the sender limits its transmission rate accordingly. This prevents the sender from overwhelming the receiver’s buffer.

TCP congestion control adjusts the sending rate based on network conditions. Algorithms like slow start, congestion avoidance, fast retransmit, and fast recovery prevent congestion collapse.


DNS (Domain Name System) translates human-readable domain names into IP addresses. It is one of the most critical infrastructure services on the internet — without it, every web request would require users to remember IP addresses.

  • DNS Overview — domain hierarchy, resolution process, and record types
  • DNS Architecture — recursive resolvers, root servers, and caching
  • DNS — record types (A, AAAA, CNAME, MX, TXT), TTL, and troubleshooting

DNS resolution is the process of translating a domain name to an IP address. Your device queries a recursive resolver, which queries root servers, TLD servers, and authoritative servers in sequence. The result is cached at each level to reduce future lookups.

DNS record types serve different purposes:

  • A maps a domain to an IPv4 address
  • AAAA maps a domain to an IPv6 address
  • CNAME creates an alias from one domain to another
  • MX specifies mail servers for a domain
  • TXT stores arbitrary text (used for verification and SPF records)

DNS caching occurs at every level — browser, operating system, recursive resolver, and authoritative server. The TTL (Time to Live) determines how long a record can be cached. Lower TTLs mean faster propagation of changes but more DNS queries.


HTTP (HyperText Transfer Protocol) is the foundation of the World Wide Web. HTTPS adds TLS encryption to HTTP, providing confidentiality and integrity for web communication.

  • HTTP Overview — request/response model, methods, and status codes
  • HTTP — headers, cookies, caching, and connection management
  • HTTP/2 and HTTP/3 — multiplexing, server push, and QUIC
  • WebSockets — bidirectional communication for real-time applications

HTTP methods indicate the desired action: GET retrieves data, POST creates resources, PUT replaces resources, PATCH partially updates resources, and DELETE removes resources. Idempotent methods (GET, PUT, DELETE) can be safely retried without side effects.

HTTP status codes indicate the result of a request: 2xx success, 3xx redirection, 4xx client error, 5xx server error. Common codes include 200 OK, 301 Moved Permanently, 404 Not Found, and 500 Internal Server Error.

HTTP/2 introduced multiplexing (multiple requests over a single connection), header compression, and server push. HTTP/3 replaces TCP with QUIC, improving performance on unreliable networks.


TLS (Transport Layer Security) provides encryption, authentication, and integrity for network communication. HTTPS is HTTP over TLS — every secure website uses TLS.

  • TLS Overview — encryption, certificates, and the handshake process
  • TLS — symmetric and asymmetric encryption, certificate chains, and trust
  • TLS Internals — cipher suites, key exchange, and protocol versions

The TLS handshake establishes a secure connection. The client and server negotiate cipher suites, exchange keys, and verify certificates. This happens before any application data is sent — the handshake is transparent to the user.

Symmetric encryption (AES, ChaCha20) encrypts data with a shared key. It is fast and suitable for bulk data. Asymmetric encryption (RSA, ECDSA) uses a public-private key pair. It is used during the handshake to exchange the symmetric key, not for bulk data.

Certificate chains establish trust. A server presents its certificate, which is signed by an intermediate CA, which is signed by a root CA. The client verifies the chain back to a trusted root certificate in its trust store.


Network tools are essential for diagnosing, debugging, and understanding network behaviour. Knowing how to use these tools separates competent engineers from those who guess.

ping tests connectivity by sending ICMP echo requests and measuring round-trip time. It tells you whether a host is reachable and how latency compares to baseline.

traceroute (or tracert on Windows) shows the path packets take to a destination. It identifies which router is causing delays or packet loss.

tcpdump captures raw packet data on a network interface. It is the most powerful tool for understanding exactly what is happening on the wire. Learn its filter syntax — it is indispensable for debugging.


Layer 2 handles communication within a single network segment. Ethernet is the dominant Layer 2 technology, using MAC addresses to identify devices and switches to forward frames.

MAC addresses are 48-bit hardware addresses burned into network interfaces. They are used for local delivery within a network segment — once a packet reaches the destination network, ARP resolves the IP address to a MAC address.

VLANs (Virtual LANs) logically segment a physical network. Devices on different VLANs cannot communicate directly — they must go through a router. VLANs improve security and reduce broadcast traffic.


Wireless networking uses radio waves to provide network connectivity without physical cables. Wi-Fi is the dominant wireless technology for local area networking.

Wi-Fi standards (802.11a/b/g/n/ac/ax) define speed, range, and frequency bands. Modern networks use Wi-Fi 6 (802.11ax) for improved performance in dense environments.

WPA3 is the current Wi-Fi security standard. It provides stronger encryption and protection against offline dictionary attacks. Never use WEP or WPA — they are broken.


Email and application protocols provide specific services over the network. Understanding them is essential for building and maintaining communication systems.

SMTP (Simple Mail Transfer Protocol) sends email between servers. IMAP (Internet Message Access Protocol) retrieves email from a server while keeping it synchronised across devices. POP3 (Post Office Protocol) downloads email to a single device.

SSH (Secure Shell) provides encrypted remote access to servers. It is the standard tool for server administration. Use key-based authentication instead of passwords.


Networking knowledge builds in layers — literally. Follow this progression.

  • Study the OSI and TCP/IP models
  • Learn IP addressing and subnetting
  • Understand TCP and UDP fundamentals
  • Study DNS resolution and record types
  • Learn HTTP methods, status codes, and headers
  • Understand TLS and certificate chains
  • Master network tools — tcpdump, Wireshark, traceroute
  • Study Layer 2 — Ethernet, VLANs, and switching
  • Learn wireless networking and email protocols
  • Study network security — firewalls, IDS/IPS, and VPNs
  • Learn cloud networking — VPCs, load balancers, and CDNs
  • Build and debug real networked applications

Wyatt’s Notes is a network of interconnected study sites. The networking content connects to related material:


Start with the OSI model and TCP/IP. Understand what each layer does and which protocols operate at each layer. Then learn IP addressing — subnetting is a fundamental skill. Build from the bottom up.

Yes. Subnetting is essential for network design, troubleshooting, and security. Practise calculating subnets by hand — it builds an intuition that tools alone cannot provide.

What is the difference between TCP and UDP?

Section titled “What is the difference between TCP and UDP?”

TCP provides reliable, ordered delivery with connection management. UDP provides fast, connectionless delivery without reliability guarantees. Use TCP for web traffic, file transfer, and email. Use UDP for DNS, video streaming, gaming, and real-time communication.

Start with ping — is the host reachable? Then traceroute — where is the packet being dropped? Then tcpdump — what does the actual traffic look like? Work from connectivity up to application layer.

TLS encrypts data in transit, preventing eavesdropping and tampering. Without TLS, anyone on the network path can read your passwords, modify your data, and impersonate the server. Always use HTTPS.

Start with ping, traceroute, and tcpdump. These three tools can diagnose the vast majority of network problems. Learn Wireshark for detailed packet analysis when tcpdump is not enough.


Last updated: 24 July 2026

Written by Wyatt. For questions or feedback, visit wyattau.com.