Creating an IPsec Profile

The IPsec profile enables secure, encrypted tunneling for access points and Data Plane connections using industry-standard protocols. When applied, the profile determines authentication, encryption, and tunnel type assignment, allowing you to control how traffic is protected across the network.
Note: Assign an IPsec Profile to a Zone in the AP GRE Tunnel Options within the Edit Zone: configuration page.

Assigning an IPsec Profile to a Zone

Attention: RUCKUS GRE tunnels support IPsec only when the following settings are present in the tunnel profile:
  • Ruckus Tunnel Mode is GRE.
  • Tunnel Encryption is Disable.
If any of these settings is missing from the RUCKUS GRE tunnel profile, the RuckusGRE option is grayed out for the IPsec Tunnel Mode field in the AP GRE Tunnel Options of the Zone.

RuckusGRE Required Profile Configuration for IPsec Support

Complete the following steps to create an IPsec profile for secure tunneling that can later be used for encrypting RuckusGRE or SoftGRE tunnels.
  1. In the controller web UI, select Services > Tunnels & Ports > IPsec.
  2. Click Create.
    The Create IPsec Profile dialog box is displayed.
  3. Under General Options, configure the following:
    • Name: Enter a name for the profile.
    • Description: Enter a description for the profile.
    • Security Gateway: Enter the IP address or fully-qualified domain name (FQDN) of the IPsec server. If you use the IP address, the IP address format that you must enter will depend on the IP mode that is configured on the controller (IPv4 or IPv6).
    • Tunnel Mode: Select SoftGRE or RuckusGRE.
    • IP Mode: Select IPv4 only or IPv6 only. This setting determines which IP protocol version the IPsec tunnel uses for communication. Choose IPv4 only for networks that use IPv4 addressing or IPv6 only for networks that use IPv6.
  4. The remaining configuration options depend on whether you select SoftGRE or RuckusGRE as the tunnel mode.
    To complete the configuration, refer to one of the following topics:

Configuring an IPsec Profile for SoftGRE Tunnels

