This guide outlines the various methods available to ensure that the backend server is equipped to collect the original client IP through the NetScaler. The focus of this article lies in configuring the NetScaler to effectively forward the original client source IP to the backend server.

Instructions

Inserting Client IP in Various Scenarios on NetScaler

1. Insert Client IP in HTTP Header: For the insertion of the client IP into the HTTP header, follow the configuration steps outlined in the official documentation: Insert Client IP in HTTP Header.

2. Insert Client IP in Proxy Protocol Header in TCP Payload:

   • In versions prior to 13.0, you can use a rewrite policy to send a proxy protocol header containing client information to the backend server. Detailed information can be found in CTX224265.
   • In 13.0/13.1 versions, proxy protocol configuration can be achieved through the net profile. Refer to the official documentation for configuration steps: Proxy Protocol Configuration.

3. Insert Client IP in TCP Option:

   • In version 13.0, utilize the tcp profile to configure the insertion of the client IP through a TCP option. For detailed instructions, visit: Insert Client IP in TCP Option.

4. Using USIP Mode: To set up NetScaler for using the client's IP address as the source IP for connections to the backend server, navigate through the instructions provided in the official documentation: USIP Mode Configuration.

These approaches empower administrators to seamlessly integrate various methods to include the client IP address in different scenarios, enhancing data accuracy and facilitating efficient network management.