Client IP visibility issue at Remote Server

Reply
Highlighted
L3 Networker

Client IP visibility issue at Remote Server

Hi Team,

Below is possible in paloalto side?

 

Note: there is no proxy in between client and paloalto

 

Problem description :

The clients behind PA firewall connecting to AWS NLB then connecting to our AWS web servers(https:// tallysolutions.com).  Now we are not able to see the actual client ip address in the AWS Web server.  To resolve this issue AWS team suggested to insert XXF header in the client traffic. Can we achieve this in PA?

 

As per AWS :

" The internal ALB appends the NLB’s private IP address in the X-Forwarded-For header before sending to a request to the backend targets. Therefore, if the requests from the clients contain X-Forwarded-For header, the backend targets will see the clients’ actual IP addresses along with the private IP address of the NLB in the X-Forwarded-For header. Otherwise, the backend targets will only see the NLB’s private IP address in the X-Forwarded-For header. "

 

Can anyone help me here?

 

-

Regards,

Sethupathi M

Highlighted
L2 Linker

Re: Client IP visibility issue at Remote Server

@Sethupathi As the file does not act as proxy for the traffic, it is not able to modify the HTTP header and insert "x-forwarded-for"

Highlighted
L7 Applicator

Re: Client IP visibility issue at Remote Server

Hello,

Check the config on the load balancer. some have the option to let you see the source IP after the LB. However this is a common issue with using LB's.

 

Sorry its not a solution :(.

 

Regards,

Highlighted
L4 Transporter

Re: Client IP visibility issue at Remote Server

@Sethupathi i agree with @OtakarKlier , this can be control on LB itself. There are two options on LB as follows

 

1. Without SNAT. here client actual IP address is send to server but in this case mostly asymmetric routing issues are observed as most of the times, application server default gateway is not set to LB.

 

2. To avoid above issue, SNAT is enabled which actually NATs client IP address with one of the LB IP while sending request to application server.

If you want to see actual client IP on server side with SNAT enabled, you need to enable X-forwarder-for setting on LB side which actually adds client IP under header while sending request to web server.

 

hope it helps!

 

Mayur



Mayur Sutare
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!