Complete the following steps to create an IPsec profile that will define how a SoftGRE tunnel is encrypted.
  1. In the Create IPsec Profile dialog box, select SoftGRE as the tunnel mode.

    Creating an IPsec Profile for SoftGRE Tunnels

  2. For IP Mode, select IPv4 only or IPv6 only. This setting determines which IP protocol version the IPsec tunnel uses for communication.
  3. Under Authentication, choose one of the following types:
    • Preshared Key. Use a preshared key (PSK) for authentication. The PSK you enter must be 8 to 128 ASCII characters.
    • Certificate. Use an X.509 certificate from a certificate authority (CA) or registration authority (RA) server. The controller uses the CMPv2 protocol to obtain the signed certificate from the CA or RA server. For more information about certificate validation, refer to Data Plane Certificates.
  4. Under Security Association, set the IKE Proposal Type and ESP Proposal Type fields to one of the following:
  5. Under Rekey Options, configure the following options:
    • Internet Key Exchange. The Internet Key Exchange (IKE) Rekey Time setting controls how often the system renegotiates the keys used to secure the IKE phase of your VPN tunnel. Enter a value and select the unit (day, hour, or minute). To disable automatic rekeying, select the Disable checkbox.

    • Encapsulating Security Payload. The Encapsulating Security Payload (ESP) Rekey Time setting controls how often the system renegotiates the keys for encrypting and authenticating data packets in the tunnel. Enter a value and select the unit (day, hour, or minute). To disable automatic rekeying, select the Disable checkbox.
      Attention: Regular rekeying helps maintain security by replacing old keys with new ones at set intervals. If disabled, the system will not automatically renegotiate IKE or ESP keys, instead, it will use the same key until manually reset or the session ends, which may reduce security if the key is exposed.
  6. Under Advanced Options, configure the following options:
    • DHCP Option 43 Sub Code for Security Gateway: Devices use the DHCP Option 43 subcode to discover the address of the security gateway. Keep the default subcode (7) unless your network requires a different subcode for gateway discovery.
      Attention: Devices may fail to locate the gateway if the subcode does not match your network configuration.
    • Retry Limit: Set the number of times that the controller will attempt to discover the address of the security gateway. The default retry count is 5. Accepted values are 1 through 16. Increase the limit to improve connection reliability; decrease to reduce network traffic. Disable the retry functionality by clicking the Disable checkbox. If disabled, the controller will not attempt to discover the address of the security gateway after the first failed attempt.
    • Replay Window: This setting defines how many data packets the system tracks to protect against replay attacks. A replay attack occurs in the Encapsulating Security Payload (ESP) phase when an attacker intercepts and resends valid data packets to disrupt or compromise the connection. A larger replay window allows the system to accept packets that arrive out of order, which can happen in busy or unstable networks. This helps prevent legitimate packets from being rejected. A smaller window uses less memory but may drop valid packets if they arrive out of order. If disabled, the system will not check for duplicate or replayed packets, which can expose your tunnel to security risks.
    • IP Compression: Enables IP Payload Compression Protocol (IPComp) before encrypting traffic in the VPN tunnel. Use this option to reduce the size of data packets, which can improve bandwidth efficiency, especially on slow or congested links.
      Attention: Enable only if both ends of the tunnel support IPComp and your network benefits from reduced packet size.
    • Force NAT-T: Network Address Translation Traversal (NAT-T) ensures that VPN traffic can pass through NAT devices without being blocked. When enabled, this option enforces UDP encapsulation for ESP packets, which is required for NAT-T. Enable this option if devices are behind a NAT device, such as a firewall or router.
    • Dead Peer Detection: Monitors the health of the remote VPN peer using periodic checks. If the peer becomes unreachable, the system can quickly terminate or renegotiate the connection. If disabled, the system does not check peer status; failed connections may persist until manually reset. As a best practice, enable this setting for reliable VPN operation unless troubleshooting requires it to be off.
      Note: When you clear the Disable checkbox for Dead Peer Detection, the Delay field becomes available. This field defines the interval in seconds between Dead Peer Detection probes that check if the peer is still active. The range is 1 to 65536 seconds. A shorter delay detects failures faster but increases probe traffic, while a longer delay reduces traffic but may take more time to identify a dead peer.
    • NAT-T Keep Alive Interval: Sets how often the system sends keepalive messages to maintain NAT mappings. NAT devices may close idle connections. Sending regular keepalive messages prevents this, ensuring the VPN tunnel remains open. Enter a value (in seconds) to set the keepalive interval for NAT traversal. By default, this option is enabled and the interval set to 20 seconds. Accepted values are 1 to 65536. To disable the keep alive interval, click Disable.
    • FailOver Options: Control how APs respond when unable to connect to the security gateway in the following way:
      • Retry Period: Set the number of days during which APs will keep attempting to connect; accepted values are 3 through 65536. Select the Forever checkbox to keep trying indefinitely (this is the default setting).
      • Retry Interval: Set the interval (in minutes) between each retry attempt. The default retry interval is 1 minute. Accepted values are from 1 through 30 minutes.
      • Retry Mode: Click Revertive if you want APs to fall back to the specified primary security gateway. Click Non-revertive (the default setting) if you want APs to maintain connectivity with the security gateway to which they are currently connected.

  7. Click OK.
    The dialog box is closed. The profile configuration is saved and listed on the IPsec page.

Configuring Specific IKE and ESP Proposals for SoftGRE Tunnels

If you are choosing to configure specific proposals for IKE and ESP, use the following as a guide to set up the different variables according to your network needs.
IPsec secures IP traffic by encrypting and authenticating packets. It is composed of two main actors:
  • Internet Key Exchange (IKE): Negotiates Security Associations (SAs) and cryptographic keys between endpoints.
  • Encapsulating Security Payload (ESP): Encrypts and authenticates actual IP packets after IKE negotiation.
    Note: IKE and ESP work together to provide confidentiality, integrity, and authentication for VPN tunnels.
A proposal is a set of cryptographic algorithms and parameters offered during negotiation. Each proposal includes choices for encryption, integrity, Pseudo-Random Function (PRF), and Diffie-Hellman (DH) group. Multiple proposals can be added to allow negotiation flexibility. During negotiation, IPsec peers select the first matching proposal supported by both sides.

