DHCP Server and NAT Service on the Data Plane
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.
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.
- 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.