Bug ID 466875: SNAT automap may select source address that is not attached to egress VLAN/interface

Last Modified: Aug 19, 2026

Affected Product(s):
BIG-IP LTM(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.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

Fixed In:
12.0.0, 11.6.3.3, 11.5.7

Opened: Jun 12, 2014

Severity: 3-Major

Related Article: K15586

Symptoms

Egress packets have a source address that is not associated with the VLAN or interface.

Impact

Packets may not be routed properly.

Conditions

Occurs when the following conditions are met: - Virtual utilizes SNAT automap. - There exists a route matching a self-ip on interface A to a VLAN on interface B.

Workaround

Use SNAT pool instead of automap.

Fix Information

SNAT Automap now matches self-ip against selected SNAT pool member instead of the pool member route.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips