A client of mine recently raised a great networking question while we were planning a new laptop build: what actually happens when a machine is already connected over WiFi and you then plug in Ethernet—whether that's a docking station, a USB dongle, or the built-in port? It's a classic "it depends" scenario, and it's the kind of WiFi vs LAN question that gets debated far more often than it gets tested. If you've ever wondered which connection your laptop prioritizes, the answer is worth verifying yourself rather than trusting secondhand claims.
Since I've worked with these guys for years, I skipped the diplomacy and got straight to the point. I told them I wasn't interested in theories they'd heard secondhand, read in a forum, or gotten from a vendor—my question was simply, "Have you personally tested this?" The answer, predictably, was no. That's usually how it goes with network interface questions: plenty of strong opinions, very little packet capture to back them up.
So I suggested we run a quick test ourselves and settle it. Cue the usual pushback about not having time, being too busy, and so on. I let them debate for about two minutes before cutting in with the obvious point: the time they'd spent avoiding the test could have been spent running it. I explained the whole thing would take a minute or two at most—and that measuring real behavior beats guessing every time.
That's exactly what we did. We fired up Wireshark, watched the live traffic, and got a concrete answer instead of a guess—along with a few handy Wireshark tips that came up along the way, which I captured in the accompanying video. Nothing beats observing the actual frames and interface behavior yourself when you're trying to understand how a laptop manages two active network paths at once, including how metrics and interface priority factor in.
The takeaway is simple: next time someone tells you how a machine "should" behave when WiFi and LAN are both connected, ask whether they've actually tested it. A couple of minutes with a packet analyzer will teach you more than an hour of hearsay—and you might pick up a Wireshark trick or two in the process. Testing it yourself is the fastest way to understand your own network setup.
