Local Traffic Policy and forward to virtual not working

Hi,

 

Maybe not "not working at all" but for some reasons for some configs not :-(

 

I tried setup like that:

 

• VS1 - Standard, wildcard with pool containing default gateway IP (not really relevant here), SNAT enabled, Address and port translation disabled
• VS2 - ForwardingIP, wildcard

VS1 has LTP attached: forward to VS2

 

Client pointed at BIGIP selfIP as default gateway. Because VS1 has Source Address set to client IP VS1 is processing client request. From log it's obvious that traffic from VS1 is passed to VS2 then delivered to target server.

 

Setup like that is not working - forward to VS2 is completely ignored, traffic is passed directly to target server (same one as for first config)

 

• VSProxy - Standard, Explicit forward proxy profile attached, no pool, SNAT enabled, Address and Port translation disabled
• VS2 - same as above

VSProxy has same LTP attached

 

No traffic ever reaches VS2, client request is passed directly to target server. I know of course how VS with explicit proxy HTTP profile is working but can't understand why it's ignoring LTP and not forwarding traffic to VS2 - even if connection will not work then forward should not be ignored - but it is :-(

 

Sure there is Address/Port translation enabled but still...

 

When Address/Port translation is disabled on VSProxy connection fails completely but traffic is not hitting VS2 as well.

 

So either it's by design or it's kind of bug?

 

Piotr