http://70.231.62.181/index.php?action=history&feed=atom&title=Control_and_Provisioning_of_Wireless_Access_Points_protocolControl and Provisioning of Wireless Access Points protocol - Revision history2026-04-22T21:01:45ZRevision history for this page on the wikiMediaWiki 1.45.1http://70.231.62.181/index.php?title=Control_and_Provisioning_of_Wireless_Access_Points_protocol&diff=16605863&oldid=previmported>Guninvalid: /* Implementations */ removed, see WP:RSPGITHUB2025-06-08T00:24:59Z<p><span class="autocomment">Implementations: </span> removed, see <a href="/index.php?title=WP:RSPGITHUB&action=edit&redlink=1" class="new" title="WP:RSPGITHUB (page does not exist)">WP:RSPGITHUB</a></p>
<p><b>New page</b></p><div>{{Short description|Networking protocol}}<br />
The '''Control And Provisioning of Wireless Access Points''' ('''CAPWAP''') protocol is a standard, interoperable networking protocol that enables a central [[wireless LAN controller]] to manage a collection of ''Wireless Termination Points (WTPs)'', more commonly known as [[wireless access point]]s. The protocol specification is described in RFC 5415.<ref>{{Cite IETF |title=Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification |rfc=5415 |editor-first1=Pat R. |editor-first2=Michael |editor-first3=Dorothy |editor-last1=Calhoun |editor-last2=Montemurro |editor-last3=Stanley |date=March 2009 |publisher=[[Internet Engineering Task Force|IETF]] |access-date=24 October 2013 |doi=10.17487/RFC5415}}</ref><br />
<br />
==Protocol overview==<br />
CAPWAP is based on [[Lightweight Access Point Protocol]] (LWAPP). The state machine of CAPWAP is similar to LWAPP's, but with the addition of a full [[Datagram Transport Layer Security]] (DTLS) tunnel establishment. The standard provides configuration management and device management, allowing for configurations and firmware to be pushed to access points (APs). Because the overall state design of the CAPWAP protocol is largely the same as the [[finite-state machine]] (FSM) in LWAPP, a detailed diagram is not needed.{{citation needed|reason=Personal opinion|date=January 2016}}<br />
<br />
The protocol uses a generic encapsulation and transport mechanism, making it independent of a specific radio technology. The specification of CAPWAP for a particular wireless technology is called a ''binding''. An [[IEEE 802.11]] binding is provided in RFC 5416.<ref>{{Cite IETF |title=Control and Provisioning of Wireless Access Points (CAPWAP) Protocol Binding for IEEE 802.11 |rfc=5416 |editor-first1=Pat R. |editor-first2=Michael |editor-first3=Dorothy |editor-last1=Calhoun |editor-last2=Montemurro |editor-last3=Stanley |date=March 2009 |publisher=[[Internet Engineering Task Force|IETF]] |access-date=24 October 2013 |doi=10.17487/RFC5415}}</ref><br />
<br />
CAPWAP uses [[User Datagram Protocol|UDP]] ports 5246 (control channel) and 5247 (data channel).<br />
<br />
==See also==<br />
* [[Lightweight Access Point Protocol]] (LWAPP) used to manage a large set of WAPs<br />
* [[Wireless LAN]] - networks consisting of one or more access points plus one or more devices<br />
<br />
== References ==<br />
{{Reflist}}<br />
<br />
[[Category:IEEE 802.11]]<br />
[[Category:Network access]]<br />
[[Category:Telecommunications infrastructure]]<br />
[[Category:Wireless networking]]<br />
<br />
<br />
{{Wireless-stub}}</div>imported>Guninvalid