Users Guide

Table Of Contents
Dell PowerConnect ArubaOS 5.0 | User Guide Remote Access Points | 181
local resources (for example, a local printer). The remote AP examines session ACLs to distinguish between
corporate traffic destined for the controller and local traffic.
Figure 30 Sample Split Tunnel Environment
Figure 30 displays corporate traffic is GRE tunneled to the controller through a trusted tunnel and local traffic is
source NATed and bridged on the wired interface based on the configured user role and session ACL.
Configuring Split Tunneling
To configure split tunneling:
z Define a session ACL that forwards only corporate traffic to the controller.
Configure a netdestination for the corporate subnets.
Create rules to permit DHCP and corporate traffic to the corporate controller. When specifying the action
that you want the controller to perform on a packet that matches the specified criteria, “permit” implies
tunneling, which is used for corporate traffic, and “route” implies local bridging, which is used for local
traffic.
You must install the PEFNG license in the controller. For information about user roles and policies, see
Chapter 10, “Roles and Policies” .
Apply the session ACL to a user role.
z Configure the AAA profile.
The AAA profile defines the authentication method and the default user role for authenticated users. The
configured user role contains the split ACL.
z Configure the virtual AP profile:
When configuring the virtual AP profile, you specify which AP group or AP the profile applies to.
Set the VLAN used for split tunneling. Only one VLAN can be configured for split tunneling; VLAN
pooling is not allowed.
When specifying the use of a split tunnel configuration, use “split-tunnel” forward mode.
Create and apply the applicable SSID profile.
arun_022
corporate
remote office
corporate traffic tunneled to
the controller
local traffic remains
local
local server
Note: 802.1x and PSK authentication is supported when configuring split tunnel mode.