Xforwarded Property

Hi Huseyin,

You can log the X-Forwarded-For value using an iRule to make sure it's being inserted:

when HTTP_REQUEST priority 501 {
   log local0. "XFF's: [HTTP::header values X-Forwarded-For]"
}

I wonder if Avaya can't handle multiple XFF header values. If that's the case, you could have LTM remove any existing XFF headers using a custom HTTP profile with the header to remove set to X-Forwarded-For and the header to insert set to X-Forwarded-For: [IP::client_addr].

If that's not it and you see the XFF being inserted from LTM, I'd try contacting Avaya again.

Aaron

Hi Aaron;

 

 

Yes, we see that XFF being inserted from LTM, so could you please contact with Avaya about the problem ?

 

 

Avaya Dialog Designer Version : 5.0.0.1802

 

Avaya VPMS Version : 5.0.0.2.0104

 

Avaya MPP Version : 5.0.0.2.0106

 

 

 

> LTM LOG :

 

 

F5 Server Ip : XXX.XX.XXX.70

 

App Server 1 Ip : XXX.XX.XXX.90

 

App Server 2 Ip : XXX.XX.XXX.91

 

 

local/tmm info tmm[5106]: Rule ivrist_prod_local_ltmlog : client: XXX.XX.XXX.73:54920 -> dest: XXX.XX.XXX.100:80

 

local/tmm info tmm[5106]: Rule ivrist_prod_local_ltmlog : client: XXX.XX.XXX.70:54921 -> dest: XXX.XX.XXX.91:9081

 

local/tmm3 info tmm3[5109]: Rule ivrist_prod_local_ltmlog : client: XXX.XX.XXX.94:36419 -> dest: XXX.XX.XXX.100:80

 

local/tmm3 info tmm3[5109]: Rule ivrist_prod_local_ltmlog : client: XXX.XX.XXX.76:38539 -> dest: XXX.XX.XXX.100:80

 

local/tmm1 info tmm1[5107]: Rule ivrist_prod_local_ltmlog : client: XXX.XX.XXX.94:36421 -> dest: XXX.XX.XXX.100:80

 

local/tmm1 info tmm1[5107]: Rule ivrist_prod_local_ltmlog : client: XXX.XX.XXX.76:38541 -> dest: XXX.XX.XXX.100:80

 

local/tmm1 info tmm1[5107]: Rule ivrist_prod_local_ltmlog : client: XXX.XX.XXX.70:38544 -> dest: XXX.XX.XXX.90:9085

 

local/tmm2 info tmm2[5108]: Rule ivrist_prod_local_ltmlog : client: XXX.XX.XXX.73:54922 -> dest: XXX.XX.XXX.100:80

 

local/tmm3 info tmm3[5109]: Rule ivrist_prod_local_ltmlog : client: XXX.XX.XXX.94:36423 -> dest: XXX.XX.XXX.100:80

 

local/tmm3 info tmm3[5109]: Rule ivrist_prod_local_ltmlog : client: XXX.XX.XXX.93:41807 -> dest: XXX.XX.XXX.100:80

 

local/tmm info tmm[5106]: Rule ivrist_prod_local_ltmlog : client: XXX.XX.XXX.73:54924 -> dest: XXX.XX.XXX.100:80

 

local/tmm info tmm[5106]: Rule ivrist_prod_local_ltmlog : client: XXX.XX.XXX.70:54927 -> dest: XXX.XX.XXX.90:9083

Hi,

 

 

I was suggesting you contact Avaya to resolve the issue. I'm not in a position to do this for you.

 

 

Aaron

If the LTM is inserting the XFF properly, but the Avaya isn't interpreting it, that's not something we can fix on the LTM side. If there is some specific requirement on how to (or how not to) format/configure the XFF, then we can certainly help with that, but we can only assist with things that are actually within the realm of F5 gear.

 

 

Colin