Altostratus
MVPIn order to assist you we would really need to know the topology of the F5 and where connections originate from. The reason this information is necessary is because typically Virtual Servers (VS) do not have SNAT enabled by default and is typically configured to solve for a specific problem.
AltostratusThanks Paulius, of course. This is the topology. I tried with Npath routing but I cannot see original address, even I cannot see traffic in the virtual server forwarding layer 4 172.60.60.175. I configured in the loopback interface equally to this kb: https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm-implementations-11-6-0/5.html but is not possible connect.
MVPThe only way to resolve this would be to put the F5 in path rather than out of path, the way it is now.
.png){kind=link}