CurrentStatusandOverviewoftheCAPWAPProtocol.pdf资源-CSDN文库

需积分: 9 76 浏览量 2012-04-10 11:06:18 上传评论收藏 774KB PDF 举报

近期由于项目需要，开始学习WAPCAP，现在将自己找到的资料分享一下，主要内容简介：关于WLAN的两个标准： RFC5415(主要介绍协议的工作原理) 和 RFC5416（主要介绍如何与802.11协同工作） capwap-0.93.3.tar.gz：上面的两个协议的具体实现，一个开源的项目 Opencapwap+An+Open+Source+Capwap+Implementation+For+The+Management+And+Configuration+Of+Wifi+Hot-spots.pdf ：上面的opencapwap-0.93.3的作者写的介绍 CAPWAP Overview.ppt Current Status and Overview of the CAPWAP Protocol.pdf 基于CAPWAP协议的集中式无线局域网架构.pdf CAPWAP介绍.ppt 这些都是一些capwap的介绍。后期会奉上自己这段学习的一个总结！ ### 关于CAPWAP协议的现状与概述 #### 一、引言随着无线网络技术的发展，企业级无线局域网(WLAN)部署的需求日益增长。为了满足这种需求，业界提出了多种解决方案和技术标准来简化无线局域网的管理和配置，并确保不同厂商之间的设备能够兼容互操作。其中，控制和配置无线接入点协议(Control and Provisioning of Wireless Access Points,简称CAPWAP)是目前最为广泛接受的标准之一。本文旨在概述CAPWAP协议的工作原理、架构以及其实现方案，并对比其他相关协议如LWAPP和SLAPP等。 #### 二、CAPWAP的目标 CAPWAP协议的主要目标包括： - **简化管理**：通过集中化的方式简化无线接入点(AP)的管理和配置。 - **多厂商兼容性**：确保不同厂商生产的无线接入点与控制器之间能够实现良好的兼容性和互操作性。 - **安全增强**：提供安全机制，保护无线通信数据的安全。 #### 三、CAPWAP提案概述 CAPWAP提案涵盖了以下几个方面： - **协议结构**：定义了无线接入点与控制器之间的交互模型。 - **数据传输**：规范了数据包的格式和传输流程。 - **安全机制**：提出了一系列安全保障措施，包括加密算法和身份验证方法。 #### 四、AP-控制器架构在企业级无线局域网中，通常采用AP-控制器架构来实现集中化的管理。这一架构主要包括以下几种类型： - **无线控制器**：作为核心组件负责管理和配置无线接入点。 - **胖AP与瘦AP**：胖AP具有完整的功能，可以独立运行；而瘦AP则依赖于控制器进行配置和管理。 - **本地MAC与远程MAC实施**：本地MAC是指MAC地址管理在AP端完成，而远程MAC则是由控制器统一管理。 - **分层MAC实施**：结合了本地MAC和远程MAC的优点，实现灵活的部署方式。 #### 五、具体实现：LWAPP协议 LWAPP协议（轻量级无线接入点协议）是一种早期的无线局域网管理协议，其特点包括： - **概述**：主要用于简化无线接入点的配置和管理。 - **分层MAC操作**：支持不同的MAC地址管理方式，以适应不同的应用场景。 - **安全性**：提供了基本的安全保障措施。 #### 六、具体实现：SLAPP协议 SLAPP协议（安全轻量级接入点协议）是对LWAPP的一种改进，其特点包括： - **概述**：增强了安全性和互操作性。 - **安全性**：采用了更先进的加密技术和认证机制。 - **与LWAPP的区别**：SLAPP在安全性方面进行了显著的增强。 #### 七、具体实现：CAPWAP协议 CAPWAP协议是当前最广泛使用的标准之一，其特点包括： - **协议概述**：定义了AP与控制器之间的交互细节。 - **厂商立场**：不同的厂商对CAPWAP的支持程度和实现方式有所不同。 - **案例分析**：例如Aruba Networks和Trapeze Networks等公司都有自己的实现方案。 #### 八、开源解决方案：OpenCAPWAP OpenCAPWAP是一个开源项目，旨在提供一个灵活、可扩展的CAPWAP实现框架。它可以帮助开发者快速构建支持CAPWAP协议的无线网络应用，同时支持多种无线接入点和控制器。 #### 结论 CAPWAP协议为无线局域网的管理和配置提供了标准化的方法，大大简化了无线网络的部署过程。通过比较不同的协议实现（如LWAPP、SLAPP和CAPWAP），我们可以看到CAPWAP在互操作性和安全性方面具有明显的优势。此外，OpenCAPWAP等开源项目的出现进一步推动了CAPWAP的应用和发展。未来，随着无线网络技术的不断进步，CAPWAP协议将继续发挥重要作用，为企业级无线局域网部署提供更加高效和可靠的解决方案。

