I swear WiFi is making me hate networking   

General Discussion
1

Been working as a network tech for about 2+ years now, and I usually vibe with the work.

Give me routing, VLANs, site-to-site VPNs, or sketchy firewall problems, and I’m happy to deal with it all day long.

But WiFi? I cannot stand it.

The guys on our team are solid — we can all deploy APs, configure controllers, and manage SSIDs or authentication with zero issues.

But as soon as we get a ticket like:

“My Teams calls keep dropping but my signal is great”

…we’re all just throwing darts in the dark.

RSSI looks solid, SNR is good, SIR is fine, and everyone else in the area is totally fine. But this one laptop is just throwing a tantrum.

Our only troubleshooting tool is a standard WiFi analyzer and site-survey app. It helps for spotting coverage gaps or interference, but once those check out, we’re completely stumped. Plus, management isn’t going to approve a budget for high-end wireless tooling anytime soon.

It’s crazy because I can sweat over a janky IPsec tunnel for hours and actually enjoy the grind.

I’ve been eyeing a move toward an ISP or network engineering role to get my hands dirty with BGP, OSPF, MPLS, and SD-WAN. Catch is, I live in a smaller city, so I’d likely have to pack up and move for a job like that.

Am I the only one who loves networking but absolutely loathes WiFi?

2

Every wireless engineer eventually discovers the premium enterprise technology known as a cable.Need low latency? Cable. Need consistent throughput? Cable. Need it to work during the CEO’s presentation without somebody asking why Mercury is in retrograde? Cable. Unfortunately users keep buying laptops without Ethernet ports, so here we are.

3

The annoying part is that good RSSI/SNR only tells you one piece of the story. I’ve had clients sitting at -50 dBm acting completely broken because of driver bugs, roaming decisions, power saving, authentication weirdness, whatever. That’s why WiFi troubleshooting feels way less deterministic than route/switch. Packet captures become your friend eventually.

4

What analyzer are you using? We use NetSpot for the RF side and it’s been useful for ruling out coverage/interference issues. Obviously it won’t tell you why one random laptop driver is losing its mind, but at least you can prove the wireless environment itself looks sane before you start digging into the client.

5

@Dilemma_Fixer That’s actually the one we use too. It’s good for surveys and checking the RF side, I just wish there was a magic “why is this one client broken” button lol. That’s the part that kills me. With routing I feel like if I keep tracing the path I’ll eventually find the thing that’s wrong. With WiFi I can prove coverage looks fine and still have no idea why this one laptop hates its life.

6

As someone who went the opposite direction and specialized in wireless: that’s actually the point where it starts getting interesting. The RF design is only half the job. 802.11 behavior, roaming, association/authentication, client capabilities, driver/firmware bugs, packet captures — once you understand those, the “random” problems become a lot less random. Good wireless engineers are harder to find than people who can configure an SSID.

7

One rule that saved my sanity: If one client is broken, suspect the client first. If one area is broken, suspect RF/design. If everyone is broken, start looking at infrastructure.

8

Don’t quit networking because one part of it pisses you off. After 20+ years I can assure you every specialization contains at least one technology specifically designed to make you question your career choices. You just haven’t met all of them yet.Don’t quit networking because one part of it pisses you off. After 20+ years I can assure you every specialization contains at least one technology specifically designed to make you question your career choices. You just haven’t met all of them yet.