Networking

Every time you press play on your wireless headphones, something remarkable happens beneath the surface. Your phone and headphones engage in a choreographed dance across the radio spectrum, switching frequencies up to 1,600 times every second. This is frequency hopping spread spectrum (FHSS), and it’s the reason your Bluetooth connection survives in a world crowded with Wi-Fi networks, microwave ovens, and billions of other wireless devices. The story of this technology traces back to a surprising origin: a Hollywood actress and an avant-garde composer. In 1942, Hedy Lamarr and George Antheil patented a “secret communication system” using frequency hopping to prevent radio-guided torpedoes from being jammed. The U.S. Navy initially dismissed their invention, but decades later, the same principle became fundamental to Bluetooth, Wi-Fi, and modern military communications. Lamarr’s contribution wasn’t the invention of frequency hopping itself—that had existed in various forms since the early 20th century—but her specific implementation using piano-roll mechanisms to synchronize hopping between transmitter and receiver. ...

In October 1986, something alarming happened on the Internet. Data throughput between Lawrence Berkeley Laboratory and UC Berkeley—sites separated by just 400 yards and two network hops—dropped from 32 Kbps to 40 bps. That is not a typo. The throughput collapsed by a factor of 1000. The Internet was experiencing its first “congestion collapse,” and nobody knew how to fix it. Van Jacobson, then at Lawrence Berkeley Laboratory, became fascinated by this catastrophic failure. His investigation led to a landmark 1988 paper titled “Congestion Avoidance and Control,” which introduced the fundamental algorithms that still govern how data flows through the Internet today. The story of TCP congestion control—from those desperate early fixes to modern algorithms like CUBIC and BBR—is really a story about how we learned to share a finite resource without a central coordinator. ...

On May 3, 1978, a Digital Equipment Corporation marketer named Gary Thuerk sent a message to 393 ARPANET users advertising a new computer system. The message generated $13 million in sales. It also created a permanent problem that would plague the internet for the next four decades: Thuerk had sent the first spam email. What made this possible wasn’t clever hacking or sophisticated exploitation. It was a fundamental design decision built into email itself—a protocol that assumed everyone on the network could be trusted. When Jonathan Postel published RFC 821 in August 1982, defining the Simple Mail Transfer Protocol (SMTP), he created a system where the sender’s identity was entirely self-declared. Any mail server could claim to be sending from any address, and receiving servers had no way to verify it. ...

On February 24, 2008, at 18:47 UTC, Pakistan Telecom (AS17557) started announcing a more specific route to YouTube’s IP prefix: 208.65.153.0/24. Within minutes, YouTube traffic from around the world was being redirected to Pakistan. The Pakistan government had ordered the ISP to block YouTube domestically, but a configuration error caused the route to propagate globally through PCCW Global (AS3491), their upstream provider. YouTube engineers responded approximately 80 minutes later by announcing even more specific routes (/25 prefixes) to reclaim their traffic. By 21:01 UTC, the hijack was over. But for nearly two hours, a single misconfiguration in one country had effectively stolen one of the world’s most popular websites. ...

The coffee shop has free Wi-Fi. The password is posted on a chalkboard near the counter. You sit in the corner booth, open your laptop, and connect. The signal passes through three walls, a glass window, and a wooden partition before reaching your device. How? This isn’t a minor engineering achievement. Your router is broadcasting radio waves at frequencies measured in billions of cycles per second, encoding gigabytes of data into invisible electromagnetic fields, and somehow that signal arrives intact after bouncing off your refrigerator, penetrating your walls, and competing with your neighbor’s network. Understanding how this works requires peeling back layers of physics that most people never consider—electromagnetic wave behavior, material properties, and the mathematical cleverness of modern encoding schemes. ...

A file sits on disk. Your application reads it and sends it over the network. Simple enough—but behind this mundane operation hides one of computing’s most persistent performance bottlenecks. In a traditional I/O path, that single file traverses through four distinct memory copies before reaching the network interface. The kernel reads data from disk into a kernel buffer via DMA. The read() system call copies it to user space. The write() system call copies it back to a kernel socket buffer. Finally, DMA transfers it to the NIC. Each copy consumes CPU cycles, memory bandwidth, and cache space. ...

The padlock icon in your browser’s address bar suggests something simple: this connection is secure. But in the roughly 100 milliseconds between clicking a link and seeing the page, your browser and the server performed one of the most sophisticated cryptographic dances in computing history. They established a shared secret over a public network, verified each other’s identities, and set up encrypted communication—all while an attacker watching every packet could learn nothing useful. ...