Pakkit.net
← Back to blog

Infrastructure

Put a Managed Switch on Your Desk

A cheap managed switch on your desk turns a single network drop into as many isolated VLANs as you need — which means you can rehearse real network topology, segment your lab gear, and stop testing multi-network behavior by imagining it.

  • Infrastructure
  • Networking
  • Homelab
  • Testing

For a long time my bench had exactly one network: whatever the wall drop handed me, everything plugged into a dumb switch, one flat subnet. Every time I needed to test something that involved more than one network — a device on an isolated segment, traffic crossing a VLAN boundary, a lab that shouldn’t be able to reach the rest of the house — I’d either fake it, skip it, or go beg for a real environment. Then I put a small managed switch on my desk, and a whole category of “I can’t really test that here” quietly disappeared.

One drop, many networks

A managed switch — even a cheap one — does the thing a dumb switch can’t: VLANs. It takes your single uplink and lets you carve the ports into as many isolated Layer 2 segments as you want, trunk multiple VLANs down one cable, and decide exactly what can talk to what. My desk went from “one network” to “as many networks as I feel like defining,” without a single extra wall drop or a call to anyone.

A managed switch turns your desk from a single network into a patch panel for whatever topology you’re trying to reproduce.

That’s a bigger deal than it sounds, because so much of infrastructure work is about the boundaries between networks — what’s segmented from what, which VLAN a device lands on, how traffic crosses (or doesn’t). If your bench only has one network, you literally cannot rehearse the part that matters. A managed switch gives you the boundaries to rehearse against.

Rehearse the topology instead of imagining it

The payoff is the same one I keep coming back to with a homelab: you learn systems by running them, not by reading about them. With VLANs at the desk I can stand up a segment that mirrors how a thing will actually be deployed — an isolated network for the gear under test, a separate management network, a trunk carrying both — and find out how it behaves before it’s somewhere I can’t poke at it. Does the device come up on the right VLAN? Does it get an address where I expect? Can it reach only what it’s supposed to? Those are questions you answer by building the topology, and now the topology fits on your desk.

It’s the network-layer version of building the rehearsal instead of extrapolating: a segmented bench is a small, safe stand-in for the real multi-network world, and it catches the “oh, that doesn’t work across the boundary” surprises early.

Segment your lab off from everything else

There’s a safety dividend too. Lab gear is, by definition, half-broken, experimental, and occasionally doing something obnoxious to the network — a rogue DHCP server, a flood of traffic, a device firmware you don’t fully trust. On a flat network, that mess is everyone’s problem. Behind a VLAN on a managed switch, the blast radius stops at the boundary you drew. You get to break things in a fenced-off segment instead of on the network everyone else (or every other device in your home) depends on. That isolation is the same instinct as putting untrusted things on their own segment anywhere else — it’s just applied to your own bench.

Treat the switch itself as infrastructure

One honest caveat: a managed switch is a small piece of infrastructure, which means it has config that matters and can bite you. Its VLAN setup, its management access, its uplink — get those wrong and you can cut off your own network or leak segments into each other. So it earns the same care as anything else that carries a network: know its config, don’t fat-finger the port that’s holding up your uplink, and treat “how is this switch set up” as a real question, not a set-and-forget. It’s a tiny router with opinions, and respecting that keeps it an asset instead of a foot-gun.

None of this requires a rack or a budget — a small managed switch is cheap, and it’s one of the highest-leverage things you can add to a bench, because it upgrades your lab from “a network” to “networks, plural, arranged however the problem needs.” The moment you can reproduce a boundary at your desk, a lot of infrastructure stops being abstract. If you’ve built out a segmented bench and found it changed what you could learn at home, I’d love to hear how you set it up.