edubun
English

What the internet is

Wiring 10 computers directly to each other takes 45 cables. The internet gets around that with switches and routers.

Say you are on the subway and send a photo to a friend who is at home. (This is a made-up example.) Your phone passes the photo to the mobile network. Your friend's phone picks it up from the Wi-Fi router in the living room. In between, the photo crosses machines that belong to several different companies, and nobody worked out that exact route in advance. It arrives anyway. To see how, start with a much smaller network.

Ten computers, forty-five cables

Two computers can talk over one cable or one wireless link. Now try ten, and give every computer its own cable to every other one. MDN's guide to how the internet works counts the cost: 45 cables, with nine plugs on each computer. The sum is 10 × 9 ÷ 2. Each machine needs a line to the nine others, and you halve the total because every cable has two ends. With 20 computers the same sum gives 190. The count grows roughly with the square of the number of machines, so nobody builds a network this way.

The usual fix is a small computer called a switch. Each machine gets one cable to the switch, so ten computers need ten cables, and the switch passes every message to the right machine. It tells them apart by MAC address, a number fixed to the network hardware. Inside one building that works well. A switch that had to remember every device on Earth would not.

The box at home links your network to everyone else's

Between networks the job goes to routers. A router reads a different kind of address, the IP address, which works more like a street address: it says which network a device belongs to. That lets a router keep one rule for a whole group of addresses instead of one rule per device. The router in your home links your home network to an internet service provider (ISP), and ISPs link their routers to each other's. The internet is that whole mesh of joined networks. That is why people call it a network of networks.

A photo leaves in pieces

An old telephone call held one complete line between two phones for as long as the call lasted, silences included. The internet does something else. Data is cut into small pieces called packets, and each packet carries the address it is going to. Packets from millions of people take turns on the same cables. If one goes missing, only that piece has to be sent again. If a route breaks, the rest can go another way. The name for this is packet switching.

Loading

Drag to turn. Scroll or pinch to zoom.

Press Send. The message is cut into four packets, numbered 1 to 4. They leave the laptop one after another, may take different routes through R1 to R5, and can reach the server out of order. The server puts them back in order. Tap a moving packet to read its header.

Watch the packet numbers as they land. Packets on the faster lower route can overtake the ones on the upper route. Now use the menu to cut a link and send again: the routers steer everything around the gap. Cut the link between R5 and the server, though, and nothing gets through. The server has only that one connection.

The internet is not the web

One more distinction before the history. The internet and the web are not the same thing. The internet is the set of connected networks. The web is one service that runs on top of it, where web servers send pages to web browsers. Email, video calls and online games are other services on the same networks. A chat app or a game can use the internet all day without opening a single web page.

BackgroundOn 29 October 1969 at 22:30, Charley Kline, a student working with Professor Leonard Kleinrock at UCLA, tried to log in to a computer at the Stanford Research Institute over the new ARPANET. He meant to type "login". The letters L and O went through, and then the system crashed. So the first message on the network that grew into the internet was "LO". About an hour later the full login worked. On 1 January 1983 the ARPANET switched to the TCP/IP protocols that the internet still uses.
  • 1969: First ARPANET message, "LO", UCLA to SRI
  • 1980: UDP described in RFC 768
  • 1981: IPv4 described in RFC 791
  • 1983: ARPANET switches to TCP/IP on 1 January
  • 1987: DNS standards RFC 1034 and RFC 1035
  • 2011: IANA hands out its last free IPv4 blocks on 3 February
  • 2017: IPv6 published as RFC 8200
  1. How many cables does it take to join 10 computers so that every pair has its own cable?
  2. And for 20 computers?
  3. With one switch in the middle, how many cables do 10 computers need?
  4. What does a router join together?
    • Separate networks
    • A keyboard and a screen
    • Two programs on one computer
    • Web pages to each other
  5. Which sentence is true?
    • The web is a service that runs on the internet
    • The internet is one program inside the web
    • Email needs the web to work
    • The internet and the web are two names for one thing
  6. What is packet switching?
    • Cutting data into addressed pieces that share the links
    • Reserving one whole line for each conversation
    • Swapping broken cables for new ones
    • Sending every message twice
  7. Why is it useful to cut a big file into packets?
    • A lost piece can be resent alone, and packets can go around a broken link
    • The file becomes smaller
    • Nobody can read packets
    • Packets never get lost
  8. What two letters made up the first ARPANET message in 1969?
  9. In which year did the ARPANET switch to TCP/IP?
  10. In the simulator the packets reached the server out of order. How does the server rebuild the message?
    • By the sequence number in each packet
    • By the colour of the packet
    • By the time on the server clock
    • It cannot
