Users Guide

Table Of Contents
Client Operating
System
Supported Suite-B
IKE Authentication
Supported Suite-B IPsec
Encryption
l Windows client
NOTE: Windows client
operating system
includes Windows XP and
later versions.
l IKEv1 Clients using ECDSA
Certificates
l IKEv1/IKEv2 Clients using ECDSA
Certificates with L2TP/PPP/EAP-TLS
certificate user-authentication
l AES-128-GCM
l AES-256-GCM
Table 74: Client Support for Suite-B
The Suite-B algorithms described in Table 73 are also supported by Site-to-Site VPNs between Dell controllers,
or between a Dell controller and a server running Windows 2008 or StrongSwan 4.3.
Working with IKEv2 Clients
Not all clients support both the IKEv1 and IKEv2 protocols. Only the clients in Table 75 support IKEv2 with the
following authentication types:
Windows Client StrongSwan 4.3 Client VIA Client
l Machine authentication
with Certificates
l User name password
authentication using
EAP-MSCHAPv2 or PEAP-
MSCHAPv2
l User smart-card
authentication with EAP-
TLS / IKEv2
NOTE: Windows clients
using IKEv2 do not support
pre-shared key
authentication.
NOTE: Windows client
operating system includes
Windows 7 and later
versions.
l Machine authentication
with Certificates
l User name password
authentication using EAP-
MSCHAPv2
l Suite-B cryptographic
algorithms
l Machine authentication with
Certificates
l User name password
authentication using EAP-
MSCHAPv2
l EAP-TLS using Microsoft cert
repository
NOTE: VIA clients using IKEv2 do not
support pre-shared key authentication.
Table 75: VPN Clients Supporting IKEv2
Support for VIA-Published Subnets
Starting from ArubaOS 6.5, a new feature is introduced in controllers to support IKEv2 configuration (CFG_SET)
payload for VIA clients. This is in conformation with section 3.15 of
RFC 5996 applicable for route-based VPNs.
This feature is disabled by default.
When this feature is enabled, controllers can accept CFG_SET message with the INTERNAL_IP4_SUBNET
attribute type. When a controller receives this message, which consists of an IP address and netmask, it adds
an entry to the datapath route table that points to the VIA’s inner IP address as the next-hop. The datapath
route-cache for the VIA’s inner IP will point to the tunnel endpoint associated with the VIA.
Dell Networking W-Series ArubaOS 6.5.x | User Guide Virtual Private Networks |
344