没有合适的资源?快使用搜索试试~ 我知道了~
首页Current Status and Overview of the CAPWAP Protocol.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的介绍。 后期会奉上自己这段学习的一个总结!
资源详情
资源推荐
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
-
4
-
10
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
-
4
-
10
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
-
4
-
10
http://www.cse.wustl.edu/~jain/cse574
-
10/ftp/capwap/index.html
Fig. 1: Typical WLAN deployment, with a router, 2 controllers, 5 APs, and clients
2.1 Wireless Controllers
In the typical centralized architecture, one or more controllers manage a set number of deployed
access points. Access points retrieve their configuration from the controller, and report their status
back to the controller for management purposes. With the typical usage case, data from an access
point is tunneled back to the controller for processing, and sending onto the back haul network. 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. [Sridhar06] Controllers may
also provide SNMP (Simple Network Management Protocol) data about associated access points,
or other types of monitoring information, such as graphs of traffic data, or numbers of associated
users. [Cisco69561]
Wireless controllers have some general tasks that they perform. They are responsible for
discovering, authenticating, and registration of APs, as well as maintaining a service channel to
communicate over. There are 6 main portions of a controller's duties.
AP Discovery1.
Authentication2.
Association3.
Firmware Distribution4.
Management Traffic5.
Configuration6.
AP Discovery allows a controller to take ownership of an AP, or potentially redirect control to
another controller. The controller can then authenticate the AP, and negotiate its advertised
capabilities, such as being 802.11a, b, g, or n capable, OFDM (Orthogonal Frequency Division
Multiplexing) capable, or what encoding the AP is capable of performing, radio transmit and
receive power, and more. The controller then authenticates the AP, and begins uploading firmware
to the AP. The firmware is used to program radio capabilities on the AP. During this initialization,
as well as operation, periodic control messages must be exchanged between the AP and the
页码,4/19
Current Status and Overview of the CAPWAP Protocol
2012
-
4
-
10
http://www.cse.wustl.edu/~jain/cse574
-
10/ftp/capwap/index.html
剩余18页未读,继续阅读
suifeng
- 粉丝: 8
- 资源: 27
上传资源 快速赚钱
- 我的内容管理 收起
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
会员权益专享
最新资源
- zigbee-cluster-library-specification
- JSBSim Reference Manual
- c++校园超市商品信息管理系统课程设计说明书(含源代码) (2).pdf
- 建筑供配电系统相关课件.pptx
- 企业管理规章制度及管理模式.doc
- vb打开摄像头.doc
- 云计算-可信计算中认证协议改进方案.pdf
- [详细完整版]单片机编程4.ppt
- c语言常用算法.pdf
- c++经典程序代码大全.pdf
- 单片机数字时钟资料.doc
- 11项目管理前沿1.0.pptx
- 基于ssm的“魅力”繁峙宣传网站的设计与实现论文.doc
- 智慧交通综合解决方案.pptx
- 建筑防潮设计-PowerPointPresentati.pptx
- SPC统计过程控制程序.pptx
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功