LWAPP (Lightweight Access Point Protocol)

 LWAPP was Cisco’s original tunneling + control protocol used between lightweight APs and a Wireless LAN Controller (WLC) before CAPWAP became the standard.

Think of LWAPP as:

• Cisco-proprietary

• Older

• Superseded by CAPWAP

• Functionally similar, but less secure + less standardized

---

LWAPP Purpose

LWAPP allowed Cisco to convert “fat APs” (autonomous) into “thin APs” (controller-based).

It provided:

1. Control channel

   • AP → WLC for configs, RF, join process

2. Data channel

   • AP → WLC for client frames

3. Central management

   • APs received configs from controller

4. Split MAC architecture

   • WLC handled most MAC functions

   • AP handled real-time RF stuff

---

Why Cisco Replaced LWAPP

Cisco eventually moved to CAPWAP (Control and Provisioning of Wireless Access Points) because:

LWAPP	CAPWAP
Cisco-proprietary	IETF standard
Encryption optional	DTLS encryption mandatory for control
Limited interoperability	Multi-vendor capable
Early design	Modern RF features supported

CAPWAP fully replaced LWAPP on modern CCNA-tested controllers.

---

Ports

LWAPP used:

• UDP 12222 (data)

• UDP 12223 (control)
  CAPWAP uses:

• UDP 5246 (control)

• UDP 5247 (data)

---

Exam Tip for CCNA

• CAPWAP is on the exam.

• LWAPP is NOT except as a historical reference.

• You only need to know:
  🔹 “LWAPP was Cisco’s older proprietary tunneling protocol replaced by CAPWAP.”