08-01-2011 09:31 AM
We have recently transitioned one of our Ecommerce products to a new data center, at which we now use a one-armed load balancing approach rather then the routed load balancing approach we used previously. This is casuing us some issues as we generally log the source IP address a user comes in on when he fills out an application. Now the logs only show the natted ip address recieved by the load balancer, which does us no good. What I was hoping is that someone knew a way to log the source IP address when a new connection is created to a particular vip? Any ideas?
08-01-2011 09:48 AM
If this is http traffic you can have the ace insert a header such as X-Forwarded-For and insert the original client ip.
The you would have your server log this ip from the header (do google search on X-forwarded-for for server details )
see:
for how to do header insert.
IF the connection is not http the only way to preserve client ip would be to use policy-based routing to get the server return traffic back to the ace instead of using source nat.
08-01-2011 09:50 AM
The connections will be https.
08-01-2011 10:09 AM
If this is http traffic you can have the ace insert a header such as X-Forwarded-For and insert the original client ip.
So your saying something like....
header insert request X-Forwarded-For %is
and insert this parameter map to the virtual server? Will this work for HTTPS?
The you would have your server log this ip from the header (do google search on X-forwarded-for for server details )
see:
for how to do header insert.
IF the connection is not http the only way to preserve client ip would be to use policy-based routing to get the server return traffic back to the ace instead of using source nat.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide