Forum Discussion
8 Replies
Sort By
- Nicolas_MenantEmployeeyou can use the command persist source_addr: Click here
- Michael_Hull_61NimbostratusThe customer wants the persistence to stop when either the browser closes or the session with the application ends. The customer wants to use source_addr persistence, however, I don't see a simple way of doing it. Is there an iRule written out there that can do this?
- Nicolas_MenantEmployeeSession Cookie persistence would definitely be better and would avoid iRules
- Michael_Hull_61NimbostratusThank you...I will go back to my customer with your comments.
- Yoda_34023NimbostratusI have a similiar requirement, but in my case the LTM is acting as a SSL pass through device. Only way I can persist is based on source IP. Now here's the problem; some clients use distributed Proxies. What I thought is to created a Data Group per client. Then somehow do a lookup to these Data Groups and then just direct each data Group to a given Node. In that way no persistance is required, the client's SSL communication does not break. The trade off is that these specific clients never get load balanced (unless there is way to select another node, only if the primary node is not available); of course everything else should be processed as per normal. Any ideas how this can be done?
- HamishCirrocumulusYou can load balance based on SSL id... It used to break with older versions of IE (And I admit I haven't tried doing it for a long time now, I use tend to use session cookies & SSL Offload) but might be worth having a go.
- husam_othman_37Nimbostratusis it possible to reveal the source IP address for an inbound session (even if SNAT) is configured for: HTTP, HTTPS and FTP traffic?
- JRahmAdminsource ip inbound would be IP::client_addr, regardless of the protocol.