Selective SNAT rule

Eric: I apologize. This was only just changed in 9.2. You can work around it by disabling Rule validation with the following command:

[root@gumby:Active] config  bigpipe db Rule.Validation none

You do need to use LB::reselect because when the LB_SELECTED event is triggered, both the server and snat have already been picked. Using just the snat command will not change the snat behavior at that point.

Note: In 9.2, the LB_SELECTED event will be fired again after the LB::reselect (this is because a new LB decision is being made). You should add some logic to not reselect the snat if it has already happened once otherwise you'll create an indefinite loop (using a variable is usually easiest).

Brian: He actually wants to disable snat based on the server that was picked, not the clientside source address.