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.
|Published (Last):||5 March 2005|
|PDF File Size:||13.43 Mb|
|ePub File Size:||14.81 Mb|
|Price:||Free* [*Free Regsitration Required]|
Primary Discovery Request Message The AP handles the encryption of traffic between itself and its clients, with the controller provided keys. A device that contains an interface to a wireless medium WM. The AP forwards packets to the controller, and maintains normal operation. Meru has made no plans public for enabling support for a standards compliant method of AP-controller interaction.
This thread is used to accept non-realtime requests from the associated client stations, such as any message in Split MAC that may need to be forwarded to the controller in the CAPWAP ffc. The controller implements most of the management and configuration logic. Extensibility is provided via a generic encapsulation and transport mechanism, enabling the CAPWAP protocol to be applied to many access point types in the future, via a specific wireless binding.
The publishers argue that an unencrypted data channel is not a security threat, because full IPsec is available. The first is targeted at server hardware, and handles the operation of the controller.
Vendors such as Trapeze criticized the specification, as it makes assumptions about capaap topology of the network that the WLAN will be deployed on, as well as assumptions about the complexity and functionality implemented by the AP, by allowing only Local and Split MAC implementations. The paper covers the current architecture of enterprise 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.
Because a capsap change would require the purchase of duplicate Controller and AP hardware, it is often unfeasible for a wireless network to be migrated from one vendor to another. In order to understand the CAPWAP, one must first understand the basic cawpap structure, common to most, rtc not all enterprise grade wireless network deployments. From the Run rfv, an AP and controller may exchange new key material, by entering the Key Update state.
Discovery – Discovery is the initial broadcast from an AP, informing controllers that they are interested in communicating in a specific protocol. Inter-AC and station-to-AC communication are strictly outside the scope rfcc this document. Thus, the entire process of deploying an AP can be implemented in a vendor neutral format, from finding an initial controller, to deploying firmware updates, to configuration and access point redirection. CAPWAP only seeks to relay what a device is and is not capable of, in order to classify and provision the device into operation.
Major vendors have also expressed doubt over the demand from customers for interoperable WLAN infrastructure. Change State Event Request Thus, OpenCAPWAP is only a proof of concept, as they are limited in the hardware that they may support, by capeap lack of common target hardware, as well as differencing Configure capsap An Capqap with a sufficient version of code may then request to be configured by the controller.
The controller then authenticates the AP, and begins uploading firmware to the AP.
CAPWAP, Control And Provisioning of Wireless Access Points
Change State Event Response The AC may also provide centralized bridging, forwarding, and encryption of user traffic. There are 2 primary components to the wireless network.
The second program is run on each AP, in order to facilitate communication between the Capwapp and controller. The significant cost of enterprise level WLAN deployment, coupled with both hardware and software differences on Controllers and Access Points breeds vendor lock-in.
This is accomplished by the AP broadcasting a Discovery Request.
It merely relays the encrypted frames to the controller for processing. The cost per unit is much lower than Fat APs, as the only logic necessary for functioning is the radio hardware and capwsp simple wired interface, with memory to store firmware. In either case, the L2 wireless management frames are processed locally.
Overview of CAPWAP (Cisco Wireless LAN Controllers)
The AP broadcasts a Discovery Request, and upon reception of the response, moves to the Acquiring phase as well. Thin APs have their MAC layers implemented entirely on the controller, and use tunneling to a controller to have all of their frames processed for forwarding onto the back haul caowap. SLAPP was designed as a simple, extensible protocol that could be extended to other wireless standards, and allow for newer authentication schemes and control protocols to be implemented on top of SLAPP.
The process by which an AP discovers a controller, validates firmware, and downloads firmware and configurations does not change. The controller capwwp a channel to the AP, which stays open for the up time of the access point.
Current Status and Overview of the CAPWAP Protocol
One of the reasons for such little support is that the deployment is restricted to a Layer 2 boundary. Contributing Authors This section lists and acknowledges the authors of significant text and concepts included in this specification.
One of the main differences is the use of DTLS. The DTLS tunnel allows for different authentication styles, ranging from full stream encryption, to one way encryption, to anonymous authentication. The Principal thread creates a Receiver thread, to handle the responses from the capwwp. WTPs require a set of efc management and control functions related to their primary task of connecting the wireless and wired mediums.
The firmware is used to program radio capabilities on the AP. Fat APs are much more complex, and cost much more per unit than their thinner cousins. Receiver and Session Manager [fig7]. The only duties that the controller is responsible for ccapwap this scheme is wireless key management caapwap authentication proxying. A large corporate network with hundreds of APs could use a more centralized solution, which is realized by Thin APs.
A Fat AP understands and speaks layer 2 and possible layer 3 protocols, and is addressable on the network. Table of Contents 1. In this survey, a look at different proposed standards for enabling WLAN controllers to support multi-vendor APs, and how to solve the problems introduced by the AP-controller architecture, has been taken.
Rather, it attempts to provide the framework with which devices may request a specific configuration method, which is then layered on top of SLAPP.