For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Jose_Santiago_O's avatar
Jose_Santiago_O
Icon for Nimbostratus rankNimbostratus
Jan 16, 2009

Implementing TCP Lan Optimized Profile.

Hi,     I want to implement the tcp lan/Wan Optimized Profile, my boxes are 6400 running ltm 9.3.1 HF4.     I have some doubts about it, that will enumerate here.     ...
config
design
Josh_41258's avatar
Josh_41258
Icon for Nimbostratus rankNimbostratus
Jan 21, 2009

First, OneConnect uses the source IP address which initiated the TCP connection for all subsequent packet transfers. So in our web logs, we could not distinguish clients based on the source IP address without doing something fancy. And though we never tested this, I believe there would be some problems with Cookie-based persistence.

 

 

 

Maybe I completely misunderstood this.. but, it sounds like your web logs are probably showing the self IP of the LTM, not of the actual source (being the client). You can easily get around this by using the X-Forwarded-For HTTP header. Configure your webserver to use this header in it's logging mechanism... If you are using Apache, no extra modules are needed:

 

 

LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"%Du" combined

 

 

Then, make sure the "X-Forwarded-For" header is enabled in your HTTP profile. After this, you should see the real source IPs in your web logs.

 

 

Josh