OneConnect and Proxy/Squid Load Balancing

I use one-connect quite often with a /32 mask so that individual clients get connection reuse. And the fe/be connections aren't shared between clients. However in testing, doing it this way is actually almost always unnecessary as the clients & servers usually specify connection reuse in the headers anyway.

 

 

Having something other than a /32 mask on the profile does add a lot more (Multiple clients get multiplexed across fewer poolmember connections), but you have to be careful. So many servers assume that the same client is coming across a singel connection. So they make assumptions about the 2nd and subsequent connection (e.g. Authentication and authorisation... oops...)

 

 

H