Bug ID 473527: IPsec interop problem when using AES-GCM.

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.1 HF1

Opened: Jul 29, 2014

Severity: 2-Critical

Symptoms

BIG-IP AES-GCM negotiation through IKEv2 does not accept the case of no integrity algorithm. This can happen with the tunnel configured to use AES-GCM.

Impact

The IPsec tunnel will not be established.

Conditions

When configuring IPsec tunnel to use AES-GCM to inter-operate between two BIG-IPs of version 11.6 and 12.0, or configuring IPsec tunnel on a BIG-IP of 11.6 to inter-operate with another vendor using AES-GCM.

Workaround

For BIG-IP only, ensure both sides of the tunnel are the same release level.

Fix Information

Do not include integrity algorithm for AES-GCM.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips