SD-LAN Services - Enabling NAT-Traversal for VxLAN-GPE Tunnels

Network Address Translation Traversal (NAT-T) enables devices located behind a NAT-enabled router to establish and maintain connections with devices on the public internet or across different private networks. NAT-T is particularly important for tunneling protocols, which often struggle to function across NAT boundaries.

It typically involves:

  • Encapsulating tunnel traffic in UDP packets, which are more NAT-friendly and less likely to be blocked or altered.
  • Maintaining NAT mappings using periodic keep-alive messages or by configuring port forwarding rules on the NAT device.

Feature Overview

NAT allows multiple devices on a private network to share a single public IP address. While it works well for outgoing connections, it typically blocks incoming connections unless explicitly configured to allow them. Enabling NAT-T support for Generic Protocol Extension for Virtual Extensible LAN (VxLAN-GPE) tunnels addresses deployment scenarios where VxLAN-GPE traffic between RUCKUS devices must traverse a NAT router, ensuring seamless tunnel establishment and communication.

Requirements

Your RUCKUS Edge devices and APs must meet the minimum required firmware version and supported AP models for SD-LAN network service configuration. You can find this information in RUCKUS One by clicking Network Control > Service Catalog, hovering on the icon in the SD-LAN tile, and clicking on the displayed See the compatibility requirements hyperlink. The resulting Compatibility Requirement sidebar displays the information.

The cluster must be up with RUCKUS Edge nodes running.

Considerations

This feature has no special considerations pertaining to feature enablement or usage.

Limitations

When you enable NAT-T support for tunneling between the AP and the Edge cluster, load balancing of VxLAN-GPE tunnel traffic is compromised. This is due to the loss of UDP source port entropy, which introduces the following system-level limitations:

  • When NAT-T is enabled, traffic from the AP to the Edge device may be routed through a single physical link, potentially leading to congestion and suboptimal bandwidth utilization.
  • The RUCKUS Edge device’s packet processing system (based on VPP with DPDK) will map all tunnel traffic from an AP to the same receive queue and worker thread, which can negatively impact throughput performance.

Best Practices

This feature has no special recommendations for feature enablement or usage.

Prerequisites

Before adding an SD-LAN service, a Tunnel Profile meeting the requirements of your AP-to-Cluster tunnel must already be configured. The Tunnel Profile must also have the Enable NAT-T Support option enabled. Refer to Creating a Tunnel Profile for creating a new tunnel profile.