SD‑LAN Service
SD‑LAN provides centralized forwarding using VxLAN‑GPE tunnels between APs and the Edge appliance. It supports Layer‑2 bridging and segmentation so user traffic is sent to the Edge and forwarded to the core network, DMZ, or L2GRE endpoints. While the Edge device provides Layer-2 bridging for the client traffic, it does not provide DHCP, Gateway or NAT functionality to the connecting clients.
The SD-LAN service is supported with an Active-Active cluster, not an Active-Standby cluster.
The following sections describe RUCKUS One features and functionalities that are compatible with the SD-LAN service.
IPSec Encryption for VxLAN-GPE Tunnels
VxLAN-GPE tunnels between APs and RUCKUS Edge devices support IPsec/IKE-based encryption, providing secure transport for VxLAN tunnel traffic. This enhancement ensures data confidentiality and integrity, particularly in distributed deployments where APs and Edge devices operate across different subnets or geographic regions.
Edge Delegation
Edge Delegation allows an MSP to define policies and configuration in RUCKUS One, while the Edge appliance executes those services locally. This includes SD‑LAN, mDNS, ARP handling, and other local functions. The MSP manages multiple customer sites centrally, and each Edge appliance performs delegated tasks at the site.
mDNS
The Edge appliance acts as an mDNS gateway, enabling device discovery (such as printers, casting devices, and IoT) across VLANs or segments. mDNS requests, directed to the sites where mDNS services are discovered, thus reducing flooding. mDNS service advertisements are allowed to be flooded into the service VLAN as per configuration to enable service discovery across VLANs or segments.
Application Visibility
Provides traffic identification and monitoring to help administrators understand application usage and optimize policies at the site.
ARP Termination
The Edge appliance does the ARP suppression to reduce forwarding ARP broadcast packets for SD‑LAN, PIN, and other tunneled segments. It builds ARP cache by listening to ARP traffic and responds to ARP requests locally by using the ARP cache, thus reducing broadcast traffic upstream.