Lightweight Access Point Protocol
来源:互联网 发布:jvm垃圾收集算法有哪些 编辑:程序博客网 时间:2024/05/20 10:10
原文地址:https://en.wikipedia.org/wiki/LWAPP
Lightweight Access Point Protocol
Lightweight Access Point Protocol or LWAPP is the name of a protocol that can control multipleWi-Fi wireless access points at once. This can reduce the amount of time spent on configuring, monitoring or troubleshooting a large network. The system will also allow network administrators to closely analyze the network.
This system is installed in a central server that gathers data from RF devices from different brands and settings. The server can command a selected group of devices to apply given settings simultaneously.
Contents
[hide]- 1Standardization
- 1.1LWAPP Layer 2
- 1.2LWAPP Layer 3
- 2See also
- 3References
- 4External links
Standardization [edit]
LWAPP was proposed by Airespace, as a standard protocol to provide interoperability among any brand of access point. Airespace was purchased by Cisco Systems. Its purpose was to standardize "lightweight" access points with the Internet Engineering Task Force (IETF), but it was approved as a standard. Sponsored by Cisco Systems, it has been submitted to IETF inRFC 5412.[1]
Although this protocol has so far not been popular beyond the Airespace/Cisco product lines, theCAPWAP standard is based on LWAPP. Support for LWAPP is also found in analysis products fromAirMagnet, who has recently implemented a software based on this protocol to analyzeCisco wireless products.[2]
Still considered proprietary, LWAPP systems compete with other non-standard lightweight wireless mechanisms from companies like Meru Networks and Aruba Networks.
LWAPP Layer 2 [edit]
On Layer 2, LWAPP only requires a data link connection in order to transfer frames and Layer 2 broadcasts. Even if IP connectivity is not established it will still operate at layer 2.
LWAPP Layer 3 [edit]
IP Layer 3 (UDP 12222 [data channel] and 12223 [control channel]) connectivity must be established to work with this form of the protocol. Broadcasts orDHCP option 43 can be used to prime the access-points of the network. The controller must be on the same subnet if DHCP is not configured to handle layer 3 LWAPP provisioning. Another option for directing an AP to the controller is by defining the controller on the DNS server of the network.
See also [edit]
- CAPWAP - Control and provisioning of wireless access points (CAPWAP) protocol specification
References [edit]
- ^RFC 5412,Lightweight Access Point Protocol, P. Calhoun, R. Suri, N. Cam-Winget, M. Williams, S. Hares, B. O'Hara, S.Kelly (February 2010)
- ^Griffith, Eric (2007-02-20).Wi-fiPlanet.com "AirMagnet Analyzes Cisco". Wi-Fi Planet.
External links [edit]
- Cisco Wireless LAN Controller Configuration Guide, Release 4.0
- LWAPP: Standardizing Centralized Wi-Fi Management from Wi-Fi Planet
- Lightweight Access Point Protocol IETF Standard
- Control And Provisioning of Wireless Access Points (CAPWAP)Protocol Specification
- Internet protocols
- Lightweight Access Point Protocol
- 轻量级目录访问协议(Lightweight Directory Access Protocol)
- LDAP Injection (Lightweight Directory Access Protocol Injection)
- LANEscape Inter Access Point Protocol (LIAPP) Specification v0.3 Draft
- Point to Point Protocol (PPP)
- Select Access Point
- WAP:wireless access point
- Wireless access point
- Wireless Access Point
- Edison Ubilinux Access Point
- Create new internet access point
- Access Point Compatibility of MRF24WB
- Wireless 802.11g Access Point
- 关于无线 AP (Access point)
- AP ---(Wireless Access Point) 研究
- RFC 2637 Point-to-Point Tunneling Protocol (PPTP)
- 点对点隧道协议PPTP(Point-to-Point Tunneling Protocol)
- RFC1661_The Point-to-Point Protocol _点对点协议(PPP)
- ubuntu操作命令
- CAPWAP
- CIRCOS教程翻译 5.8——Rule
- latex 首行缩进
- Windows phone 应用开发[14]-调用WebBrowser
- Lightweight Access Point Protocol
- secureCRT相关
- 多人实时协同文本编辑平台
- Linux 下进程控制编程——vfork()使用
- 问题解决unrecognized selector sent to instance
- Android手机中获取手机号码和运营商信息
- C++ Prime学习过程中的细节摘记(一)
- 烟台大学举办首届ACM程序设计大赛
- JSON 入门笔记