Controller-based Wi-Fi — where the tunnel ends
In a controller-based wireless network the 802.11 MAC layer is split between the access point and a central controller, and one design choice — where client traffic leaves the tunnel — decides whether an AP's switchport is an access port or a trunk. This chapter covers that split, the CAPWAP control and data tunnels, the jobs an AP's radio can be given, how a controller plugs into the wired network, channel-width planning, and what a wireless network profile decides.
What you'll learn
- Split 802.11 responsibilities between a controller-based AP and its controller.
- Describe the CAPWAP control and data tunnels and the ports they use.
- Match a requirement to a radio role: serve clients (centrally or locally switched), monitor the air, capture frames, or carry mesh backhaul.
- Decide whether a given AP needs an access port or an 802.1Q trunk, and say why.
- Describe how a controller attaches to the wired network: a management address, client VLANs on a trunked uplink, an optional out-of-band port, and link aggregation.
- Plan 2.4 GHz channels and 5 GHz channel widths for coverage versus capacity.
Split-MAC — who does what
A controller-based AP is not a dumb radio and it is not a self-contained access point either. The 802.11 MAC layer is split in two. The AP keeps every job that has to complete in microseconds: sending beacons and probe responses, acknowledging frames, retrying failed transmissions, buffering for power-save clients, and encrypting or decrypting the data as it crosses the air.
The controller keeps every job that can survive a round trip across the wired network: association and re-association, 802.1X/EAP authentication and key management, roaming, radio resource management (which channel and how much power each AP uses), and the security, QoS and VLAN policy attached to each wireless network. That split is why one change on the controller reaches two hundred APs at once — and why a controller outage does not instantly silence a radio.
| Function | Handled by |
|---|---|
| Beacons, probe responses, 802.11 ACKs, retries | AP — real-time MAC |
| Frame buffering and power-save delivery | AP — real-time MAC |
| Over-the-air encryption / decryption | AP — real-time MAC |
| Association, re-association, disassociation | Controller |
| 802.1X / EAP authentication and key management | Controller |
| Channel and transmit-power assignment (RRM) | Controller |
| Per-WLAN security, QoS, and VLAN mapping | Controller |
CAPWAP — two tunnels, not one
An AP discovers a controller (from DHCP option 43, a DNS record, a broadcast on its own subnet, or a controller it has joined before), then builds a CAPWAP tunnel to it. CAPWAP is the IETF standard (RFC 5415) for this AP-to-controller conversation.
There are two tunnels, not one. The control tunnel runs over UDP 5246 and carries AP configuration, RRM instructions, and client management. The data tunnel runs over UDP 5247 and carries the actual client frames when the wireless network is centrally switched. The control tunnel is DTLS-encrypted by default; encrypting the data tunnel as well is optional and costs throughput.
The consequence to remember: because CAPWAP encapsulates client frames, the AP's wired path only ever sees packets sourced from the AP's own IP address. When a wireless network is centrally switched, a client's VLAN never appears on the AP's switchport at all — it appears on the controller's uplink, where the tunnel is unwrapped. That single fact answers most 'what should the AP's switchport be?' questions.
CAPWAP also routes: the AP and the controller do not have to share a VLAN or a subnet, which is what makes a central controller with branch APs possible. The tunnel does add header overhead, so an undersized MTU somewhere on the path shows up as APs that join and then drop again.
7 more sections in this chapter, plus a 4-question quiz.
Modules 2–8 are part of the Course & Lab Pass and All-Access Max — start with a free account
You can see the title, summary, learning objectives and the opening sections. The rest of this chapter, like all of modules 2–8, comes with the Course & Lab Pass and All-Access Max. A free account opens Module 1: How Networks Work end-to-end and saves your labs — start there, no card required.
- Read every chapter in Module 1 — How Networks Work
- Save labs of up to 5 devices
- Save up to 3 topologies
- See the full course syllabus + chapter titles
Free account · no card required · compare plans any time