When the Edge SWG (ProxySG) is making outbound connections, you want it to send the IP address of the clients that initiate the requests.
You need to monitor outbound traffic but you are unable to determine the origin due to the Edge SWG (ProxySG) sending it's own IP address as the source.
The Reflect Client IP option is only supported in transparent Edge SWG (ProxySG) deployments.
By default, the Edge SWG (ProxySG) uses its own IP address as the source IP address for requests (when connecting to servers). If Reflect Client IP is enabled, the Edge SWG (ProxySG) uses the client IP address for all requests. Enabling this option is not an arbitrary decision; it depends on the deployment and role of the Edge SWG (ProxySG). For example, if this Edge SWG (ProxySG) is acting as a branch peer in an Application Delivery Network (ADN) deployment, enable client IP address reflection. This provides maximum visibility for network usage statistics and enables user-based access control to network resources.
However, if you have asymmetric routing from the internet to your client workstations (usually the case in explicit proxy deployment mode), you may not want to enable this setting as it will cause connections to break since the return packets from the server may never reach the Edge SWG (ProxySG).
Enable Reflect Client IP (globally) using the Management Console:
Configure Reflect Client IP for specific requests using the Visual Policy Manager:
* You can add other criteria to the rule such as destination request URL in order to make it a specific match.
** You will need to install policy for the changes to take effect.
Configure Reflect Client IP (globally) using the command line interface:
ProxySG#configure terminal
ProxySG#(config)general
ProxySG#(config general)reflect-client-ip {enable | disable}