How a Dorm‑Room Network Hack Triggered a VLAN Storm and What It Reveals About Ethernet Loops

Shortly after starting university, the author faced a common dorm problem: noisy roommates staying up late playing games on laptops while the lights were off. With only a Nokia slide phone and no hardware, he decided to use a simple technical trick to cut off network access.

He discovered that the dorm’s Ethernet infrastructure was shared across hundreds of rooms, with no VLAN segmentation. By repurposing a spare four‑pair Ethernet cable from a set‑top‑box installation, he connected two separate cable pairs together, effectively creating a loop.

The loop caused a broadcast storm: the switch repeatedly forwarded broadcast packets between its two ports, saturating the backbone bandwidth. The author explains that this happens because switches forward broadcast frames to all interfaces, and a loop causes endless circulation until the Spanning Tree Protocol (STP) detects and blocks the loop.

Why does plugging a cable into two ports of a switch cause a storm? Because the switch forwards broadcast packets to every interface; if two interfaces form a loop, broadcasts circulate indefinitely, exhausting bandwidth. STP exists to detect and break such loops.

After the initial experiment, the author refined the setup: he trimmed the cable, concealed it behind furniture, and created a hidden “switch” that could be engaged or disengaged by pressing a foot‑controlled elastic switch hidden in a sock.

Various iterations (v1, v2) improved reliability, but occasional mishaps—such as a maintenance worker discovering the dangling cable—highlighted the need for a more discreet, automatic solution.

Ultimately, the story illustrates practical networking fundamentals, the dangers of unmanaged Ethernet loops, and creative (though mischievous) ways to control a shared LAN without dedicated hardware.