IKE proposals define how endpoints negotiate the secure channel. To create a custom IKE proposal, complete the following steps:

  1. Set the IKE Proposal Type to Specific and select the Encryption Algorithm, Integrity Algorithm, Pseudo-Random Function, and DH Group according to your needs as explained in Parameter Selection Table for IPsec Proposals.
    Note: Match PRF strength to integrity algorithm for consistency
  2. Click Add to add the configured proposal.

    Configuring a Specific IKE Proposal

  3. Set the ESP Proposal Type to Specific and fill the Encryption Algorithm, Integrity Algorithm, and DH Group according to your needs as explained in Parameter Selection Table for IPsec Proposals. The available options defined in Parameter Selection Table for IPsec Proposals are organized from most secure to least secure for each parameter.
  4. Click Add to add the configured proposal.
  5. Parameter Selection Table for IPsec Proposals

    Parameter Available Options Recommended Use Limitations
    Encryption Algorithm: Determines how data is transformed into an unreadable format during transmission. It protects the confidentiality of information sent over the VPN tunnel. AES256 Use for highly sensitive data, compliance-driven environments, or when long-term confidentiality is a priority. Higher CPU usage may impact performance on resource-constrained devices.
    AES192 Use when AES256 is unavailable or not supported by peer devices, but you require stronger protection than AES128. Slightly slower than AES128; not as widely supported as AES128 or AES256.
    AES128 Use for general enterprise traffic, performance-sensitive applications, or when compatibility with legacy systems is required. Lower security margin compared to AES256; may not meet some regulatory requirements for highly sensitive data.
    3DES Use only if required for interoperability with legacy equipment that does not support AES. Considered weak by modern standards; slow and resource-intensive; vulnerable to cryptographic attacks.
    Integrity Algorithm: Verifies that data has not been altered during transit. It generates a cryptographic hash for each packet, allowing the receiver to detect tampering or corruption. SHA512 Use for environments with strict compliance requirements or where maximum integrity assurance is needed, such as critical infrastructure or classified data. Increased CPU and memory usage; may not be supported on all devices.
    SHA384 Use for sensitive data flows, regulatory compliance, or when SHA512 is not supported but higher security than SHA256 is required. Higher resource consumption than SHA256; may not be universally supported.
    SHA256 Use for most enterprise deployments, including VPNs, remote access, and internal communications. Balances security and performance. None significant; recommended for most use cases.
    AES-XCBC Use for IoT, embedded systems, or mobile devices where computational resources are limited. Limited support in some platforms; not as widely adopted as SHA family.
    SHA1 Use only if required for interoperability with older systems that do not support SHA256 or higher. Vulnerable to collision attacks; not recommended for new deployments.
    MD5 Outdated integrity algorithm, included only for legacy support. Avoid in all new deployments; use only if absolutely required. Severely compromised security; susceptible to collision and preimage attacks.
    Pseudo-Random Function: Used during key exchange to generate cryptographic keys from shared secrets. It ensures that the keys used for encryption and authentication are unpredictable and unique for each session. The strength of the PRF directly affects the security of the keying material. PRF-HMAC-SHA512 Use for high-security environments, compliance-driven deployments, or when maximum key strength is needed. Increased computational overhead; may not be supported on all devices.
    PRF-HMAC-SHA384 Use for sensitive applications or when SHA512 is unavailable but higher security than SHA256 is desired. Slightly higher resource usage than PRF-HMAC-SHA256.
    PRF-HMAC-SHA256 Use for most enterprise VPNs and secure communications; recommended for interoperability and strong security. None significant; widely supported and recommended.
    PRF-AES-XCBC / AES-CMAC Use for IoT, embedded, or mobile deployments where performance is critical. Limited compatibility; may not be supported by all platforms. PRF-AES-CMAC is newer, standardized by NIST, and generally preferred, but PRF-AES-XCBC remains supported for compatibility.
    PRF-HMAC-SHA1 Use only if required for legacy interoperability. Weaker security; not recommended for new deployments.
    PRF-MD5 Avoid in all new deployments; use only if absolutely required for legacy interoperability. Insecure; vulnerable to attacks.
    Use integrity ALG Select this option to automatically use the same algorithm as the Integrity Algorithm for the PRF. This simplifies configuration and ensures consistency between integrity and PRF settings. Only available when the selected Integrity Algorithm is supported as a PRF. Not all integrity algorithms are valid PRFs; verify compatibility with your peer device.
    DH Group: Defines the mathematical parameters for securely exchanging cryptographic keys between endpoints. ECP384 (Group 20) Use for new deployments where both endpoints support elliptic curve groups; preferred for high security and performance. Requires support on both endpoints; may not be compatible with legacy systems.
    MODP8192 Use for government, financial, or other environments with strict regulatory requirements. Very slow; high resource consumption; may not be supported on all devices.
    MODP6144 Use for compliance-driven deployments where MODP 8192 is not supported but higher security than MODP 4096 is required. Slow performance; increased resource usage.
    MODP4096 Use for sensitive data, compliance, or when MODP 6144/8192 are not supported. Higher CPU load; slower negotiation.
    MODP3072 Use for enterprise VPNs and secure communications where MODP 4096 is not required. Higher resource usage than MODP 2048.
    MODP2048 (Group 14) Use for most enterprise VPNs and secure communications; balances security and performance. May not meet the highest compliance standards for long-term confidentiality.
    MODP1536 / 1024 / 768 Avoid in all new deployments; use only if required for legacy interoperability. Deprecated; weak security; vulnerable to attacks.
    None Use when you do not require Perfect Forward Secrecy (PFS) for the ESP phase. Select None to disable PFS for this proposal. This may be needed for compatibility with certain peers or to meet specific security requirements. Disables PFS for the ESP phase, which may reduce the security of the tunnel. Not recommended unless required for interoperability or policy reasons.
  6. Continue to add additional proposals for more flexible negotiation capabilities.
  7. Use the Cancel and Delete options to cancel an ongoing proposal configuration or delete a proposal, respectively.
    Attention: List strongest proposals first. Add fallback proposals for compatibility with legacy systems.
  8. Continue to finish the profile configuration parameters as explained in Configuring an IPsec Profile for SoftGRE Tunnels.

