For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Feng_Zhang_01_1's avatar
Feng_Zhang_01_1
Icon for Nimbostratus rankNimbostratus
Apr 07, 2014

client ip address unstable fails "source ip affinity"

We used source ip affinity in our F5 configuration, but it is not working as expected: A java client is getting load balanced to different instances within a minute. We noticed that client ip address changes after through x-forward-for address log. For example, a x-forward-for address example is "192.168.0.1, 172.16.0.1, 10.0.0.1", we can see for the failed client, the ip address we record using request.getHeader(X_FORWARDED_FOR_HEADER) some times return "192.168.0.1", sometimes return "10.0.0.1". Does anyone know the solution?

 

1 Reply

  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    Apr 07, 2014

    This likely isn't due to a problem with your BIG-IP. Sounds like your client could have multiple egress points in their local network. Some device in their network could also be inserting the X-forwarded-for header.

     

    Taking the X-forwarded-for header out of the mix, does the BIG-IP always see traffic sourced from the same origin IP address of the client or does it change? If you were to do a tcpdump monitoring on the virtual server IP address, you should be able to see the behavior.