Dell 6.2 Figure 160: , Figure 161: , Figure 162:

511| Remote AccessPoints DellPowerConnect W- Series ArubaOS 6.2 | UserGuide
Figure 160: Remote AP with a Private Network
lDeployment Scenario 2: Theremote AP is on the public network or behind a NAT device and the controller is
on the publicnetwo rk.The remote AP must be configured with the tunnel termination point which must be a
publicly-routableIP address. In this scenario, a routable interface is configured on the controllerin the DMZ. The
remote AP uses the controller’sIP address on the public network to establish the IPSec VPN tunnel.
Figure 161: Remote AP with Controller on Public Network
lDeployment Scenario 3: Theremote AP is on the public network or behind a NAT device and the controller is
also behinda NA T device. (Dellrecommends this deployment for remote access.) The remote AP must be
configuredwit h the tunneltermination point which must be a publicly-routable IP address. In this scenario, the
remote AP uses the public IP address of the corporate firewall.The firewall forwards traffic to an existing
interface onthe controller. (The firewallmust be configured to pass NAT-T traffic (UDP port 4500) to the
controller.)
Figure 162: Remote AP with Controller BehindFirewall
In any of the describeddeployment scenarios, the IPSec VP N tunnelcan be terminated on a local , with a master
controllerlocated elsewhere in the corporate network (Figure 163). The remote AP must be able to communicate
with the master controllerafter the IPSec tunnel is established. Make sure that the L2TP IP pool configured on the
localc ontroller(from which the remote AP obtains its address) is reachable in the controllernetwork by the master
controller.