I'm a quality and brand compliance manager at a cable manufacturer. I review roughly 200+ cable SKUs a year, and I've rejected my share of first runs because the jacket print was off by a decimal. That job has taught me to be precise, but it's also taught me that precision matters more in some places than others.
When someone searches 'what is on my wifi,' they usually expect a list of connected devices. I hear it differently. After four years of inspecting cable before it ships, I know that the devices on your WiFi are only half the story. The other half is the cabling you don't see.
So here's the honest answer: there is no one-size-fits-all answer. Your situation probably falls into one of three buckets.
- You have an installed network that's slow or flaky.
- You're planning a new install and need to choose the right cable.
- You suspect something unknown has connected to your WiFi.
Each scenario points to a different next step. Let's walk through them.
Scenario 1: The Network Is Already Installed And It's Slow
If the network is already in place, start by identifying what's connected. Log into your access point or router and look at the client list. If you have a managed switch, check its ARP table. That tells you which devices are on the WiFi, but it doesn't tell you why the connection is bad.
This is where I see a lot of blaming the wrong thing. People assume the WiFi radio is weak, but the bottleneck is often the wired backhaul. Access points need a cable that can handle the data rate. If the backhaul is old Cat5e or damaged cabling, your 1 Gbps link becomes 100 Mbps, and no amount of WiFi tweaking will fix it.
In my first year, I made the classic specification error: I assumed 'network cable' was network cable. I didn't verify the jacket rating. On a factory rooftop, that mistake led to a cracked jacket and a $14,000 re-pull. Now I check everything—including the cable that feeds the access point.
I also once told a vendor 'as soon as possible,' and they heard 'whenever convenient.' Result: the cable shipment arrived two weeks after the access points were installed. That's on me. I should have said 'by March 15, on a skid, with a spec sheet.'
If your device list looks normal but performance is still poor, inspect the cable path. Look for damaged jackets, rusted connectors, and runs longer than the spec allows. Sometimes the problem is a cable that has been in service for years and simply reached its limit.
A WiFi analyzer can help, but don't stop at signal strength. A strong signal can still have bad throughput if the channel is crowded. That's a configuration issue, not a cable issue. If your cable backhaul is fine, then yes, tweak the channels. But check the cable first—it's cheaper to inspect than to replace an access point.
Scenario 2: You're Specifying New Cable And Want To Get It Right
If you're in the planning stage, the question shifts from 'what is on my wifi' to 'what's feeding my WiFi.' The best advice depends on the environment.
For clean offices and data centers, Cat6A or fiber is the safe call. For industrial environments with cable trays, motors, and control panels, you need cables rated for that world. General Cable VNTC is a workhorse for control and tray cable applications, but it isn't an Ethernet cable. Don't use it to link an access point. Use it for the control circuits that keep the building alive, and use a properly rated industrial Ethernet cable for data.
General Cable Corp—now part of Prysmian Group—has been making wire and cable for well over a century. The VNTC line is one example of a product built for a specific job. When people search 'general cable vntc,' they're usually looking for a replacement or a spec confirmation. The right answer is: check the print legend, check the temperature rating, and don't substitute a generic 'tray rated' cable if the spec says VNTC.
I once ran the numbers for a facility expansion and the spreadsheet said Cat6A for every backbone link. My gut said some of those runs would need fiber. The spreadsheet won. We re-pulled three links later at double the time. My gut wasn't magic—it just knew the cable path had heat, bends, and future capacity issues the spreadsheet didn't model. So when you're choosing cable, look at the route, not just the chart.
When someone asks me to recommend a cable without telling me the route, I usually say: 'How old is the building? Is there a ceiling plenum? Any fire rating requirements? What's the distance from the IDF to the AP?' The right cable depends on those answers. A cheap cable in a hard environment is not cheap.
A Word About 'Cat 7.1'
While I'm on the topic of specs: 'Cat 7.1' is not a recognized TIA category. Category 7 and Category 7A are real standards, but there is no '7.1' in the official spec. If you see 'Cat 7.1' on a product, ask the seller to point to the standard. Per FTC guidance, technical claims have to be truthful and substantiated—and a marketing group's name is not a standard.
If a vendor tells you 'Cat 7.1 is the new thing,' take it with a grain of salt. I'm not 100% sure where that term started, but I do not use it in any spec I approve. The recognized categories are Cat5e, Cat6, Cat6A, Cat7, and Cat7A. If someone uses a number that isn't in the standard, ask for the test report.
Scenario 3: You Suspect Unwanted Devices
If you're asking 'what is on my wifi' because you're worried about freeloaders or intruders, that's a security problem, not a bandwidth problem. Start by changing the admin password on the router, making sure WPA3 or at least WPA2 is enabled, and looking at the DHCP client list for unknown MAC addresses. Run a scan with a phone app if you want a second opinion.
Please don't dismiss a small network because 'it's only a few devices.' I've watched a customer grow from a $200 cable order to a $20,000 order over four years. The vendors who treated the first order seriously are the ones they still call. Small doesn't mean unimportant—it means potential. The same logic applies to network security: a small network can still be the back door to a larger system.
If you find a device you don't recognize, don't just disconnect it. Change your passphrase, set up guest network isolation, and make sure smart devices are on a separate VLAN if possible. Then ask why it got on in the first place. The answer is usually a default password or an open management port.
How To Tell Which Scenario You're In
Still not sure? Ask yourself three questions:
- Is the network already installed and slow? Start with Scenario 1.
- Are you choosing cable for a new build or upgrade? Start with Scenario 2.
- Are you worried about devices you didn't add? Start with Scenario 3.
And if you're staring at a spec sheet and don't know whether you need General Cable VNTC, Cat6A, fiber, or something else, get an engineer involved before you buy. Guessing is expensive. I do not guess when a re-pull costs more than the cable itself.