Common mistakes
  • "The internet and the web are the same thing." The internet is the connected networks. The web is one service on top of them, where servers send pages to browsers. Email, video calls and games use the same networks and are not part of the web.
  • "When I send a photo, my phone opens a line straight to my friend's phone." That is how old telephone calls worked, and it is called circuit switching. The internet cuts the photo into packets, and each packet finds its own way while sharing the cables with everyone else's packets.
  • "Full Wi-Fi bars mean the internet is working." Wi-Fi is only the short wireless hop between your device and the router. Full bars say that hop is fine. If the router's link to the ISP is down, pages still will not load.
Teacher's noteStart at the board, not with definitions. Draw four computers and join every pair: six lines. Then ask how many lines ten computers would need, and let the class work toward 45 before you show the switch. The switch and the router are the pair that gets mixed up, and one sentence settles it for most learners: a switch joins machines inside one network, a router joins networks. The internet and the web come next. The quickest test is to name something that uses the internet without a web page, such as an online game.
Key points
  • The internet is many networks joined by routers.
  • Switches connect machines in one local network by MAC address; routers forward between networks by IP address.
  • Data travels as packets that share links and can take different routes.
  • The web, email and games are services that run on the internet.
Sources for this course (28)
  • (checked 2026-10-17; reordered 2026-10-19: standards first, then official documentation, then operators and papers, history sources last)
  • IETF RFCs (rfc-editor.org): RFC 768 UDP (1980, 8-byte header)
  • RFC 791 IPv4 (1981, 32-bit addresses, "does not provide a reliable communication facility", TTL field "measured in units of seconds" but every module must decrease it by at least one, so it is only an upper bound)
  • RFC 792 ICMP (Time Exceeded)
  • RFC 801 NCP/TCP transition plan (1 January 1983)
  • RFC 894 Ethernet (1500-byte payload)
  • RFC 1034 and RFC 1035 DNS (1987, HOSTS.TXT kept by SRI-NIC, labels up to 63 octets and names up to 255, TTL in seconds)
  • RFC 1122 (127.0.0.0/8 loopback)
  • RFC 1918 private addresses (10/8, 172.16/12, 192.168/16)
  • RFC 2131 DHCP, RFC 3022 NAT, RFC 3596 AAAA records, RFC 3849 and RFC 5737 documentation addresses, RFC 4271 BGP-4, RFC 4291 IPv6 text form, RFC 6298 TCP retransmission timer (initial RTO 1 second)
  • RFC 6335 port ranges (0-1023, 1024-49151, 49152-65535)
  • RFC 7766 DNS over TCP, RFC 8200 IPv6 (128-bit addresses, Hop Limit)
  • RFC 8446 TLS 1.3 (one round-trip handshake)
  • RFC 9000 QUIC and RFC 9114 HTTP/3, RFC 9110 HTTP semantics (status code classes)
  • RFC 9293 TCP (three-way handshake, sequence numbers)
  • IANA: ip-parameters registry (recommended default TTL 64)
  • IPv4 free pool depleted 3 February 2011 (NRO and ARIN announcements)
  • Official documentation: MDN Web Docs "How does the Internet work?" (45 cables for 10 computers, switches, routers, MAC and IP addresses, internet and web)
  • "What is a URL?", "HTTP response status codes" (developer.mozilla.org)
  • Cloudflare Learning Center: "What is DNS?" (four kinds of DNS server, 8 steps of an uncached lookup, browser and OS caches, TTL)
  • "What is HTTP/3?" (cloudflare.com/learning)
  • Google Chrome Help, "Browse in Incognito mode" (support.google.com/chrome/answer/95464, checked 2026-10-19: Incognito limits what is saved to the device; websites and organisations that manage your network, like your school, employer or internet service provider, may be able to observe your activity)
  • Operators and papers: root-servers.org (13 root name servers run by 12 organisations, 2047 instances on 2026-10-17)
  • Jacobson and Karels 1988, Congestion Avoidance and Control (loss mostly congestion)
  • History blocks only: UCLA Samueli School of Engineering, Internet50 (first ARPANET message "LO", UCLA to SRI, 29 October 1969, 22:30)
  • historyofinformation.com and Wikipedia ARPANET (Kline)
  • Spiceworks/SRI history (HOSTS.TXT kept by SRI-NIC)
  • Numbers (2^32, 2^96, 45 and 6 cables, packet counts, round-trip times)

Checked: 2026-10-17