So, you're staring at your router's admin page, or maybe you got a notification from a network monitoring app that says 'New device detected: UNKNOWN,' and now you've got that cold feeling in your stomach. What's on my WiFi?
The short answer? It depends. And if you're managing a network that involves Adtran gear—like an 834-5 ONT or a 452 switch—the answer is a little more nuanced than just logging into your consumer router's app. I've been on the receiving end of this panic in my role managing service delivery for a mid-sized ISP. In March 2024, a client called at 10 PM on a Friday because their network was 'slow.' Turns out, someone had plugged a rogue access point into a conference room, and it was acting as a DHCP server. That took six hours to troubleshoot.
This guide is about helping you identify what is actually on your network, and it breaks down into three common scenarios. There's no universal answer; it depends entirely on your setup, your access, and your tolerance for complexity.
Scenario A: The 'I Only Have a Consumer Router' User
This is the simplest case. You have one box provided by your ISP (which might be an Adtran ONT with a built-in router, like a model from the Total Access family, or a simple ONT feeding a third-party router).
The Easy Way: Most modern consumer routers have an app (e.g., ASUS Router app, Netgear Nighthawk app, TP-Link Tether) that shows you connected devices. Log in, and you'll see a list of IP addresses, MAC addresses, and a 'Friendly Name.' The friendly name is usually enough. 'iPhone-12-Pro' is obvious. 'Living-Room-TV' is obvious. 'ESP_3F2A' is a lightbulb or a sensor.
The Problem: The friendly name is a lie. Any device can claim any name. I've seen a malicious device label itself 'Guest-HP-Printer.' Don't trust the name blindly. Check the IP address and the MAC address vendor prefix (the first 6 characters). If you see 'Samsung' or 'Apple,' that's usually legit. If you see 'Unknown' or 'Gigabyte,' and you don't own a Gigabyte motherboard, that's a red flag. Put another way: trust the MAC vendor, not the name.
What if you have an Adtran ONT (like the 834-5) with a separate router?
Your ONT isn't the router. Log into your router. If you can't find the device in the router's list, it might be connected behind the ONT, on the ISP's side. (Should mention: this is rare for home users, but common in business setups.) If you see an IP address that starts with something like 10.0.0.x that isn't your router's range, you have an issue.
Scenario B: The 'I Have a Business-Grade Network (Adtran 452, 834-5, SDX)' User
This is where things get interesting. You're not just asking 'what's on my wifi'; you're asking 'what's on my network.' The 'what's on my wifi' question is a subset. You likely have Adtran switches like the 452 series, 834-5 ONTs, maybe an SDX 6000 for management.
The Right Way (but requires access): You need to access your network management interface.
- If you have a CPE device (like the 834-5): Log in via SSH or HTTP. The command
show lldp neighborsis your best friend. LLDP tells you what devices are directly connected to the switch port. For the 834-5 specifically, you can check its DHCP client list on the web UI (usually under Status -> Network). - If you have a managed switch (like the 452): Use
show mac-address-tableto see all learned MAC addresses. Cross-reference with the port. That's your device map. If I'm remembering correctly, the '452' series handles this well. - If you have SDX: The dashboard will show you a list of every device that's been given an IP. You can also run a 'ping scan' or 'SNMP poll' from the SDX server.
The Hard Way (but the most accurate): Pick a single endpoint (like a laptop) and run arp -a from the command line. This shows the ARP table of that device. It lists IPs and MACs. Then, compare that list with the list on your switch. Anything that's on the switch but not in your laptop's ARP table is a device that's communicating but maybe not with you—that's a potential problem.
I can only speak to domestic setups. If you're dealing with a multi-site MPLS network with different VLANs, your 'what's on my wifi' question is meaningless. Your 'what's on my VLAN 20' question is what matters.
Scenario C: The 'I Just See 'Unknown' Devices' Panic
This is the most common email I get from junior network engineers. They see a new device called 'Unknown' on their Adtran network. Panic ensues.
What it usually is (and why your ONT might be the culprit):
- Your ISP's ONT. The Adtran 834-5 itself might be appearing as a device. Some configurations allow it to get an IP from the upstream. It's usually called 'Adtran' or 'ONT.' That's fine.
- A managed switch that's not configured. You plugged in a new 452 switch, but didn't set an IP. It defaults to 192.168.1.x or gets an IP via DHCP. It shows up as an unknown device. (Oh, and I should add: its default credentials might be admin/admin, so fix that immediately.)
- A VoIP phone. You mentioned 'phones.' An Adtran G100 gateway will do this. It'll show up as a generic SIP device.
- A rogue device. This is the one you're worried about. But 9 times out of 10, it's a printer or a guest's phone that you forgot about.
How to tell the difference: Look at the MAC address. If it starts with 00-13-1A (Adtran's OUI), it's an Adtran device. If it starts with 00-11-5C (Broadcom), it's a chipset. These are safe. If it starts with a Chinese vendor that you don't recognize, and it's on a 'guest' SSID, it's suspicious. Use a MAC address lookup tool (like Wireshark's OUI lookup).
So, Which Scenario Are You?
If you're thinking 'I just need to know what devices are on my network,' you're probably Scenario A. If you're an IT manager for a company that has an Adtran network and you're fielding 'what's on my wifi' calls from users, treat it as a security incident. Tell them, 'I can see your device's MAC address. Is it a Samsung phone or a Lenovo laptop?' If they say 'I don't know,' ask them to check the sticker. That's not being a dick; that's verifying identity. The certainty of knowing the device is worth more than the panic of a 'new unknown device' notification.
I only believed in the power of a definitive MAC-based check after ignoring it. In Q3 2023, we chased a 'rogue' device for three days. It was a new smart TV. The MAC was a Korean vendor we didn't recognize. We wasted $800 in labor. Looking back, I should have just checked the MAC. At the time, the user said 'I didn't add any new devices.' He had. The TV was two days old.
Prices as of May 2024: A decent MAC lookup API is about $10-20/month. Using Wireshark is free. Your internal labor rate is probably $100+/hour. Do the math on that 'what's on my wifi' question before you escalate it.
