Overview

For B2B telecom engineers and network architects managing Optical Network Terminals (ONTs), accurately auditing the number of connected Wi-Fi clients is critical for capacity planning, security enforcement, and SLA compliance. This FAQ addresses high-intent pre-sales and post-sales queries regarding device count verification, CLI configuration, DHCP lease inspection, maximum client thresholds, and redundant power failover troubleshooting on enterprise-grade ONT platforms.

Frequently Asked Questions

Q1: How do I check how many devices are currently connected to my ONT Wi-Fi using the web GUI?

To check connected devices via the web GUI, log into the ONT management interface at its default gateway IP (typically 192.168.100.1 or 192.168.1.1), navigate to the WLAN or Wi-Fi Settings section, and select Associated Devices or Client List. This page displays the total count of active Wi-Fi clients along with their MAC addresses, IP assignments, RSSI signal strength, and connection duration in real time. For dual-band ONTs, verify both 2.4 GHz and 5 GHz client tables separately, as the dashboard may aggregate or split the count depending on firmware version.

Q2: What CLI commands can I use to count connected Wi-Fi devices on an ONT?

The primary CLI command to count connected Wi-Fi devices on an ONT is show wlan clients or show wifi station, depending on the vendor CLI syntax. For a precise count, pipe the output to a filter: show wlan clients | count or show wifi station | include MAC. On Broadcom-based ONTs, wl assoclist returns all associated MAC addresses, while brctl showmacs br0 lists MAC entries on the bridge interface. Always verify DHCP lease tables with show dhcp leases to cross-reference active leases against wireless associations and detect stale entries.

Q3: What is the maximum number of Wi-Fi devices an enterprise ONT can support?

The maximum number of Wi-Fi devices an enterprise ONT can support typically ranges from 64 to 256 concurrent clients, depending on the chipset and MIMO configuration. Carrier-grade ONTs with 4x4 MU-MIMO and Wi-Fi 6 (802.11ax) support up to 128 clients per radio band, while entry-level B2B models with 2x2 MIMO cap at 32 to 64 clients per band. Exceeding these thresholds causes association failures, DHCP pool exhaustion, and airtime fairness degradation; for high-density deployments, deploy additional access points or ONTs with higher client capacity and configure band steering to distribute load across 2.4 GHz and 5 GHz radios.

Q4: How do I verify connected device counts using DHCP lease and ARP tables on the ONT?

To verify connected device counts using DHCP lease and ARP tables, run show dhcp server leases to list all assigned IP addresses with corresponding MAC addresses and lease expiry times, then run show arp to confirm active Layer 3 reachability. The DHCP lease table provides the most reliable count of devices that have obtained network configuration, while the ARP table confirms which devices are actively communicating. Cross-reference both tables to identify devices that hold leases but are no longer associated with the Wi-Fi radio; these stale entries should be purged to maintain accurate capacity accounting.

Q5: Which optical module and transceiver types are compatible with ONT uplink ports for Wi-Fi backhaul?

The optical module compatibility for ONT uplink ports includes SFP, SFP+, and SFP28 form factors supporting 1G, 10G, and 25G line rates, with QSFP28 for 100G aggregation in higher-tier models. Third-party transceivers must comply with MSA (Multi-Source Agreement) standards and the ONT vendor's I2C EEPROM signature requirements; unsupported modules trigger show interface transceiver diagnostic failures and link-down states. For B2B deployments, always validate transceiver compatibility against the ONT firmware release notes and ensure the module's DOM (Digital Optical Monitoring) parameters are readable for proactive link health monitoring.

Q6: How do I configure stacking interfaces and redundant power failover on ONT platforms?

To configure stacking interfaces and redundant power failover, first verify that the ONT supports hardware stacking via dedicated stacking ports or 10G uplinks, then assign stack IDs and priorities using stack configuration commands. Redundant power failover is configured by installing dual AC or DC power supply modules and enabling the power redundancy feature in the system configuration; the ONT automatically switches to the backup PSU within 10-20 milliseconds of primary failure. Monitor PSU status with show power and verify failover events in the system log to ensure uninterrupted Wi-Fi service during power anomalies.

Q7: What are the differences between current-generation and previous-generation ONT Wi-Fi capacity and throughput?

Current-generation ONTs with Wi-Fi 6 deliver up to 3 Gbps aggregate throughput and support 128 clients per radio, compared to previous-generation Wi-Fi 5 models that cap at 1.7 Gbps and 64 clients per radio. The key architectural differences include OFDMA scheduling for multi-user efficiency, 1024-QAM modulation for higher spectral efficiency, and BSS Coloring for reduced interference in dense deployments. For B2B buyers, these generational improvements translate directly to higher device density support, lower latency for time-sensitive applications, and reduced total cost of ownership per connected client.

Q8: How do I troubleshoot devices that appear connected to ONT Wi-Fi but have no internet access?

To troubleshoot devices that show as connected but lack internet access, first verify the DHCP lease assignment and default gateway configuration on the client device, then check the ONT WAN status with show wan status and show route for proper default route installation. Common root causes include DHCP pool exhaustion, VLAN mismatches between the Wi-Fi SSID and WAN uplink, DNS resolution failures, and firewall ACLs blocking client traffic. Use ping and traceroute from the ONT CLI to isolate whether the fault lies in the Wi-Fi association, Layer 2 bridging, or Layer 3 routing domain.