blog banner


RFC CAPWAP Protocol Base MIB May CAPWAP Control Channel: A bi-directional flow defined by the AC IP Address, WTP IP Address, AC control. The Control And Provisioning of Wireless Access Points (CAPWAP) protocol is a standard, The protocol specification is described in RFC RFC (part 1 of 6): Control And Provisioning of Wireless Access Points ( CAPWAP) Protocol Specification.

Author: Batilar Doukasa
Country: Central African Republic
Language: English (Spanish)
Genre: Relationship
Published (Last): 11 May 2007
Pages: 252
PDF File Size: 18.70 Mb
ePub File Size: 12.94 Mb
ISBN: 656-4-60326-652-9
Downloads: 30238
Price: Free* [*Free Regsitration Required]
Uploader: Goltigor

It merely relays the encrypted frames to the controller for processing. Vendors do not have a clearly defined capwsp of protocols that must be implemented, in order to be compatible with other vendors.

A single Receiver thread receives and processes any requests from APs. The Receiver is then responsible for processing the packets, and either dropping the packets, or moving a good connection into a Session Manager Cspwap.

Finally configuration takes place, and the AP is set into active mode. Image Download – The newly joined AP then may request a firmware update, upon seeing the controller advertise a higher version of code.

A device that contains an interface to a wireless medium WM. The significant cost of enterprise level WLAN deployment, coupled with both hardware and software differences on Controllers and Access Points breeds vendor lock-in.

Additionally, ffc of its generic design, the network location of an AP and controller do not necessarily have to be within the same broadcast domain. This protocol can be anything, as long as capeap sides agreed on it.

Overall convergence for the APs to come online will take longer in this scenario. Decryption Error Report Period A standard that ensures compatibility between vendors is necessary to prevent vendor lock-in.

Current Status and Overview of the CAPWAP Protocol

The creation of a vendor neutral protocol is a potential boon to consumers of enterprise grade managed wireless solutions. This would allow for more rapid reaction to new innovations in the WLAN sector, as well as improve implementation quality. Local MAC refers to the location of the rc The only difference is the protocol being used between the AP and the controller. Figure 2 shows the Local MAC mode, in which a station transmits a wireless frame that is encapsulated in an It is important to realize that the definition of what a controller is is not clearly defined.


The controller and AP will exchange 2 types of messages: Contributing Authors This section lists and acknowledges the authors of significant text and concepts included in this specification.

Returned Message Element Reason Each time the AP would have to download firmware when moving from one controller to the next with different code versions. One of the main differences is the use of DTLS. Inter-AC and station-to-AC communication are strictly outside the scope of this document.

This leaves the time-critical applications of wireless control and access in the WTP, making efficient use of the computing power available in WTPs, which are subject to severe cost pressure.

The AP would only implement the The controller transmits a “client end” message, to signify the termination of the DTLS exchange. Thin APs have their MAC layers implemented entirely on the controller, and use tunneling to a controller to have all fapwap their frames processed for forwarding onto the back haul network. SLAPP attempted to solve a more general problem, not limiting itself to An overview of the architecture and protocols use in access point AP to controller communication in enterprise grade wireless networks.

The Principal thread creates a Receiver thread, to handle the responses from the controller. A Fat AP understands and speaks layer 2 and possible layer 3 protocols, and is addressable on the network. It was seen as overly complex, as well as lacking in security, as portions of the control stream are unencrypted, and the entire data stream capwp controller and AP are unencrypted.

Overview of CAPWAP (Cisco Wireless LAN Controllers)

There are 3 types of AP threads, and no more than 3 threads may be active at any one time: The controller then moves into the Negotiated Control Protocol state. In this regard, the controller acts in similar fashion to a router, by accepting and processing layer 2 frames, and then switching layer frames on to the access network.


The WLAN market is structured similarly to an oligopoly, because the market is controlled by a very small set of vendors, namely Aruba, Cisco, Meru, and Trapeze. The state machine in [fig6] show the 4 states attainable during protocol negotiation by a device.

This reduces complexity of the AP. Current vendor solutions and interoperability is also covered, and the current state and trends in the enterprise WLAN market are discussed.

And finally, ensuring network security, both from 3rd party hardware, such as rogue access points being connected to the network, as well as preventing the loss of network secrets from the physical theft rfd access points is also critical.

More specifically, it fails to define key duties mentioned in [Section 2. Network Working Group P. There are 6 main portions of a controller’s duties. Distribution of this memo is unlimited. Please refer to the current edition of the “Internet Official Protocol Standards” STD 1 for the standardization state and status of this protocol.

However, only the control messages are transmitted in a DTLS tunnel still. Some vendors have produced products that allow operation with multiple brands of AP, such as Aruba Network’s AirWave being able to provision and control Aruba, Cisco, and Meru access points.

The paper covers the current architecture of rgc WLAN deployments, as well as proposed protocols that attempt to simplify their management and configuration, and allow inter-vendor compatibility of access points APs and controllers.

CAPWAP, Control And Provisioning of Wireless Access Points

A controller must respond with a Discovery Response. The need for flexible wireless network infrastructure will become more pronounced as WLANs become larger and more widespread. The following people are authors of significant DTLS-related text included in this document: Firstly, it should enable a centralized management solution of the various hardware in cxpwap typical WLAN deployment.

This lack of customer mobility leads to less innovative product offerings from the wireless vendors.