DHCP Server and NAT Service on the Data Plane

DHCP and NAT are essential functions in SmartZone Data Plane (DP) deployments for tunneled WLANs. The DP can be configured to provide DHCP and NAT services directly, or these functions can be delegated to external servers, depending on network requirements and topology.

Note: The DHCP Server and NAT functions, when enabled, are exclusively supported for the assignment of IPv4 addresses to wireless clients.

DHCP and NAT Request Flow

When a wireless client connects to a tunneled WLAN, its traffic is encapsulated and forwarded to the Data Plane appliance. If the DP is configured as the DHCP server, DHCP requests from clients are terminated at the DP, which assigns IP addresses and lease parameters according to its configuration. If NAT is enabled, the DP translates internal client IP addresses to a public IP address for outbound traffic, allowing secure access to external networks.

  • DHCP Request Path:
    • Client sends DHCP DISCOVER/REQUEST over the tunnel.
    • DP intercepts and processes the request, responding with an IP assignment.
    • All DHCP traffic remains within the tunnel between the client and DP.
  • NAT Request Path:
    • Client traffic destined for external networks is routed through the DP.
    • DP performs address translation, mapping internal addresses to a configured public IP and port.
    • Outbound packets are forwarded to the upstream network with the translated address.

Remote Office Scenarios and Network Topology

Remote office deployments can use one of two topologies:

  • Data Plane at the remote site: In this topology, the Data Plane appliance is located at the branch site. WLAN traffic from local APs is tunneled to the DP. The DP typically provides DHCP and NAT services for all local clients, which simplifies management and ensures consistent address assignment and traffic routing.
    • Remote office APs establish tunnels to the DP.
    • The DP provides DHCP and NAT services for all tunneled WLAN clients.
    • The DP connects to the corporate WAN or the internet through its core network interface.
  • Data Plane at the central office: In this topology, the DP appliance resides in the central office. WLAN traffic from remote APs is tunneled across the WAN to the central DP. DHCP requests from branch clients travel through these tunnels to the DP, which assigns IP addresses and routes traffic back through the same tunnel. This design centralizes DHCP and NAT services but requires sufficient WAN bandwidth and low latency for optimal performance.
    • Remote APs tunnel WLAN traffic to the central DP.
    • DHCP requests and responses traverse the tunnel between the branch and the central DP.
    • The central DP connects directly to the corporate network and Internet.
    Note: For details on optimizing traffic flow and reducing latency, refer to Split Tunnel Profile.