Bug ID 601916: IPsecALG resources remain in use after IPsec clients switch to NAT-T

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP AFM, CGN(all modules)

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1

Opened: Jun 28, 2016
Severity: 3-Major

Symptoms

IPsecALG resources will remain in use even after IPsec clients switch to NAT-T and do not send ESP packets. ESP connections will be setup, but not used. They will remain until the 'idle-timeout' specified in the IPsecALG profile has been reached. Translation endpoints will be unavailable until the 'idle-timeout' specified in the IPsecALG profile has been reached.

Impact

IPsec clients that are not using NAT-T will not be able to establish connections if the translation addresses are in use to the same server. This condition will clear after the IPsecALG profile 'idle-timeout' expires.

Conditions

An IPsecALG profile is attached to a UDP virtual to handle IKE traffic with LSN or AFM FW-NAT enabled. IPsec clients detect the NAT and transition to NAT-T instead of sending ESP packets.

Workaround

None

Fix Information

None

Behavior Change