资源推荐

资源详情

资源评论

Current Status and Overview of the

CAPWAP Protocol

Author: Gabe Conradi <gabe [dot] conradi [at] gmail [dot] com>, <gc2 [at] cec [dot] wustl [dot]

edu>

Abstract

This paper presents an overview of the Control and Provisioning of Wireless Access Points

(CAPWAP) working group, and the proposals that have emerged from it. 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. The Lightweight Access Point Protocol (LWAPP), Secure Light

Access Point Protocol (SLAPP), and CAPWAP protocols are all discussed and compared. Current

vendor solutions and interoperability is also covered, and the current state and trends in the

enterprise WLAN market are discussed. Open source solutions such as OpenCAPWAP are also

inspected, and compared to vendor solutions currently available.

Keywords

CAPWAP, Control and Provisioning of Wireless Access Points, SLAPP, Secure Light Access

Point Protocol, LWAPP, Lightweight Access Point Protocol, WLAN, Multi-vendor, Split MAC,

Local MAC, Remote MAC, OpenCAPWAP, Centralized Management, Wireless, WLAN, AP,

Access Point, Wireless Switch, Wireless Router

Description

An overview of the architecture and protocols use in access point (AP) to controller

communication in enterprise grade wireless networks.

Table of Contents

1. Introduction to CAPWAP •

1.1 Goals of CAPWAP◦

1.2 Overview of CAPWAP proposals◦

2. AP-Controller Architecture •

2.1 Wireless Controllers◦

2.2 Fat vs. Thin vs. Fit APs◦

2.3 Local MAC Implementations◦

2.4 Remote MAC Implementations◦

2.5 Split MAC Implementations◦

2.6 Important Considerations◦

3. Specific Implementations: LWAPP •

3.1 LWAPP Overview◦

3.2 Split MAC Operation in LWAPP◦

3.3 Security◦

3.4 Current Status◦

页码，1/19

Current Status and Overview of the CAPWAP Protocol

2012

http://www.cse.wustl.edu/~jain/cse574

10/ftp/capwap/index.html

4. Specific Implementations: SLAPP •

4.1 SLAPP Overview◦

4.2 Security◦

4.3 Differences Between SLAPP and LWAPP◦

5. Specific Implementations: CAPWAP •

5.1 Protocol Overview◦

5.2 Vendor Positions ◦

5.2.1 Aruba Networks■

5.2.2 Trapeze Networks■

5.2.3 Cisco Systems■

5.2.4 Meru Networks■

6. Future Directions and Developments •

6.1 OpenCAPWAP Overview◦

6.2 OpenCAPWAP Implementation◦

6.3 Current Status◦

7. Summary•

References•

List of Acronyms•

List of Related Products•

1. Introduction to CAPWAP

The term CAPWAP is used for the Control And Provisioning of Wireless Access Points working

group. The CAPWAP working group was created in the IETF in order to standardize and define a

protocol to ease the implementation of large WLAN deployments that utilize the Controller-AP

(Access Point) architecture. The nature of such systems is of such complexity, that vendor

implementations can vary widely in their scope and features, leading to incompatibilities between

vendors. The significant cost of enterprise level WLAN deployment, coupled with both hardware

and software differences on Controllers and Access Points breeds vendor lock-in. Because a

vendor 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. This lack of

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

The size of many wireless networks in large companies and universities also introduces many

problems of maintaining a consistent configuration across many similar devices, with potentially

different hardware capabilities and physical locations. Vendors have provided individual solutions

to these issues stated above. However, the implementations are proprietary and have different

views on where functionality in the network should be.

The CAPWAP working group seeks to rectify this by specifying a protocol that ensures a common

standard for APs and WLAN controllers to communicate with. 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. Ideally controllers of

any vendor could provision access points from any other vendor, provided they implement a

common CAPWAP protocol. This would allow for more rapid reaction to new innovations in the

WLAN sector, as well as improve implementation quality.

This paper is organized as follows: [Section 1] will talk about the goals of the CAPWAP working

group. [Section 2] will talk about general architecture of current wireless 802.11 infrastructure, as

well as discuss the differences between Split MAC, Local MAC, and Remote MAC layers in APs.

[Section 2] will also focus on how so called "Fat APs" are managed and route traffic, as compared

to "Thin APs". [Sections 3], [4], and [5] discuss 3 specific protocols that have been proposed, and

discusses the differences between them. Next, [Section 6] will look at new trends in the CAPWAP

页码，2/19

Current Status and Overview of the CAPWAP Protocol

2012

http://www.cse.wustl.edu/~jain/cse574

10/ftp/capwap/index.html

space, and focus specifically on an open source alternative called OpenCAPWAP. Finally,

[Section 7] will summarize the key concepts of CAPWAP.

1.1 Goals of CAPWAP

A unified CAPWAP standard aims to be a protocol that could enable centralized wireless

hardware utilize a simple, streamlined method of communicating between access points and

controllers. As specified by the CAPWAP working group in the IETF (Internet Engineering Task

Force), CAPWAP should address 4 main issues. Firstly, it should enable a centralized

management solution of the various hardware in a typical WLAN deployment. Second, it should

make configuration of multiple hardware types transparent, and ensure configurations are

consistent across the network. Third, monitoring the status of both hardware and software

configurations is necessary to ensure a properly operating network. 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 of access points

is also critical. [RFC3990] [Villani] [Jou04]

1.2 Overview of CAPWAP proposals

The challenges facing wireless networks with regard to standardized management and

provisioning are difficult. Proposals for a CAPWAP protocol have been submitted to the

CAPWAP WG for review. However, some have been met with criticism. 3 specific protocols have

surfaced, that have received the most attention and review. The first, LWAPP, or Lightweight

Access Point Protocol was proposed, in part supported by Cisco Systems. Next, Aruba Networks

and Trapeze proposed a competing protocol named SLAPP, or Secure Light Access Point

Protocol, which took a more abstract approach to handling proprietary firmware for vendor's

access points. Finally, an updated protocol called CAPWAP, penned by Cisco Systems, Aruba

Networks, and Research In Motion, among others, took the place as the front runner of the

proposals. [RFC5412] [RFC5413] [RFC5415]

Table of Contents

2. AP-Controller Architecture

In order to understand the CAPWAP, one must first understand the basic controller-AP structure,

common to most, if not all enterprise grade wireless network deployments. There are 2 primary

components to the wireless network. The controller implements most of the management and

configuration logic. The controller acts as a management station, configuration station, and

potentially a router. The access point contains the wireless radio(s), and acts as the end point of

the network, and communicates directly with user radios. The AP typically contains some amount

of logic, however, that amount is governed by the MAC architecture that the AP implements,

which will be covered in [Section 2]. A typical diagram of a WLAN network is in [fig1].

页码，3/19

Current Status and Overview of the CAPWAP Protocol

2012

http://www.cse.wustl.edu/~jain/cse574

10/ftp/capwap/index.html

剩余18页未读，继续阅读

评论收藏

内容反馈

suifeng

粉丝: 8
资源: 27

Current Status and Overview of the CAPWAP Protocol.pdf

Network Security Current Status And Future Directions.pdf

Synthetic Aperture Sonar A Review of Current Status.pdf

CAPWAP协议

capwap协议

capwap协议分析

CAPWAP学习文档

CAPWAP 协议介绍

CAPWAP Overview.ppt

CAPWAP介绍.ppt

rfc5416.pdf

Overview of the IRAQ Opportunity.ppt

2007 - Smith - An Overview of the Tesseract OCR Engine.pdf

capwap协议中文版

CAPWAP的RFC文档

Overview of 5G security technology.pdf

C++标准库（第二版）英文版.pdf

An Overview of Multi-Task Learning in Deep Neural Networks.pdf

AUTOSAR_PRS_TestabilityProtocolAndServicePrimitives.pdf

Overview of the High Efficiency Video Coding(HEVC) Standard.pdf

mojal 23 Modeling and control of overhead cranes, A tutorial overview and perspectives. ann rev ctrl.pdf

System Center 2012 Overview Datasheet-EN.pdf

An overview of multi-task learning.pdf

Overview of HEVC codec standard.rar

Overview of the RANSAC Algorithm

国际经济学课件1-15PDF版打包.zip

全球云竞争概览 An Overview of Global Cloud Competition 202304.pdf

最新资源