Forum Discussion
Load Balancing based off TCP Payload entity
Well, this has turned out to be a tough one...
So I think we're left with two possibilities:
-
Continue to investigate the ephemeral port option. Maybe take a closer look at the payload of the first session to see if there's ANYTHING in there (request or response) that indicates what that second session will be.
-
Use source address persistence. In the absence of ANY information in the second session to tie it to the first, you may be limited to the only information that will be consistent to a single client.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
