Bug ID 511398: Tunnels come up with incorrect ipsec-policy remote IP address configuration

Last Modified: Aug 19, 2026

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

Known Affected Versions:
11.5.1, 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, 11.5.2 hf1, 11.5.3, 11.5.3 hf1, 11.5.3 hf2, 11.5.4, 11.5.4 hf1, 11.5.4 hf2, 11.5.4 hf3, 11.5.4 hf4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Fixed In:
12.0.0

Opened: Mar 09, 2015

Severity: 3-Major

Related Article: K45148021

Symptoms

IKE/IPsec SAs come up fine. but traffic does not pass.

Impact

Traffic does not pass, and the system posts an ICMP error message.

Conditions

Configure ipsec-policy with an incorrect remote IP address.

Workaround

Correct the remote IP address in the ipsec-policy configuration.

Fix Information

When the responder side ipsec-policy remote IP address is configured with wrong IP address, tunnel negotiation now fails, which is correct behavior.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips