The CAPWAP implementation is just the encapsulation format and
therefore really not the full protocol. While there were some
uses of it (primarily hardware support and UDP transport). But
these are most likely better provided by VXLAN. As a result,
CAPWAP will be removed no earlier than February 2013.
Signed-off-by: Pravin B Shelar <pshelar@nicira.com>
- Interface type "null".
- Numeric values for reserved ports (see "ovs-ofctl" note above).
- Tunnel Path MTU Discovery.
+ - CAPWAP tunnel support.
- The data in the RARP packets can now be matched in the same way as the
data in ARP packets.
- Interface type "null".
- Numeric values for reserved ports (see "ovs-ofctl" note above).
- Tunnel Path MTU Discovery.
+ - CAPWAP tunnel support.
- The data in the RARP packets can now be matched in the same way as the
data in ARP packets.
ovs_be32 saddr = htonl(0);
uint32_t flags;
+ if (!strcmp(type, "capwap")) {
+ VLOG_WARN_ONCE("CAPWAP tunnel support is deprecated.");
+ }
+
flags = TNL_F_DF_DEFAULT | TNL_F_HDR_CACHE;
if (!strcmp(type, "gre") || !strcmp(type, "gre64")) {
is_gre = true;
implemented. UDP ports 58881 and 58882 are used as the source and
destination ports respectively. CAPWAP is currently supported only
with the Linux kernel datapath with kernel version 2.6.26 or later.
+
+ CAPWAP support is deprecated and will be removed no earlier than
+ February 2013.
</dd>
<dt><code>patch</code></dt>