WiFi · Networking
WAP
Also known as: Wireless Access Point, Access Point, AP
The device that creates a Wi-Fi network — bridges wireless clients to the wired Ethernet infrastructure and is managed individually or via a controller.
An access point does one job: it translates between wireless (Wi-Fi) and wired (Ethernet) communication. Wireless clients associate with the AP, and the AP forwards their traffic over its Ethernet uplink to the network.
Standalone vs controller-managed
Standalone APs — configured individually via web interface or CLI. Fine for very small deployments (1–3 APs in a small office) but don't scale. No central visibility, no coordinated channel management.
Controller-managed APs — a central controller (physical or cloud) manages all APs as a fleet. Channel selection, power, client roaming, RF optimization, and firmware updates are all managed centrally. The right choice for any deployment with more than a handful of APs. UniFi, Cisco Meraki, Aruba, and Ruckus all follow this model.
Powering APs
APs are almost universally powered via PoE — a PoE switch port or injector powers the AP over the Ethernet cable, eliminating the need for a power outlet at the ceiling. This is one of the primary use cases driving PoE+ adoption; modern dual-radio 6E APs may need 25W or more.
AP placement and density
AP coverage is a balance between coverage area (fewer APs, more power, wider range) and capacity (more APs, lower power, each AP serves fewer clients more efficiently). In a high-density environment, the goal is usually capacity rather than coverage — more APs operating at lower transmit power, each serving a smaller area with better per-client performance.