Cloud storage killed the USB stick for most people, but there’s one flavour of thumb drive that deserves a revival: the pocket repair kit. An XDA piece recently made this case with four Windows-friendly picks, and it’s the right idea — it’s just aimed a bit too consumer for the homelab and small-business crowds. When a client site is half-down or your own rack is misbehaving, you don’t want to be downloading tools on the one connection you don’t trust. Here’s my version: what’s on the stick, and — the part everyone forgets — what’s in the pocket with it.
Carry it all with Ventoy
First, the container. The stick runs Ventoy, so it’s simultaneously a portable-apps drive and a multiboot installer: drop rescue ISOs (GParted Live, a Linux rescue image, memtest) next to the tools folders and boot any of them without re-flashing. One stick, every job. A 64GB drive is plenty; bigger just invites hoarding.
The software kit
Two of XDA’s picks make my cut unchanged, and I swap the rest for tools that answer the questions clients actually ask.
Wireshark Portable
Still the definitive answer to “what is this thing actually doing?” The classic move when a link feels slow: capture for sixty seconds, sort by bytes, and watch the backup job, the misbehaving smart TV, or the sync-happy app reveal itself. Portable runs without installing, which matters when you’re working on someone else’s machine and don’t want to leave footprints.
Nmap
The “is it even on the network?” tool. Two commands cover ninety percent of site visits:
nmap -sn 192.168.1.0/24
lists everything alive on the subnet — perfect for finding the smart plug that silently dropped off Wi-Fi — and
nmap -sV --top-ports 100 192.168.1.10
tells you what a mystery box is running and whether that IoT gadget is exposing more than it should. Before you pat yourself on the back for the closed ports, scan from outside too: the view from the LAN and the view from the internet are different audits.
iperf3
This is my first addition, and honestly the highest-value one. Clients don’t call saying “my TCP window scaling is suboptimal” — they say “it’s slow.” iperf3 splits that complaint in half in under a minute: run a server on the laptop, point the client at it from another device, and you learn whether the network is slow or the endpoint is. Wi-Fi that negotiates at 40Mbps, a flaky patch lead capping a gigabit run at 100 — iperf3 finds these while everyone’s still describing symptoms. Carry builds for Windows, macOS, and Linux; you’ll need all three.
mtr
Ping tells you a thing is down; mtr tells you where. It combines traceroute with continuous ping statistics, so instead of a single frozen path you get per-hop loss and latency over time. When the question is “us, the ISP, or them,” mtr answers it with evidence you can paste into a ticket. Run it for a few hundred cycles, not five.
dig
The XDA article suggests DNS Jumper for flipping between resolvers. It’s fine for consumer use, but dig gets you the truth without a GUI: query a specific server directly, chase the delegation chain, compare answers.
dig @1.1.1.1 example.com +trace
When “the internet is down” turns out to be one broken DNS record, this is the tool that finds it. It ships with BIND tools on Windows and everywhere else on Linux — no third-party download needed.
Where I differ from the original list
NetResView, the fourth pick, is a genuine throwback — SMB network browsing has been deprecated by Microsoft itself, and modern shares don’t announce themselves that way. If you need to inventory Windows shares and printers, nmap’s SMB scripts do it on any platform. A repair kit should be tools you trust on any box, not Windows XP-era utilities that half-work.
The hardware that rides in the same pocket
- A USB 3.0 ethernet adapter. Instant second NIC for laptop captures, and a known-good spare when a desktop’s onboard port is the suspect.
- A USB-serial console cable. The difference between a two-minute switch recovery and a drive to site. If you run any gear with a console port, this is non-negotiable.
- Two known-good patch leads and a coupler. Half of “the network is broken” is one bad lead in a wall of good ones. Yours are known-good because they’ve never left the bag.
- A phone with tethering. To download the driver you inevitably need, from a network that isn’t the patient.
Keep it honest
A repair kit rots quietly. Put a recurring calendar reminder to refresh it quarterly: update the tools, swap in current ISOs, and keep a plain-text manifest of what’s aboard. The worst time to discover your stick’s Wireshark is three years old is mid-outage, on a client’s machine, with no working internet.
Verdict
The XDA premise is right and the execution just needs a homelab accent: Ventoy for the container, Wireshark and Nmap as agreed, then iperf3, mtr, and dig — plus the physical bits that turn software into an actual repair kit. Old USB drives are free; a kit that saves one site visit pays for itself the first time you plug it in.