Contents tagged with Protocol
-
Remote client IP identification using F5 NLB
Are you struggling to identify the IP traffic source on your servers? When using a F5 NLB at the edge of your network, you won’t be able to identify on your servers where the traffic is coming from. That is unless the protocol can support adding the proper headers to leave a trace of the original IP address. Any traffic received by the server appears to be coming from one of the load balancer IP addresses, which makes it impossible for you to identify the real source of traffic.