skip to content

In CAPWAP's IEEE 802.11 binding, how do Split MAC and Local MAC divide 802.11 functions between the access point and the controller?

level: middleimportance: should knowfreq 24%

answer

  1. real-time work stays on the radio
  2. who answers the association
  3. where integration happens
  4. the AAA client's location
  5. which mode is mandatory

basics

~20 s

In Split MAC the AP keeps real-time work such as beacons and probe responses, while the controller processes associations and receives all user data through the tunnel. In Local MAC the AP terminates the 802.11 MAC and may bridge traffic locally.

solid answer

~40 s

RFC 5416 gives a function-by-function table. In **both** modes the AP generates **beacons** and **probe responses** and buffers frames for power-saving clients, because those tasks are time-critical. In **Split MAC** the **distribution and integration services** sit on the controller, so every user frame crosses the CAPWAP tunnel in native 802.11 format, and association, disassociation and reassociation are processed by the controller. In **Local MAC** the AP terminates the MAC and performs the integration function; user traffic is bridged locally or tunnelled as 802.3 frames, and the AP must still forward association requests so the controller can refuse one. In both modes 802.1X/EAP and RSNA key management sit on the controller, which makes it the AAA client. Local MAC is the mode every WTP must support; Split MAC is optional.

go deeper

for a junior

Recall that both modes leave beacons on the AP, and that Split MAC sends user data to the controller while Local MAC can keep it local.

for a middle

Walk through the RFC 5416 table: integration and distribution, association handling, and the fact that 802.1X and key management stay on the controller in both modes.

for a senior

Explain what the mode choice means for traffic paths, encryption points and admission control, and where implementations go beyond the binding.

for a principal

Judge which mode each WLAN class should use, weighing central control and inspection against local forwarding and dependence on the controller.

## Why CAPWAP splits the MAC at all The 802.11 MAC mixes two very different kinds of work. Some of it is **time-critical**: beacons must go out on schedule, probe responses must answer scanning clients quickly, frames for sleeping clients must be buffered, and transmit queues must be served as the medium frees up. Some of it is **policy**: deciding whether a client may associate, running 802.1X, managing keys and enforcing QoS classes. CAPWAP (RFC 5415) lets a controller, the **Access Controller (AC)**, take over policy while the AP, the **Wireless Termination Point (WTP)**, keeps the time-critical part. Its IEEE 802.11 binding, RFC 5416, defines exactly where each function sits in its two modes. ## The binding's table | Function | Split MAC | Local MAC | |---|---|---| | Distribution service | AC | WTP or AC | | Integration service | AC | WTP | | Beacon generation | WTP | WTP | | Probe response generation | WTP | WTP | | Power management and packet buffering | WTP | WTP | | Fragmentation and defragmentation | WTP or AC | WTP | | Association, disassociation, reassociation | AC | WTP and AC | | 802.11 QoS classifying | AC | WTP | | 802.11 QoS scheduling | WTP or AC | WTP | | 802.11 QoS queuing | WTP | WTP | | IEEE 802.1X/EAP | AC | AC | | RSNA key management | AC | AC | | 802.11 encryption and decryption | WTP or AC | WTP | The **integration service** is the bridge between the 802.11 world and the wired 802.3 world; the **distribution service** decides where a frame goes next. Whoever holds them decides where user traffic leaves the wireless system. ## Split MAC in practice - The AP is a remote radio: it beacons, answers probes and queues frames, but hands every other management frame to the controller. - The **association request** goes to the controller, which lets it apply access policy before the client is admitted. - Because integration and distribution sit on the AC, **all user data is tunnelled** to it. RFC 5416 forbids pairing Split MAC with the 802.3 tunnel mode, so frames travel in **802.11 format**. - Encryption may be done on the AP or the controller; when the controller does it, frames stay protected all the way through the tunnel. - Split MAC support is **optional** for a WTP. ## Local MAC in practice - The AP **terminates the 802.11 MAC**: it handles the frame exchange with the client and performs the integration function itself. - The distribution service can stay on the AP (**local bridging**, user frames go straight onto the AP's wired port) or move to the controller (an **802.3 tunnel**, already-converted Ethernet frames sent over CAPWAP). - The AP **must forward association requests** to the controller, because the controller still needs to know about mobility events. If the AC answers with a failed association response, the AP must send the client a disassociation frame. - 802.11 encryption and decryption happen on the AP. - Local MAC is the **default mode, and the one every WTP must support**. ## What both modes keep on the controller In both modes RFC 5416 places **IEEE 802.1X/EAP** and **RSNA key management** on the controller, so the **AAA client** (the device that talks RADIUS to the authentication server) is the AC, not the AP. RFC 5418 lists the resulting key flow: 1. The station and the AAA server run EAP and produce a PMK. 2. The AAA server pushes the PMK to the AC. 3. The AC and the station run the four-way handshake, covered with WPA2. 4. If encryption is done on the AP, the AC pushes the temporal key to the WTP. 5. The WTP and the station use that key to protect frames over the air. This is the detail interviews probe most: **Local MAC is not "the AP does everything"**. Under the binding, the controller still owns admission and keys. ## Common confusions - "Split MAC means the controller sends the beacons." It never does; beacons and probe responses are generated on the AP in both modes. - "Local MAC means the AP is the RADIUS client." Not under RFC 5416; implementations may add local authentication, but that is an extension. - "Split MAC can bridge traffic locally." Not by the binding's definition; local forwarding needs Local MAC with local bridging. - "The two modes are vendor terms." They are RFC 5415 and RFC 5416 terms, signalled by the WTP during discovery and chosen per WLAN by the AC.

  • Can a Split MAC WLAN bridge user traffic locally at the AP?
    Not under RFC 5416's definition. Split MAC puts the distribution and integration services on the controller, so all user data is tunnelled to it, and the binding forbids pairing Split MAC with the 802.3 tunnel mode, so frames travel in 802.11 format. If traffic must stay local, that WLAN needs Local MAC with local bridging.
  • Under Local MAC, can the controller still refuse a client?
    Yes. The WTP must forward every association request to the AC, and if the AC replies with a failed association response, the WTP must send the station a disassociation frame. That is how central admission policy survives while the MAC is terminated on the AP.
  • Where does 802.11 encryption happen in each mode?
    The binding requires every WTP and AC to support encryption at the WTP and allows it at the AC as an option. Local MAC places it on the WTP; Split MAC lists WTP or AC. When the AP encrypts, the controller pushes the temporal key to it after the key exchange it ran with the client.

  • In Split MAC the controller generates the beacons and probe responses.
  • Under CAPWAP's Local MAC the AP runs 802.1X itself and is the RADIUS client.
  • Split MAC is the mandatory mode every CAPWAP access point must implement.
  • A Split MAC WLAN can tunnel user traffic to the controller as 802.3 frames.
  • In Local MAC the controller never sees association requests.