When used with ArubaOS 8.x, the VIA solution includes the VIA Client and the Mobility Master and managed device configuration .

VIA Client: Remote workers and mobile users can install VIA on their computers or mobile devices to connect to their enterprise network from remote locations.

Mobility Master and managed device configuration: To set up a Mobility Master and a managed device for remote users, configure the user roles, authentication profile, and connection profile using either the WebUI or CLI.

VIA 3.x requires the PEFV or VIA license and is supported on 7200 Series, 7000 Series, and virtual mobility controllers.

If a user is connected from a remote location outside the enterprise network, VIA automatically classifies the environment as untrusted and creates a secure IPsec connection between the user and the enterprise network. After the user moves to a trusted network, VIA detects the network type and moves to an idle state by dropping the IPsec connection.

VIA can be downloaded using one of the following methods:

The URL provided by a local system administrator

An app store (for Android and iOS)

Installation by a system administrator using system management software

Figure 1  VIA Topology

When used with ArubaOS 6.5.x, the VIA solution includes the VIA Client and the standalone or master/local controller configuration .

VIA Client: Remote workers and mobile users can install VIA on their computers or mobile devices to connect to their enterprise network from remote locations.

Standalone controller or master/local controller configuration: To set up a controller for remote users, configure the user roles, authentication profile, and connection profile using either the WebUI or CLI.

VIA requires the PEFV license and is supported on 7200 Series and 7000 Series controllers.

If a user is connected from a remote location outside the enterprise network, VIA automatically classifies the environment as untrusted and creates a secure IPsec connection between the user and the enterprise network. After the user moves to a trusted network, VIA detects the network type and moves to an idle state by dropping the IPsec connection.

VIA can be downloaded using one of the following methods:

The URL provided by a local system administrator

An app store (for Android and iOS)

Installation by a system administrator using system management software

Figure 2  VIA Topology

Connection Behavior

VIA provides a seamless connectivity experience for users when accessing an enterprise or corporate resource (example: workstation, server) from an untrusted or trusted network connection. By default, VIA automatically launches and establishes a remote connection when you log in to your system from an untrusted network.

The following table explains the typical behavior of VIA:

The events described in Table 1 do not always occur in the same order.

Table 1: VIA Connectivity Behavior

User Action/Environment	VIA Behavior
The client or user moves from a trusted to untrusted environment. For example, from an office to a public hotspot.	Automatically launches and establishes cnnection to the remote network.
The client moves from an untrusted to a trusted environment.	Automatically launches and stays idle. VIA does not establish a remote connection. However, you can connect to a network manually by selecting the appropriate connection profile under Settings.
While in an untrusted environment, the user disconnects the remote connection.	Disconnects from the network.
User moves to a trusted environment.	Stays idle and does not connect.
User moves to an untrusted environment.	Stays idle and does not connect. This usually occurs if the user has previously disconnected a secure connection in VIA. Users can manually connect using the default connection profile by right-clicking the VIA icon in the system tray and selecting the Connect option.
User clicks the Connect button.	Establishes remote connection.
In an untrusted environment, user restarts the system.	Auto-launches and establishes remote connection.
In an untrusted environment, user shuts down the system, moves to a trusted environment, and restarts the system.	Auto-launches and stays idle.