F5-LTM-ROUTING

The reason that you would use source address translation is to cause the response to return via the LTM, and not directly to the client.

You could disable source address translation if your pool members are configured to route traffic via the LTM, eg, if their default route points to the LTM.

Alternatively, for HTTP traffic only, you could have the LTM insert a X-Forwarded-For header with the client's original IP address.

F5 provides an ISAPI Plug-in, which you can download from the LTM's default page (click on the red f5 ball to get back to it) if you wish the client IP to be written to the IIS logs. See SOL4816 for more information on this.

Hi LAN,

Thank you so much for the response

Here in my case, we want clients original ip to be remained for the EXCHANGE traffic alone, when exchange admins capture the traffic they would like to see who are the users sending emails and their original IPs for the troubleshooting purpose

Oh we are using iAPP, even if we are using iAPP and if i create http profile with Insert-X-Forwarded-For enabled and once i associate this to MAILservers vip will it work ? when exchange admins capture the traffic will they able to see that who are all sending emails

Thanks again for your quick response

thank you for your valuable input