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

som_86408's avatar
som_86408
Icon for Nimbostratus rankNimbostratus
Feb 18, 2012

source IP based persistence

Hi,     I have a requirement where clients must stick to the same server for HTTP to HTTPS and decided to use source address persistence but in a document (http://devcentral.f5.co...
config
design
Craig_12932's avatar
Craig_12932
Icon for Nimbostratus rankNimbostratus
Feb 18, 2012
I agree that the source you are referring to is not overly clear, i may be on the wrong track here although the only thing i can think of would be the biggest drawback of Source address persistence:

 

 

If an address is NAT'd then in multiple connections behind this address from different connections will be load balanced to the same backend servers. Traditionally this is an issue with ISP mega proxies such as AOL, who used to route all traffic via a single IP for the obvious reasons, fortunately Mega Proxies at carrier level are not such an issue and not commonly used. theoretically 20K connections behind a megaproxy could connect to a VIP with 500 servers behind it and all be LB'd to the same server.

 

 

 

Hope this helps.

 

 

 

Craig