Configuring an IPsec Profile for RuckusGRE Tunnels

Complete the following steps to create an IPsec profile that will define how a RuckusGRE tunnel is encrypted.
  1. In the Create IPsec Profile dialog box, select RuckusGRE as the tunnel mode.

    Creating an IPsec Profile for RuckusGRE Tunnels

  2. Under Authentication, the Certificate option is preselected as the only available option for this tunnel type. This type uses an X.509 certificate from a certificate authority (CA) or registration authority (RA) server. The controller uses the CMPv2 protocol to obtain the signed certificate from the CA or RA server.
    Note: For more information about certificate validation, refer to Data Plane Certificates.
  3. Under Security Association, the Specific option is preselected as the only available option for the proposal types for this tunnel type. Select the algorithm combinations for IKE and ESP proposal from the following options:
    • AES128-SHA1-MODP2048: Provides AES-128 encryption for confidentiality and SHA-1 for integrity and authentication. Uses Diffie-Hellman Group 14 (MODP 2048) for secure key exchange. This combination offers moderate security and is suitable for environments where legacy compatibility is required.
    • AES256-SHA384-ECP384: Provides AES-256 encryption for strong confidentiality and SHA-384 for enhanced integrity. Uses Elliptic Curve Group 19 (ECP 384) for efficient and secure key exchange. This combination offers high security and is recommended for modern deployments requiring robust encryption. This is the default setting.
  4. Under Rekey Options, configure the following options:
    • Internet Key Exchange. The Internet Key Exchange (IKE) Rekey Time setting controls how often the system renegotiates the keys used to secure the IKE phase of your VPN tunnel. Enter a value and select the unit (day, hour, or minute). The default setting is 4 hours.

    • Encapsulating Security Payload. The Encapsulating Security Payload (ESP) Rekey Time setting controls how often the system renegotiates the keys for encrypting and authenticating data packets in the tunnel. Enter a value and select the unit (day, hour, or minute). The default setting is 1 hour.
  5. Under Advanced Options, configure the following options:
    • FailOver Options: Control how APs respond when unable to connect to the security gateway in the following way:
      • Retry Period: Set the number of days during which APs will keep attempting to connect; accepted values are 3 through 65536. Select the Forever checkbox to keep trying indefinitely (the default setting).
      • Retry Interval: Set the interval (in minutes) between each retry attempt. The default retry interval is 1 minute. Accepted values are from 1 through 30 minutes.
      • Retry Mode: Click Revertive if you want APs to fall back to the specified primary security gateway. Click Non-revertive (the default setting) if you want APs to maintain connectivity with the security gateway to which they are currently connected.

  6. Click OK.
    The dialog box is closed. The profile configuration is saved and listed on the IPsec page.