Currently, several customers using NetScaler as a central resource consumption for use in large data centers to perform compensation.
If the application NetScaler switch as> = L3 switch is used, it is setup as a proxy. However, this leads to a loss of the client source IP. As a result, we have to insert the client connection information as part of the original data stream.
. For HTTP and SSL services, this is done by inserting the ClientIP address as HTTP header on the request to the server This is not possible for TCP-based services .
This disadvantage solved this feature . According to the three-way handshake with the server, a single packet is sent from the additional data to the server. This data is the 32-bit binary representation of the value entered as the CIP header, and then the complete TCP / IP header information for the packet will be prefixed, which are constructed induces the back-end connection.
This data begins with the start of the IP header to the end of the TCP header, including IPv6 extension headers, IPv4 options and TCP options accordingly. As such, the correct logic in the application must be included to ensure that the correct fields are analyzed
An additional package will be sent by the NetScaler to the server side, the following information :.
- Variable length: Client-side session information, there is a copy of the final ACK packet in client-side connection is used (only headers)
- IPV6 :. Basic IPv6 header is copied to the server side as it is. NetScaler does not have dual-stack IPv6 rather converts IPv6 packet to IPv4 and Layer 3 and after the upper layers processes the packet. Again, the packet of IPv4 is translated to IPv6. While convert original IPv6 header to IPv4 for TCP level proxing all extension headers are ignored. But for TCP CIP, we copy the original IPv6 basic header and forwards on the server side.
client IP header sample format that will be sent in the data array
For more information on this option configuration you can be found later in the article.
http://support.citrix.com/article/CTX205670
0 Komentar