What is a Computer Network? A Beginner's Guide to Networking in 2026

A computer network is any group of devices connected so they can exchange data. The internet is just the world's largest computer network — roughly 30 billion devices in 2026, all wired or wirelessly linked, all speaking the same set of protocols. Every time you load a webpage, send a message, or open a video call, dozens of routers, DNS servers, and TCP connections cooperate in milliseconds to make it feel instant.

This guide is for the developer who consumes APIs every day but has never been told how the bytes actually get from their laptop to a server in another country. By the end you will understand IP addresses, DNS, TCP, the network layers, and why "is the internet down?" is rarely the right question.

The Core Idea: Networks Are Just Wires Plus Rules

A network is two things:

• Physical links — Ethernet cables, Wi-Fi radios, fibre, mobile radios. These move bits.
• Protocols — agreed-upon rules for what those bits mean (where the destination is, how to retransmit a lost packet, how to encrypt the payload).

The genius of the internet is that anyone can plug into anyone, as long as both ends speak the same protocols. The links can change every five years; the protocols (IP, TCP, HTTP) have lasted decades.

Packets: How Data Actually Moves

Every piece of data on a network is broken into small chunks called packets. A packet has a header (where it is going, where it came from, sequence number) and a payload (the actual bytes). Packets travel independently — different packets in the same conversation can take different routes — and are reassembled at the other end.

This packet-switched design is why the internet survives broken cables: routers detect the failure and route around it. A circuit-switched design (like old phone lines) would simply die.

The Layered Model: Why Networking Is Sane

Networking is brutally complex, so engineers split it into layers — each layer only worries about its job and trusts the layer below.

When your browser hits rune.codes, HTTP rides on TCP, which rides on IP, which rides on Wi-Fi. Each layer is replaceable: switch from Wi-Fi to 5G and HTTP does not notice.

IP Addresses: Phone Numbers For Computers

Every device on a network has an IP address. IPv4 (e.g. 142.250.74.78) is the old format — 4.3 billion addresses, exhausted years ago. IPv6 (e.g. 2607:f8b0:4006:80a::200e) is the modern format — 340 undecillion addresses, plenty for every grain of sand to have one.

IP addresses are routable: routers across the internet know how to forward a packet toward a given IP. Behind the scenes, NAT (Network Address Translation) lets multiple devices on your home Wi-Fi share a single public IPv4 address — a hack that has kept IPv4 alive far longer than expected.

DNS: The Phonebook of the Internet

Humans cannot remember 142.250.74.78, so we use names like google.com. DNS (Domain Name System) is the distributed database that maps names to IP addresses. When you type a URL, your computer asks a DNS resolver, which asks the root servers, which answer with the IP. The whole thing usually takes 10–50 ms, and the result is cached so you do not pay it again.

DNS failures look like "the internet is broken" but usually mean "your DNS resolver is broken." This is why Cloudflare's 1.1.1.1 and Google's 8.8.8.8 are famous — they are reliable public DNS resolvers.

TCP and UDP: Two Ways to Deliver

Once IP knows where to send packets, the transport layer decides how reliably.

• TCP — connection-oriented, guarantees order and delivery, retransmits lost packets. Used by HTTP, SSH, email.
• UDP — fire-and-forget, no ordering, no retransmission. Faster, used by DNS, video calls, games, and the new HTTP/3 (which builds reliability on top of UDP via QUIC).

Pick TCP when correctness matters. Pick UDP when latency matters and you can tolerate (or recover from) a few lost packets.

A Worked Example: What Happens When You Load a Webpage

Type https://rune.codes and press Enter:

1. Your browser asks DNS for the IP of rune.codes.
2. The DNS resolver returns 203.0.113.42.
3. Your laptop sends a packet to that IP via Wi-Fi → home router → ISP → internet backbone → destination data centre.
4. A TCP three-way handshake establishes a connection.
5. A TLS handshake negotiates encryption keys.
6. Your browser sends GET / over the encrypted channel.
7. The server replies with HTML, CSS, and JS — typically split across many packets and routed independently.
8. Your browser parses, requests more resources (images, fonts), and renders the page.

All of that, on a fast connection in 2026, finishes in 200–600 ms.

Local vs Wide-Area Networks

Networks come in scales:

• LAN (Local Area Network) — your home Wi-Fi, your office Ethernet. Low latency (1 ms), high bandwidth (1+ Gbps).
• WAN (Wide Area Network) — across cities or continents. Higher latency (10–200 ms), still high bandwidth.
• The Internet — a planetary WAN of WANs, glued together by ISPs and routing protocols like BGP.

When you SSH into a server in another country, you are crossing all three.

Common Mistakes Beginners Make

• Confusing IP with MAC address. IP is the routable, internet-wide address. MAC is the physical link-layer address baked into your network card.
• Thinking DNS is HTTP. It is its own protocol, usually on UDP port 53, totally separate from web traffic.
• Forgetting NAT. A "public IP" your browser shows is your router's, not your laptop's. Inbound connections from the internet do not reach you without port forwarding.
• Misreading latency. Bandwidth is how fat the pipe is; latency is how long a packet takes to cross. A 1 Gbps satellite link still has 600 ms of latency.
• Ignoring TLS. Plain HTTP is dead in 2026. Browsers warn loudly. Use HTTPS everywhere — Let's Encrypt is free.

Quick Reference