Having trouble with destination based SNAT irule

The recommendation from F5 is to do the very same thing, to create an irule that strips the route-domain off the destination address (remote_addr) before making a comparison against the strings in the data group.

 

 

To be completely honest, I'm very disappointed that a feature that should be a no brainer in usage and application has been broken since the introduction of 10.x and route domains for nearly 2 years into the current release of 11.x.

 

 

We have a ticket open for an enhancement request via our account teams and have this escalated (most likely put with what I imagine is a pile of other similar requests from other companies).

 

 

Performing semi-complex string manipulation via TCL for in depth iRules (this is a simple example compared to most of our real world applications that would exist within route domains) is not something that I would consider user-friendly. This basically limits the daily usage and development of iRules to a handful of staff that are skilled in TCL scripting. Not exactly what I'd expect when paying a premium for a product against competitive offerings, so I hope that F5 understands the significance of this limitation and the burden of the work around and addresses it sooner rather than later.