Bug ID 750712: A pool with allow-snat set to 'no' will permanently disable snat for the connection.

Last Modified: Jan 20, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,, 17.0.0,,

Opened: Nov 21, 2018
Severity: 3-Major


A server-side connection is established that does not use a source address translation address even though a source address translation should apply.


Incorrect source address used for some server-side connections.


A virtual server is configured to use more than one pool and the pools have a combination of allow-snat yes (the default) and allow-snat no. Multiple pools could be configured through an iRule or L7 policy. Multiple requests are made on a connection. After a request is sent to a pool with allow-snat set to no, future requests on the connection that use an allow-snat yes pool will not use source-address translation even though the configuration implies that they should.


When altering the pool selection per request, also explicitly set the source address translation if necessary.

Fix Information


Behavior Change