What Is A Wi-Fi Controller?
A Wi-Fi Access Point (AP) can operate as a stand alone device, in which case it's known as an Autonomous AP or it can be managed by a device known as a Wi-Fi Controller.
Before exploring the benefits of Wi-Fi controllers it's best to look at the limitations of Autonomous Access Points.
Autonomous Access Points can perform encryption, if a user associates (connects) with an AP that requires traffic be encrypted, the user will be asked to supply the encryption key (passphrase) and if it matches the key configured on the AP, the user can now send encrypted traffic back and forth between himself and the AP. Encryption is an option, traffic could also be sent "in the clear" as is the custom at public hotspots, etc. These days encryption is done using the AES algorithm for very strong encryption.
This pretty much sums up what an autonomous AP can do. Here's what an Autonomous AP can't do:
- It can't hand off a connection to a neighboring AP (roaming)
- It can't employ encryption where each user has a unique encryption key
- It can't ask users to authenticate, ie: ask for username and password
- It can't act in concert with other APs to adjust power levels
- It can't act in concert with other APs to adjust channel assignments
- It can't authenticate users against an external database, ie: RADIUS
- It can't report interference to a centralized management device
- It can't report rogue access points to a centralized management device
- It can't report rogue DHCP servers to a centralized management device
- It can't launch countermeasures when threats are active
- It can't send traffic to a neighboring AP if it's network connection is lost
- It can't participate in a Mesh network
- It can't find RFID tags through triangulation
- It can't log events to a Syslog server
- It can't send SNMP traps
- It can't identify brute force password attacks
- It can't receive firmware upgrades from a centralized server
- It can't filter traffic based on TCP ports
- It can't filter traffic based on IP addresses
- It can't filter traffic based on MAC address
- It can't restrict user traffic based on their roles in the company
- It can't restrict traffic based on WLAN
- It can't deliver statistics and information to a NMS (requires FlexMaster)
- It can't track who the most active stations are
- It can't track frames being retransmitted
- It can't redirect users to a web page for authentication
- It can't report the speeds each user is getting from the AP
- It can't grant guest access to temporary users
- It can't revoke a users login credentials
- It can't support more than 8 WLANs
- It can't email critical events to the administrator
- It can't place WLANs into WLAN groups for ease of administration
- It can't forward user connection details to other APs
- It can't load balance users across adjacent APs
- It can't receive ACL policy changes from a centralized server
- It can't disconnect and ban users from the network
- It can't throttle bandwidth usage on a per WLAN basis
This is just a partial list of things that require a WLAN controller in order to achieve. The controller is the centralized "brains" of the Wi-Fi network. Controllers can also be configured in failover pairs for fault tolerance. Even with a single AP, having a controller is almost mandatory.





Sabertech Wireless